You see errors similar to:
Example 1:
The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration. VMotion [184329483:<mig_id>] failed to create connection with remote host <###.###.###.###>: The ESX hosts failed to connect over the VMotion network Migration [184329483:<mig_id>] failed to connect to remote host <###.###.###.###>: Timeout
Example 2:
The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration. VMotion [-1408237366:<mig_id>] failed to create connection with remote host <###.###.###.###>: The ESX hosts failed to connect over the VMotion network Migration [-1408237366:<mig_id>] failed to connect to remote host <###.###.###.###>: Connection refused
Example 3:
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct.
In the /var/log/hostd.log file, you see entries similar to:
[27703B90 verbose 'Vmsvc.vm:/vmfs/volumes/<datastore_uuid>/TEMP-TEMP/TEMP-TEMP.vmx'] Handling message _vmx1: Migration [a991333:<mig_id>] failed to connect to remote host from host : Timeout
Please note that the "###.###.###.###" text represents IP addresses, which have been anonymized here for security reasons.
VMware vSphere ESXi
VMware vCenter Server
The network configuration (either virtual or physical) present is invalid.
To resolve this issue:
For more information on vMotions and troubleshooting vMotion issues, see Understanding and troubleshooting vMotion.
Other examples:
Impact/Risks:
Network misconfiguration can cause random vMotion failures. Retrying the vMotion operation may be successful, but VMware recommends that you follow this article to isolate and correct the problem.