vMotion fails after physical network changes
search cancel

vMotion fails after physical network changes

book

Article ID: 420494

calendar_today

Updated On:

Products

VMware vCenter Server

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"
  • The connectivity from source ESXi host to the destination host over vMotion kernel is not working. 

    [root@hostname:~] vmkping -I vmk2 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

Environment

vSphere ESXi
vSphere vCenter

Cause

After physical network changes, external physical network is not forwarding vmotion kernel traffic. 

Resolution

As a workaround tried the below steps:
1. Disabled vmotion service on the dedicated vmotion kernel. 
2. Enabled vmotion service over the Management kernel temporarily

Additional Information

'Error: "The vMotion failed because the destination host did not receive data from the source host on the vMotion network" '
Testing VMkernel network connectivity with the vmkping command