vMotion is not working within cluster between ESXI host.

Products

• VMware vSphere ESXi

Issue/Introduction

• vMotion Failed at 20 %
• vMotion is not working within cluster between ESXi host.
• Error while doing vMotion :

• hostd.log :

  [YYYY-MM-DDTHH:MM:SS] verbose hostd[2332791] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/[datastore]/[vm_directory]/vm_name.vmx opID=m3wuhb1q-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=m3wuhb1q-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=m3wuhb1q-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.
  --> "
  --> }

  
  Log File Name: /var/run/log/vobd.log

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

 

Environment

VMware vSphere ESXi

Cause

• This type of issue or error traces can occur only when we used similar IP for vMotion Network which was already assigned to any other device or interface.
• IP will conflict and due which migration failed.

Resolution

• As per the mentioned details and the traces, Its a Network issue which needs to check with internal Physical Network Team.
• Need to change the IP of vMotion Network or other device where same IP is assigned.

Additional Information

For troubleshooting vMotion Network issue :

https://knowledge.broadcom.com/external/article/321012/troubleshooting-vmotion-network-connecti.html