Some of the Oracle VM Server for SPARC networking features work differently when a domain runs the Oracle Solaris 10 OS as compared to the Oracle Solaris 11 OS. The feature differences for the Oracle VM Server for SPARC virtual network device and virtual switch when the Oracle Solaris 11 OS is run in a domain are as follows:
Configuring the vswn device as the primary network interface to enable a service domain to communicate with guest domains
This configuration is required only for domains that run the Oracle Solaris 10 OS. For Oracle Solaris 11, a virtual switch uses the Oracle Solaris 11 network stack, automatically enabling its virtual network devices to communicate with the network interface that corresponds to its back-end device, such as net0. You can no longer use the vswn device itself in Oracle Solaris 11 service domains.
Using an Oracle Solaris 11 etherstub device as a back-end device to create a private virtual switch
If not connected to a back-end device, a virtual switch provides communication only between guest domains and not between guest domains and the service domain. Using an etherstub as a back-end device enables a guest domain to communicate with a zone (including the global zone) that is configured in an Oracle Solaris 11 service domain. This configuration is accomplished by using a VNIC connected to that etherstub.
Using generic names for the virtual switch and virtual network devices
The Oracle Solaris 11 OS assigns generic names for vswn and vnetn devices. Ensure that you do not create a virtual switch with the back-end device that is another vsw or vnet device. Use the dladm show-phys command to see the actual physical devices that are associated with generic network device names.
Using VNICs on the virtual switch and virtual network devices
You cannot use VNICs on vswn devices. An attempt to create a VNIC on vswn fails. See Oracle Solaris 11: Zones Configured With an Automatic Network Interface Might Fail to Start in Oracle VM Server for SPARC 3.2 Release Notes .