Virtual machine loses network connectivity after a migration from an ESXi 5.1/5.5 host to an ESXi/ESX 4.1 or ESXi 5.0 host
search cancel

Virtual machine loses network connectivity after a migration from an ESXi 5.1/5.5 host to an ESXi/ESX 4.1 or ESXi 5.0 host

book

Article ID: 310870

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
After performing a vMotion of a virtual machine from an ESXi 5.1/5.5 host to an ESXi/ESX 4.1 host or an ESXi 5.0 host, you experience these symptoms:
  • The virtual machine gets disconnected from the network.
  • Virtual machine loses network connectivity when using VDS.
  • Virtual machine loses network connectivity after the migration when using VDS dvPortGroup.
  • Virtual machine regains network connectivity if it is migrated back to an ESXi 5.1/5.5 host.
  • In the vmkernel.log file of ESXi 5.0, located at /var/log/, you see entries similar to:

T19:11:33.142Z cpu11:10382050)NetPort: 2602: resuming traffic on DV port 5902
T19:11:33.142Z cpu11:10382050)WARNING: NetDVS: 1477: failed to init client for data com.server.etherswitch.port.teaming on port 5902
T19:11:33.142Z cpu11:10382050)WARNING: NetPort: 1245: failed to enable port 0x30002e1: Bad parameter
T19:11:33.142Z cpu11:10382050)NetPort: 1427: disabled port 0x30002e1
T19:11:33.142Z cpu11:10382050)WARNING: Net: vm 10382050: 207: cannot enable port 0x30002e1: Bad parameter
T19:11:33.142Z cpu11:10382050)Net: 1652: connected DataNode4.eth1 eth1 to vDS, portID 0x30002e2
T19:11:33.142Z cpu11:10382050)Net: 1985: associated dvPort 5787 with portID 0x30002e2
T19:11:33.142Z cpu11:10382050)NetPort: 2602: resuming traffic on DV port 5787
T19:11:33.142Z cpu11:10382050)WARNING: NetDVS: 1477: failed to init client for data com.server.etherswitch.port.teaming on port 5787
T19:11:33.142Z cpu11:10382050)WARNING: NetPort: 1245: failed to enableport 0x30002e2: Bad parameter
T19:11:33.142Z cpu11:10382050)NetPort: 1427: disabled port 0x30002e2
T19:11:33.142Z cpu11:10382050)WARNING: Net: vm 10382050: 207: cannot enable port 0x30002e2: Bad parameter
T19:11:33.143Z cpu11:10382050)Net: 1652: connected DataNode4.eth0 eth0 to vDS, portID 0x30002e3
T19:11:33.143Z cpu11:10382050)Net: 1985: associated dvPort 5839 with portID 0x30002e3
T19:11:33.149Z cpu11:10382050)NetPort: 2602: resuming traffic on DV port 5839
T19:11:33.149Z cpu11:10382050)WARNING: NetDVS: 1477: failed to init client for data com.server.etherswitch.port.teaming on port 5839
T19:11:33.149Z cpu11:10382050)WARNING: NetPort: 1245: failed to enable port 0x30002e3: Bad parameter
T19:11:33.149Z cpu11:10382050)NetPort: 1427: disabled port 0x30002e3
T19:11:33.149Z cpu11:10382050)WARNING: Net: vm 10382050: 207: cannot enable port 0x30002e3: Bad parameter
T19:11:33.187Z cpu8:53011)Config: 346: "SIOControlFlag2" = 0, Old Value: 1, (Status: 0x0)

  • In the vmkernel.log file of ESX 4.1, located at /var/log/, you see entries similar to:

0:00:52:03.785 cpu18:4567)VMotion: 4685: 1353178280579067 D: Resume handshake successful
0:00:52:03.785 cpu14:4578)Swap: vm 4567: 9131: Starting prefault for the migration swap file
vmkernel: 0:00:52:03.798 cpu14:4578)Swap: vm 4567: 9270: Finish swapping in migration swap file. (faulted 0 pages, pshared 0 pages). Success.
vmkernel: 0:00:52:03.847 cpu18:4576)NetPort: 2256: resuming traffic on DV port 319
vmkernel: 0:00:52:03.847 cpu18:4576)WARNING: NetDVS: 1460: failed to init client for data com.vmware.etherswitch.port.teaming on port 319
vmkernel: 0:00:52:03.847 cpu18:4576)WARNING: NetPort: 986: failed to enable port 0x3000013: Bad parameter
vmkernel: 0:00:52:03.847 cpu18:4576)NetPort: 1165: disabled port 0x3000013


Environment

VMware vSphere ESXi 5.0
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.1
VMware ESX 4.1.x
VMware ESXi 4.1.x Installable
VMware ESXi 4.1.x Embedded

Cause

The maximum length of dvUplink name in ESX/ESXi 4.1 and ESXi 5.0 is 32 characters, but in ESXi 5.1/5.5 the maximum dvUplink name length is 81 characters. When performing a vMotion from ESXi 5.1/5.5 to ESX/ESXi 4.1 or ESXi 5.0, the maximum supported dvUplink name length is 32 characters. If the dvUplink name length is longer than 32 characters in ESXi 5.1/5.5 after vMotion to ESX/ESXi 4.1 or ESXi 5.0, the VDS port might lose connection.

Note: This issue can occur regardless of the dvUplink name size. When the virtual machine is rebooted or shutdown\startup there is not any dvs port data update from the vCenter Server to this host.

Resolution

This issue is resolved in ESXi 5.0 Patch 5 (Build 1024429).
This issue is also resolved in ESX/ESXi 4.1 Patch 8.


To workaround this issue, you can perform one or more of the following actions:
  • Ensure that the dvUplink name consists of 31 or lesser characters.
  • Change the port group of the virtual machine to another network and then revert it to the original port group.
  • Power off the virtual machine which is having the issue on ESXi 5.1/5.5, migrate it to ESXi/ESX 4.1, and then power on the virtual machine in ESXi/ESX 4.1. This resolves the network connectivity issue.


Additional Information



VMware ESXi 5.0, Patch ESXi500-201303401-BG: Updates esx-base
VMware ESX 4.1, Patch Release ESX410-201304401-SG: Updates VMkernel, CIM, Tools, and others
VMware ESXi 4.1, Patch Release ESXi410-201304401-SG: Updates Firmware
ESXi 5.1/5.5 ホストから ESXi/ESX 4.1 または ESXi 5.0 ホストに移行後、仮想マシンでネットワーク接続が失われる

Powered by Wolken Software