So it is reading the SCAN information well therefore there is no problem there

I tried to start the SCAN Listeners again and ended up with the same errors

srvctl start scan_listener
------------------------------------------
PRCR-1079 : Failed to start resource ora.LISTENER_SCAN1.lsnr
CRS-2674: Start of 'ora.net1.network' on 'sol1' failed
CRS-2632: There are no more servers to try to place resource 'ora.LISTENER_SCAN1.lsnr' on that would satisfy its placement policy
PRCR-1079 : Failed to start resource ora.LISTENER_SCAN2.lsnr
CRS-2674: Start of 'ora.net1.network' on 'sol1' failed
CRS-2632: There are no more servers to try to place resource 'ora.LISTENER_SCAN2.lsnr' on that would satisfy its placement policy
PRCR-1079 : Failed to start resource ora.LISTENER_SCAN3.lsnr
CRS-2674: Start of 'ora.net1.network' on 'sol1' failed
CRS-2632: There are no more servers to try to place resource 'ora.LISTENER_SCAN3.lsnr' on that would satisfy its placement policy

If it helps, I am using the default automatic network management of Solaris 11.11 however I changed the IP addresses of net1 and net2 manually to meet my network
configuration requirements for the clusterware.

I followed every step of prerequisites for installation on solaris 11.

After verifying everything that I could have as detailed above I am now clueless as to where things are going wrong

Could it be the automatic network management of Solaris 11.11 that is not allowing creation of VIP SCAN IPs ???

the cluster had problem with the public network registration. So there seems to be an error in the setup of your public network.
What hostname have you configured on the public network. What does "hostname" command return.

Check you network setup.

Also if the cluster registered it, can you ge the output of "crsctl stat res ora.net1.network -p"

Maybe you find something in:
How to Validate Network and Name Resolution Setup for the Clusterware and RAC (Doc ID 1054902.1)

what I just saw: it seems your "public hostname" is not on the net1 network, but on the net0 network (which is 10.X.X.X), and this is set to DHCP.

=> The public network must be on the network, where the hostname responds to. So you are bound to use the 10.x.x.x network for public net (or change that in your VBox config).
=> The error you see is very likely bount to the problem, that this network uses DHCP. There are some errors in indicating a DHCP error (with what you see).

You Asked
[xml]the cluster had problem with the public network registration. So there seems to be an error in the setup of your public network.
What hostname have you configured on the public network. What does "hostname" command return.[xml]

hostname
[xml]Sol1[xml]

You asked
[xml]Check you network setup. [xml]

Can you please guide me what to check for network setup or how do I map my hostname to net1 ? Thank you!

You asked
[xml]Also if the cluster registered it, can you ge the output of "crsctl stat res ora.net1.network -p"[xml]

Net0 is NAT Adapter for internet connectivity using DHCP
Net1 is HostOnly Adapter for Public connectivity which you can see in my /etc/hosts
Net2 is HostOnly Adapter for Private Interconnect which you can see in my /etc/hosts

I ran the cluvfy utility for both pre and post installations, results are listed below :

the problem is, that the hostname the server resolves to is on the 10.X.X.X network.
As a result the cluster requires the public network to be on that network. And the error you get, is because this network is on DHCP.

So you have the following options what you can try:
a.) Change the server to have the hostname resolve to the 192.X network
b.) Change the order of the network cards
c.) Remove the 10.X.X.X network for the time of installation

I'm running the same issues. Please let me know how did you fix this problem? You said you added another NIC. What kind of NIC, bridge? How did you connect to the router? Can you show me the output of 'ipadm show-addr'?