This checklist describes end to end requirements and configurations needed for migration with vMotion between your on-premises data center and your cloud SDDC.
vMotion Requirements for SDDCs With NSX-T
|Networking speed and latency||Migration with vMotion requires sustained minimum bandwidth of 250 Mbps between source and destination vMotion vMkernel interfaces, and a maximum latency of 100 ms round trip between source and destination.|
|On-premises vSphere version||
|On-premises DVS version||6.0 higher.|
|On-premises NSX version||any
Note: SDDCs configured with NSX-T do not support hot vMotion to or from on-premises VXLAN encapsulated networks (NSX for vSphere) or Geneve Datacenter Overlay networks (NSX-T).
|IPsec VPN||Configure an IPsec VPN for the management gateway. See "Configuring VPNs and Gateways" in Getting Started With VMware Cloud on AWS.|
|Direct Connect||Direct Connect over a private virtual interface between your on-premise datacenter and your VMware Cloud on AWS SDDC is required for migration with vMotion. See Using AWS Direct Connect with VMware Cloud on AWS.|
|Hybrid Linked Mode||Hybrid Linked Mode is required to initiate migration from the vSphere Client. It is not required to initiate migration using the API or PowerCLI.
See "Hybrid Linked Mode" in Managing the VMware Cloud on AWS Data Center.
|L2 VPN||Configure a Layer 2 VPN to extend virtual machine networks between your on-premises data center and cloud SDDC. Routed networks are not supported. See VMware Cloud on AWS Networking and Security.|
|VMware Cloud on AWS firewall rules||Ensure that you have created the necessary firewall rules as described in Required Firewall Rules for vMotion.|
|On-premises firewall rules||Ensure that you have created the necessary firewall rules as described in Required Firewall Rules for vMotion.|
|Virtual machine hardware and settings||
Ensure that these requirements are met for virtual machine hardware.