vMotion is not working between ESXi hosts in the same cluster.

Products

• VMware vSphere ESXi
• VMware vCenter Server

Issue/Introduction

• vMotion failed at 20%.
• vMotion fails with error "The vMotion failed because the destination host did not receive data from the source host on the vMotion network".
  
  
  
  
• In the ESXi hosts /var/run/log/hostd.log may see the following;
  

  [YYYY-MM-DDTHH:MM:SS] verbose hostd[2332791] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/[datastore]/[vm_directory]/vm_name.vmx opID=m3####1q-707027-auto-f5jp-h5:######-16-01-32-afca] VMotionPrepare: MigrateFromDest message: 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.
-->
[YYYY-MM-DDTHH:MM:SS] info hostd[2100796] [Originator@6876 sub=Vcsvc.VMotionDst.#### opID=m3####1q-707027-auto-f5jp-h5:#######-16-01-32-afca] ResolveCb: VMX reports needsUnregister = true for migrateType MIGRATE_TYPE_VMOTION
[YYYY-MM-DDTHH:MM:SS] info hostd[2100796] [Originator@6876 sub=Vcsvc.VMotionDst.#### opID=m3####1q-707027-auto-f5jp-h5:#######-16-01-32-afca] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.checkpoint.migration.nodata",
-->          message = "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.",
-->       }
-->    ],
-->    reason = "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.",
-->    msg = "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.
--> "
--> }


• May also see the following in ESXi host log /var/run/log/vobd.log.

  [YYYY-MM-DDTHH:MM:SS] [netCorrelator] ####us: [esx.problem.net.vmknic.ip.duplicate]Duplicate IP address detected for ###.###.###.### on interface vmk1, current owner being 00:##:56:##:da:b8.
[YYYY-MM-DDTHH:MM:SS] [netCorrelator] ####us: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for ###.###.###.### on interface vmk1. The current owner is 00:##:56:##:da:b8.
[YYYY-MM-DDTHH:MM:SS] [netCorrelator] ####us: [esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for ###.###.###.### on interface vmk1, current owner being 00:##:56:##:da:b8.

Environment

VMware vSphere ESXi

VMware vCenter Server

Cause

This issue can occur when there is an IP configured on the network that is a duplicate of the ESXi hosts' vMotion vmk IP. 

Resolution

Remove or change one of the duplicated IP's prevent the conflict.

Additional Information

See Troubleshooting vMotion network connectivity issues for further details.