Extended networks require a layer 2 Virtual Private Network (L2VPN), which provides a secure communications tunnel between an on-premises network and one in your cloud SDDC.
Each end of this tunnel has an ID. When the tunnel ID matches on the cloud SDDC and the on-premises side of the tunnel, the two networks become part of the same broadcast domain. Extended networks use an on-premises gateway as the default gateway. Other network services such as DHCP and DNS are also provided on-premises.
You can change a logical network from routed to extended or from extended to routed. For example, you might configure a logical network as extended to allow migration of VMs from your on-premises data center to your cloud SDDC. When the migration is complete, you might then change the network to routed to allow the VMs to use VMware Cloud on AWS networking services.
Verify that Layer 2 VPN tunnel is available. See Configure a Layer 2 VPN Tunnel in the SDDC.
- Log in to the VMC Console at https://vmc.vmware.com.
- Follow the procedure in Create or Modify a Network Segment to create an Extended segment bound to the Tunnel ID of the L2VPN tunnel.
- Click SAVE.
- Click DOWNLOAD CONFIG to download a file containing the peer code and other information you'll need when configuring the on-premises of the remote side VPN configuration.
- Click REMOTE STANDALONE EDGE DOWNLOAD to download an NSX Standalone Edge image in OVF format that you must install and configure as the client side of the L2VPN. See Download and Configure the Autonomous NSX Edge.