The vMotion failed because the destination host did not receive data from the source host on the vMotion network.

Products

• VMware vSphere ESXi

Issue/Introduction

The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check the vMotion network setting and physical network configuration and ensure they are correct. "[175382727:8873687851581059918]" Network unreachable. vMotion migration.

[175382727:8873687851581059918] failed to create a connection with remote host <10.0.0.0>: The ESXi hosts failed to connect over the vMotion network. The vMotion migrations failed because the ESXi hosts were not able to connect over the vMotion network. Check the vMotion network setting and physical network configuration.

Failed waiting for data. Error 195887167. Connection closed by remote host, possibly due to timeout.

2024-09-27T12:26:03.280276Z Migration [-1408119426:9123156728048975813] failed to connect to remote host <xxx.xxx.xxx.241> from host <xxx.xxx.xxx.126>: Host is down. VMotionStream [-1408119426:9123156728048975813] stream thread failed to connect to the remote host <xxx.xxx.xxx.241>: The ESX hosts failed to connect over the VMotion network The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration.

2024-09-27T12:26:03.302339Z vMotion migration [-1408119426:9123156728048975813] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

Environment

VMware vSphere ESXi 8.0.x
VMware vSphere ESXi 7.0.x
VMware vSphere ESXi 6.7

Cause

The network IP configuration of vMotion VMKernel configuration present is invalid.

Resolution

1.  Check the IP connectivity over vMotion kernel interface between Source and Destination ESXi to make sure if they are reachable with expected MTU. 

               If you have Jumbo Frames configured in your environment, run the vmkping command with the -s and -d options.

              vmkping -d -s 8972 #.#.#.#

      To test 1500 MTU, run the command:

         vmkping -I vmkX #.#.#.# -d -s 1472

         vmkping -I vmkX <IP of destination host vMotion vmk> -S (If vmotion is  configured on vMotion tcp/ip stack) - d -s (to check for MTU mismatch)

Note: In the command, the -d option sets DF (Don't Fragment) bit on the IPv4 packet. 8972 is the size needed for 9000 MTU in ESXi.

If the vmotion is configured on vmotion tcp/ip stack, run the below command:
        vmkping -I vmk0 #.#.#.# -S vmotion   

    Where vmkX is the vmkernel number of the vMotion vmkernel on the source host.

2.  Check for packet loss over the vMotion network. Try having the source host ping (vmkping) the destination host's vMotion vmknic IP address for the duration of the vMotion.

     For example:

1. VMKping with -s and -s to check for MTU mismatch
2. Check Port 8000 is open between hosts.
3. Temporary tag management for vmotion on two hosts and test between them.

     For more information, see https://knowledge.broadcom.com/external/article/344313

Additional Information

For more information on vMotions and troubleshooting vMotion issues, see https://knowledge.broadcom.com/external/article/321009