The on-premises end of your L2VPN must be an NSX Edge appliance. You must configure this appliance and related on-premises vSphere networking before you can create an L2VPN.

If you have a compatible version of NSX-T installed in your on-premises data center, you can use your existing NSX Edge appliance as the on-premises (client) side of an L2VPN that connects to your SDDC. If necessary, you can download and deploy an autonomous NSX Edge and configure it as the L2VPN client. The following table lists compatible SDDC and on-premises versions. To determine the version of NSX-T running in your SDDC, see Correlating VMware Cloud on AWS with Component Releases in the VMware Cloud on AWS Operations Guide.
Table 1. L2VPN Interoperability
L2VPN Server Version (SDDC) L2VPN Client Version (On-Premises Edge)
3.1.2 3.1.2, 3.1.1, 2.5.3
3.1.1 3.1.1, 3.1.0, 3.0.1
3.1.0 3.1.1, 3.0.1, 3.0.0
3.0.3 3.0.3, 3.0.2, 3.0.1
3.0.2 3.0.2, 3.0.1, 2.5.2
3.0.0 3.0.0, 2.5.0, 2.5.1

Procedure

  1. (Optional) Download the standalone autonomous NSX Edge.
    If you do not have a compatible version of NSX-T installed in your on-premises data center, you may be able to download and configure a standalone Autonomous Edge appliance to use as the on-premises endpoint for your L2VPN. On the L2VPN page, click AUTONOMOUS EDGE DOWNLOAD to download the Autonomous Edge as an OVF file.
  2. Install and configure the Autonomous Edge.
    See Add an Autonomous Edge as an L2 VPN Client in the NSX-T Data Center Administration Guide for information about how to install and configure the Autonomous Edge in your on-premises vCenter Server.