Configuring vDS across multiple vCenters to support Long Distance vMotion

Starting with vSphere 6.0, you have the ability to hot-migrate VMs between vCenter Server with the support for geographical vMotion (long-distance vMotion).

There are some requirements, including some at the network side:

• Physical network requirements: The minimum network bandwidth is 250 Mbps with a maximum latency of 150 ms.
• Virtual network requirements: There should be layer network connectivity for the VM network port groups. Also, for each host there should exist two VMkernel adapters marked for vMotion traffic, and both must be reachable to each other (also with routing).
• CPU compatibility: Both hosts must have the same CPU generation family or must be compliant with the same EVC baseline.
• Version requirements: The source and destination vCenter Server instances and ESXi hosts must be 6.0 or later. Also, the cross-vCenter Server and long-distance vMotion features both require an Enterprise Plus license.
• Time sync: Both vCenter Server instances must be time-synchronized with each other for correct vCenter Single Sign-On token verification.

The following table summarizes the requirements for the different versions of vMotion:

The vCenter servers perform network compatibility checks to prevent several possible configuration problems.

For more information, see KB 2106949 (https://kb.vmware.com/s/article/2106949)—Long Distance vMotion requirements in VMware vSphere 6.0.