By using the management interface of VMware Cloud Director Availability in the cloud site backed by NSX Data Center for vSphere, the service provider registers the NSX Manager. Then the service provider or the organization administrator creates the server L2 VPN session enabling the L2 stretch of one or more networks across the on-premises site.
- Verify that in both the cloud site and in the on-premises site VMware Cloud Director Availability 4.2.1 or later is successfully deployed.
- Verify that the on-premises site is prepared for an L2 VPN session with NSX Autonomous Edge. For information about the order of the steps of the procedure, see Stretching Layer 2 Networks On-Premises.
- Verify that in the cloud site NSX Data Center for vSphere (NSX-V) 6.4.10 or later is deployed to allow stretching of routed networks after registering the NSX Manager.
- NSX Data Center for vSphere stretches only Routed type networks only with interface type Subinterface, not Internal nor Distributed, and cannot stretch Isolated nor Direct type networks. NSX Data Center for vSphere can stretch only VXLAN and VLAN OrgVDC routed networks connected to the Trunk interface, and cannot stretch networks connected to the Uplink nor Internal interfaces. Guest VLAN Allowed must be deselected and if at some point it was selected, recreate the network for stretch from scratch.
- For NSX-T Data Center, skip this procedure and see Create a Server L2 VPN Session with NSX-T Data Center in the Cloud.
- Verify that before stretching VLAN routed networks, in vSphere the service provider first created and associated the trunk interface with the edge gateway.
- Verify that VMware Cloud Director 10.0.0.3 or later is deployed in the cloud site.
- Verify that to register the NSX Manager with the Cloud Service for the first time, the service provider authenticates in VMware Cloud Director Availability as a System Administrator user.
- Verify that VMware Cloud Director is prepared to use vSphere backed network resources, after adding an external network, then adding an NSX Data Center for vSphere edge gateway that allows establishing the server L2 VPN session while providing the organization VDC networks with connectivity to external networks:
- Verify that in VMware Cloud Director the vSphere backed external network is added. For more information, see Add an External Network That Is Backed by vSphere Resources in the VMware Cloud Director documentation.
- Verify that in VMware Cloud Director the NSX Data Center for vSphere edge gateway is added. For more information, see Add an NSX Data Center for vSphere Edge Gateway in the VMware Cloud Director documentation.
- Log in to the management interface of the Cloud Replication Management Appliance.
- In a Web browser, go to https://Appliance-IP-Address/ui/admin.
- Select Appliance login or SSO login and enter the root or the single sign-on user credentials.
- Click Login.
- In the left pane, under the Configuration section click L2 Stretch.
- Click NSX-V Managers and select an NSX Manager with an Unconfigured status.
- Click Edit.
- In the Configure window, register the NSX Manager with the Cloud Service.
The NSX Manager is now registered, shows Up status, and is ready for creating the server L2 VPN session.
- In the Password text box, enter the admin user password for the NSX Manager.
- To register the NSX Manager for L2 stretch management by VMware Cloud Director Availability, click Configure.
Verify the thumbprint and accept the SSL certificate of the NSX Manager.
- Click L2 VPN Sessions.
- From the NSX Gateway menu, select the edge gateway and click New.
The NSX Gateway menu lists both NSX-V and NSX-T edge gateways that are registered and added in VMware Cloud Director. For information about using NSX-T for server L2 sessions, see Create a Server L2 VPN Session with NSX-T Data Center in the Cloud.
- In the New L2 VPN server session window, configure the server L2 VPN session and click Create.
- In the Name text box, enter a name for this server L2 VPN session.
- In the Local Address text box, enter an IP address residing in the IP pool of the edge gateway at the server side of the L2 VPN session.
The local IP address is a static IP address within the allocated IP range of the NSX edge gateway hosting the server L2 VPN session.
- In the Remote Address text box, enter the on-premises IP address at the client side of the L2 VPN session.
Usually the remote IP address is the static endpoint IP address of the NSX Autonomous Edge on-premises. For more information, see Configure the Networks of the NSX Autonomous Edge On-Premises.Note: Ensure that the network communication between the local IP address in the cloud and the remote IP address on-premises exists unobstructed.
- In the Pre-shared Key text box, enter the pre-shared key as provided by your network administrator.
Enter only visible ASCII characters, including space, excluding non-printable characters like Null, BEL, and so on. The pre-shared key must meet the following complexity requirements:
- At least 8 characters
- At least one uppercase letter
- At least one lowercase letter
- At least one digit
- At least one special character
- In the Tunnel Interface text box, enter a private, non-routable subnet address in a CIDR notation.
- Under Server Network(s), to establish an L2 stretch select the server side networks to stretch.
- The available networks for selection are filtered to show only OrgVDC networks connected to the trunk interface of the NSX Data Center for vSphere.
- The number of available server networks for selection, depends on the version of VMware Cloud Director. For information about the VMware Cloud Director versions, see the prerequisites above.
- Cannot change or edit the selected networks for stretching when using NSX Data Center for vSphere. To modify the stretched networks, click Delete and recreate the server L2 VPN session.
- Attempting to delete the server L2 VPN session takes several minutes. Do not attempt to recreate the server L2 VPN session immediately after deleting as it fails due to the deletion progress in the background.
You created the server L2 VPN session in the cloud site.
What to do next
You can now create the client L2 VPN session that completes the L2 stretch. For more information, see Stretching Layer 2 Networks On-Premises.