Virtual machines with multiple network adapters connected to virtual Distributed Switch (vDS) lose network connectivity after a successful HA Failover
book
Article ID: 307467
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
High Availability failover occurs and virtual machines are restarted on a new ESXi/ESX host.
A virtual machine has multiple network adapters attached to multiple virtual Distributed Switches (vDS) with the same port number.
After the virtual machine powers on, the network adapters have no network connectivity.
Attempting to manually connect the virtual network card using the vSphere Client may fail with the error:
invalid configuration for device
In the vmware.log file, you see entries similar to:
[msg.ethernet.e1000.openFailed] Failed to connect ethernet0 VMXNET3 user: failed to connect Ethernet1 to DV Port 100 VMXNET3 user: failed to connect Ethernet1 to DV Port 101 VMXNET3 user: failed to connect Ethernet1 to DV Port 103
In the /var/log/hostd.log file, you see entries similar to:
YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 1 on dvs cb 8f 1e 50 fb 06 20 37-b8 06 e0 2b 17 b4 b3 ad not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 100 on dvs cb 8f 1e 50 fb 06 20 37-b8 06 e0 2b 17 b4 b3 ad not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 100 on dvs 99 4a 1e 50 89 ee 2c ab-70 4b bb 59 36 04 c6 79 not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 101 on dvs cb 8f 1e 50 fb 06 20 37-b8 06 e0 2b 17 b4 b3 ad not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 101 on dvs 99 4a 1e 50 89 ee 2c ab-70 4b bb 59 36 04 c6 79 not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 103 on dvs cb 8f 1e 50 fb 06 20 37-b8 06 e0 2b 17 b4 b3 ad not found YYYY-MM-DD TIME Z [20544B90 verbose 'NetworkProvider'] DVPort 103 on dvs 99 4a 1e 50 89 ee 2c ab-70 4b bb 59 36 04 c6 79 not found
Environment
VMware vCenter Server 5.0.x VMware vCenter Server 5.1.x
Cause
The Fault Domain Manager (FDM) stores information about the virtual machines it protects in a mapping file. If a virtual machine has multiple network adapters attached to multiple virtual Distributed Switches (vDS) with the same port number, it will only store one vDS port in the mapping file. When a failover occurs, the FDM fails to load the other ports and results in a network outage for the virtual machine.
Resolution
This is a known issue affecting vCenter Server 5.0/5.1 and ESXi 5.1.
Note: Ensure to apply the update/patch to both ESXi and vCenter Server. Applying the update or patch to one of the products does not automatically resolve the issue in the other.
To work around this issue:
Log in to the vSphere Client.
Right click on the virtual machine and click Edit Settings.
Under the virtual network adapter, change the port group to any other portgroup on the virtual switch.
Click OK.
Once the settings have been applied, set the portgroup back to the original.
If this does not resolve the issue, migrate the virtual machine to another host and then power cycle it.
Additional Information
To be alerted when this document is updated, click the Subscribe to Article link in the Actions box