Cross vCenter migration fails with error "The vMotion failed because the destination host did not receive data from the source host on vMotion network"
Article ID: 414793
Updated On:
Products
Issue/Introduction
Cross-vCenter migration requires network connectivity between both vCenter instances and the ESXi hosts. VMware documentation specifies the following requirements:
-
Both vCenters must be reachable over TCP 443 (management communication).
-
ESXi hosts must communicate over TCP 8000 and 902 for vMotion and NFC data transfer.
-
Both environments must have routed network connectivity to allow migration traffic.
Cross vCenter Migration and Clone requirements in VMware vSphere 6.x and later
Environment
VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x
Cause
Cross-vCenter migrations between different subnets require routed Layer 3 network connectivity between the source and destination vCenter Servers, as well as their associated ESXi hosts.
An isolated subnet without proper routing will not support these migration operations.
Resolution
Ensure that Layer 3 connectivity exists between the vCenter Server instances. Proper connectivity is required for successful cross-vCenter operations. For detailed guidance and requirements regarding cross-vCenter migrations, please follow the Broadcom Knowledge Base article:
Cross vCenter Migration and Clone requirements in VMware vSphere 6.x and later
This article provides the recommended prerequisites and considerations to ensure migration operations function correctly.
Additional Information
- The Network Compatibility Checks During vMotion Between vCenter Server Instances section in the vCenter Server and Host Management Guide.
- The MAC Address Management During Migration Between vCenter Server Systems section in the vCenter Server and Host Management Guide.
- Using Enhanced Linked Mode section in the vCenter Server Host Management Guide.
For other related information, see:
Feedback
