Configure an Extended Segment for the Layer
2 VPN
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.
Verify that Layer 2 VPN tunnel is available.
See Configure a Layer 2 VPN Tunnel in the 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 GovCloud
networking services. - Log in to theVMware Cloud on AWS GovCloudat https://www.vmc-us-gov.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.
- ClickSAVE.
- ClickDOWNLOAD CONFIGto download a file containing the peer code and other information you'll need when configuring the on-premises of the remote side VPN configuration.
- Configure the client side of the L2VPN.