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

Requirement

Description

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

One of:

  • vSphere 6.7u1

  • vSphere 6.5P03

or higher.

On-premises DVS version

6.0 higher.

On-premises NSX version

any

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.

  • Virtual machine hardware version 9 or later is required for migration with vMotion from the on-premises data center to the cloud SDDC.

  • EVC is not supported in the VMware Cloud on AWS SDDC.

  • VMs that are created in the cloud SDDC or that have been power-cycled after migration to the cloud SDDC can't be migrated back to the on-premises data center with vMotion unless the on-premises EVC baseline is Broadwell. You can relocate these VMs after powering them off, as long as their virtual machine hardware version is compatible with the on-premises data center.

  • Migration of VMs with DRS or HA VM overrides is not supported. For more information on VM overrides, see Customize an Individual Virtual Machine.

Note:

Source switch configurations (including NIOC, spoofguard, distributed firewall, and Switch Security) and runtime state are not applied at the destination as part of migration in either direction. Before you initiate vMotion, apply the source switch configuration to the destination network.

Requirement

Description

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

vSphere 6.5 patch d and later

vSphere 6.0 update 3 and later

If your on-premises vCenter Server is part of an MxN Enhanced Linked Mode configuration, nodes in your on-premises data center must be within the same site to minimize latency.

vSphere 5.1 or 5.5

vMotion from on-premises data centers running vSphere 5.1 or 5.5 can be supported only by using the VMware Hybrid Cloud Extension. See https://hcx.vmware.com/content/docs/vmware-hcx-enterprise-install-guide.pdf for more information.

On-premises virtual switch configuration

Standard switches

If you use standard switches for virtual machine networking, you can migrate virtual machines to your cloud SDDC, but cannot migrate them back to your on-premises data center.

vSphere Distributed Switch 6.0

By default, VMware Cloud on AWS SDDCs are deployed with vSphere Distributed Switch version 6.0. Use vSphere Distributed Switch version 6.0 in your on-premises data center for compatibility.

vSphere Distributed Switch 6.5

If you must use vSphere Distributed Switch version 6.5 in your on-premises data center, you can request an upgrade of the distributed switches in your cloud SDDC. Contact VMware Support.

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.

  • Virtual machine hardware version 9 or later is required for migration with vMotion from the on-premises data center to the cloud SDDC.

  • EVC is not supported in the VMware Cloud on AWS SDDC.

  • VMs that are created in the cloud SDDC or that have been power-cycled after migration to the cloud SDDC can't be migrated back to the on-premises data center with vMotion unless the on-premises EVC baseline is Broadwell. You can relocate these VMs after powering them off, as long as their virtual machine hardware version is compatible with the on-premises data center.

  • Migration of VMs with DRS or HA VM overrides is not supported. For more information on VM overrides, see Customize an Individual Virtual Machine.