Troubleshooting when a virtual machine loses network connection after vMotion

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

This article provides troubleshooting steps for a single virtual machine that loses its network connection after performing a vMotion.

Symptoms:

After migrating a virtual machine with vMotion, you experience these symptoms:

The virtual machine loses its network connection.
There is no network connectivity to or from a single virtual machine.
A TCP/IP connection fails to and from a single virtual machine.

Environment

VMware ESXi 4.1.x Installable
VMware ESX 4.0.x
VMware ESX 4.1.x
VMware ESX Server 3.0.x
VMware vCenter Server 5.0.x
VMware ESXi 3.5.x Embedded
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Embedded
VMware ESXi 4.0.x Embedded
VMware vSphere ESXi 5.1
VMware VirtualCenter 2.0.x
VMware VirtualCenter 2.5.x
VMware ESX Server 3.5.x
VMware vCenter Server 4.0.x
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 5.5
VMware vSphere ESXi 6.0
VMware vCenter Server 6.0.x
VMware ESXi 3.5.x Installable
VMware vCenter Server 5.5.x
VMware vCenter Server 5.1.x
VMware vCenter Server 4.1.x

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

To troubleshoot when a virtual machine loses network connection after performing vMotion:

Verify the physical network connectivity. From the virtual machine, ping different sources to identify where the issue may be:
- Ping another virtual machine on the same virtual switch
- Ping the ESX Service Console
- Ping the default gateway
- Ping a target outside the network
  
  For more information, see Testing network connectivity with the ping command (1003486).
Verify the physical switch setup. For more information, see Loss of network connectivity when Cisco port security is configured on the physical switch (1002811).
Verify that the correct version of VMware Tools is installed. For more information, see Verifying a VMware Tools build version (1003947).
If the preceding steps do not resolve the issue and you are experiencing a complete lack of network connectivity from a particular virtual machine, see Troubleshooting virtual machine network connection issues (1003893).
If you are experiencing network connectivity issues with the ESX host or with multiple virtual machines, see ESX/ESXi hosts have intermittent or no network connectivity (1004109).

Note: If the problem persists after completing the steps in this article:

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware ESX/ESXi using the vSphere Client (653).
File a support request with VMware Support and note this Knowledge Base article ID (1003839) in the problem description. For more information, see How to Submit a Support Request .

Additional Information

Loss of network connectivity when Cisco port security is configured on the physical switch
Testing network connectivity with the ping command
Troubleshooting virtual machine network connection issues
Verifying a VMware Tools build version
ESX/ESXi hosts have intermittent or no network connectivity
vMotion 後に仮想マシンがネットワーク接続から切断された場合のトラブルシューティング
对执行 vMotion 后虚拟机失去网络连接的问题进行故障排除
Collecting diagnostic information for VMware ESX/ESXi