A number of virtual machines in a vSphere 5.5 DRS cluster are connected to the same virtual
switch port group. After several of these VMs are migrated to another host, an administrator
notices that they have lost network connectivity. The Events tab in vCenter Server shows this
error message:
Failed to initialize ethernet0.
The vmkernel log file on the host running the affected VMs contains this message:
Can’t connect device:’port group name’: Out of resources.
Which caused this issue?
A.
Network I/O Control was enabled.
B.
The DRS cluster containing the VMs was set to Fully Automated with the Migration Threshold
set to Conservative.
C.
There were insufficient uplinks configured on the virtual switches.
D.
The virtual switch port allocation was changed from the default setting.
Explanation:
Agree with D
The virtual machines lose network connection after vMotion.
After several successful vMotion migrations to the same host, many of the virtual machines lose network connectivity.
Connect is not selected for the virtual machine’s VMNIC. Reselecting Connect restores network connectivity.
The Event log and Events in VirtualCenter show the error:
Failed to initialize ethernet0
The vmware.log file for the virtual machines that lost connectivity shows the error:
[msg.ethernet.openFailed] Failed to initialize ethernet0
The VMkernel log on the host to which the virtual machines were migrated shows the error:
Can’t connect device: `port group name`: Out of resources
You may experience this issue if the virtual switch has exceeded its number of configured VMkernel ports.
For example, if you have a single virtual switch (that is set to the default of 24 ports for VMware Infrastructure 3, 56 default ports in vSphere) with multiple port groups and virtual machines, but the output of the esxcfg-vswitch command shows that the virtual switch has 32 configured ports and 32 ports in use, the virtual switch has exceeded its number of configured ports.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009103
0
0
I think C. must be the answer:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009103
0
0
Sorry, my fault. You can only increase the number of Ports on the vSwitch, NOT Uplinks.
0
0
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004075
0
0
D : The virtual switch port allocation was changed from the default setting.
0
0
In 5.5, the default is 120 ports. So it’s possible that (on a large host) the limit has been reached without touching the defaults..?
0
0