vMotion not working due to kernel uplink shows as "void"

Products

• VMware vSphere ESXi

Issue/Introduction

• vMotion fails with the error "The vMotion failed because the destination host did not receive data from the source host on the vMotion network"

• Testing the connectivity from source ESXi host to the destination ESXi host over vMotion kernel is failing. 
  
  [root@hostname:~] vmkping -I vmkX x.x.x.x -S vmotion
PING x.x.x.x (x.x.x.x): 56 data bytes

  --- x.x.x.x ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

• LAG in use and running esxtop command shows that the vMotion vmk interface doesn't have any vmnic associated and shows void.

Environment

VMware vSphere ESXi

Cause

• A VDS using Link Aggregation Group (LAG) requires all Portgroups to be configured with the LAG as the sole active uplink.
•  A misconfiguration exists on the vMotion portgroups Teaming and failover policy, with the LAG set to 'Unused' instead of 'Active' as below 
  
  
  
  
• This incorrect configuration leaves the vMotion VMkernel port (vmk) without attached uplinks, which consequently results in connectivity failures.

Resolution

• Ensure that the Teaming and Failover policy for the Distributed Switch port groups prioritizes the LAG for Active uplinks over any standalone uplinks.
  
  

Additional Information

Configuring a LAG on a vSphere Distributed Switch Port Group when using LACP