Customer onboarding can encompass several scenarios. Some common onboarding scenarios include the following:

This section describes some of the scenarios in which the VMware NSX L2VPN service can be leveraged as a means for onboarding customer workloads to a VMware Cloud Provider.

Long-distance vSphere vMotion migration is an attractive feature to leverage when considering VMware NSX L2VPN services, enabling the live migration of a VM between vCenter Server instances. With one vCenter Server node deployed in each site joined to the same SSO domain, consumers are able to perform vSphere vMotion migration tasks between vCenter Server instances through the VMware vSphere Web Client. Having both vCenter Server instances joined to the same SSO domain is not a requirement, but is recommended for easier management of hybrid cloud environments.

 

It is important to remember that for successful vSphere vMotion operations to occur, the VMware Cloud Provider Program and on-premises VMware ESXi™ hosts must be able to communicate between sites on the vSphere vMotion VMkernel port. If you are using a dedicated vSphere vMotion IP network, verify that hosts have the vSphere vMotion TCP/IP stack associated with the appropriate vSphere vMotion VMkernel ports. Because vSphere vMotion traffic is unencrypted, you might also consider configuring the appropriate access list and other internal network security standards so that vSphere vMotion traffic is not compromised.

While VMware NSX L2VPN services are best suited for low-latency, high-bandwidth situations, long-distance vSphere vMotion can be a suitable option for implementations where the site-to-site network connectivity meets the recommended requirements for long-distance vSphere vMotion migration.