You can use a VMware Cloud on Public Cloud layer 2 Virtual Private Network (L2VPN) to extend your on-premises network to one or more VLAN-based networks in your SDDC. This extended network is a single subnet with a single broadcast domain. You can use it to migrate VMs to and from your cloud SDDC without having to change their IP addresses.
If L2VPN is not activated in your SDDC, and you want to activate it, contact your account team.
In addition to data center migration, you can use an extended L2VPN network for disaster recovery, or for dynamic access to cloud computing resources as needed (often referred to as "cloud bursting").
VMware Cloud on Public Cloud uses NSX to provide the L2VPN server in your cloud SDDC. L2VPN client functions are provided by an on-premises NSX Edge. See VMware Configuration Maximums for L2VPN limits.
The VMware Cloud on Public Cloud L2VPN feature supports extending VLAN networks. The L2VPN connection to the NSX server uses an IPsec tunnel. The L2VPN extended network is used to extend Virtual Machine networks and carries only workload traffic. It is independent of the VMkernel networks used for migration traffic (ESXi management or vMotion), which use either a separate IPsec VPN or a dedicated high bandwidth, low latency connection.
You cannot bring up an L2VPN tunnel until you have configured the L2VPN client and server and created an extended network that specifies the tunnel ID you assigned to the client.
