Cross vCenter migration of Live Virtual machines fails with error "The vMotion failed because the destination host did not receive data from the source host on the vMotion network"
Article ID: 433068
Updated On:
Products
Issue/Introduction
- Cross vCenter migration of Live Virtual machines fails with below error.
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. Migration [ ] failed to connect to remote host <##.##.##.##> from host <##.##.##.#>: Network unreachable.vMotion migration [ ] failed to create a connection with remote host <##.##.##.##>: The ESX hosts failed to connect over the VMotion networkThe vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network.Check the vMotion network settings and physical network configuration. - Cross vCenter migration of Powered-off Virtual machines completes successfully.
Environment
VMware vSphere ESXi
VMware vCenter Server
Cause
Cross vCenter migration of Live Virtual machines will fail if the vMotion is enable on the vmkernal adaptors which are unable to communicate with each other across the cluster.
Live cross vCenter migration requires dedicated vMotion network. However, offline cross vCenter migration does not strictly require dedicated vMotion networking, as it can leverage the management network.
To check for IP connectivity and packet loss over the vMotion network. Try having the source host ping (vmkping) the destination host's vMotion vmknic IP address.
Example
vmkping -I vmk# <IP of destination host vMotion vmk>
where vmk# is the vmkernel number of the vMotion vmkernel on the source host. For more information, see Testing VMkernel network connectivity with the vmkping command.
Resolution
Enable the vMotion on the vmkernel adaptors of the hosts which can communicate with each other across the network.
Additional Information
Feedback
