Go to main content
Oracle® Solaris 11.3 Release Notes

Exit Print View

Updated: July 2017

Networking Issues

This section describes the network-related issues in Oracle Solaris 11.3.

SPARC: Creating a VNIC Fails If a Physical NIC Is Used as net-dev (19188703)

On SPARC systems, creating a VNIC fails if a physical NIC is specified as the net-dev parameter in the creation of a virtual switch.

The following error message is displayed:

HOST vsw: [ID XXXXXX kern.warning]
WARNING: vswX:vnic_create(ldoms-vswX.vportY failed. Err=2
DATE HOST vsw: [ID kern.warning]
WARNING: vswX: Unable @ DATE HOST to add new port (0xHHH), err=1

Workaround: Use the network vanity name (net0, net1, or net2) as the link name. For example, do not use the physical NIC name to create a virtual switch.

# ldm add-vsw net-dev=igb1 primary-vsw1 primary

Instead, use the network vanity name.

# ldm add-vsw net-dev=net1 primary-vsw1 primary

You can use the dladm show-phys command to find the network vanity names.

# dladm show-phys -P
net1     igb1       Ethernet     ------

In the example, net1 is the network vanity name.

DLMP Does Not Work on an SR-IOV Virtual Function or a Virtual Network Device in a Guest Domain (17656120)

You cannot configure a Datalink Multipathing (DLMP) aggregation on an SR-IOV NIC virtual function or a virtual network device in a guest domain.

SPARC: Migrating a Zone Between Guest Domains Sharing alt-mac-addrs Loses Networking (20463933)

When a zone is running inside a guest domain and the zone is allocated one of the domain MAC addresses, migrating the zone to another guest domain might cause networking to silently fail. The MAC address is allocated by using the following command:

# ldm set-vnet alt-MAC-addrs

Network failure occurs when the same MAC address is configured on the destination guest domain, both the guest domains are on the same physical host, and both domains share the same virtual switch configured on the control domain. This failure applies to cold migration of zones and live migration of kernel zones.

Workaround: Migrate to a guest domain on a separate physical host. Otherwise, if the migration is already complete, halt the guest domains, unbind and rebind them, and boot the guest domain. This process resets the networking configuration and enables the zone networking to function again.