After configuring the networks of the NSX Autonomous Edge, by using On-Premises to Cloud Director Replication Appliance create the client side of the L2 VPN session, stretching one or more networks across the cloud site.
- Verify that VMware Cloud Director Availability 4.2 or later is successfully deployed.
- Verify that the On-Premises to Cloud Director Replication Appliance is paired with a cloud site. All L2 stretch settings on-premises enable only after pairing with a cloud site as the On-Premises to Cloud Director Replication Appliance must browse the virtual machines.
- Verify that in the cloud site the server L2 VPN session is created. For more information, see Create a Server L2 VPN Session with NSX in the Cloud.
- Verify that in the on-premises site the networks of the NSX Autonomous Edge are configured. For more information, see Configure the Networks of the NSX Autonomous Edge On-Premises.
- Log in to the management interface of the VMware Cloud Director Availability On-premises Appliance.
- In a Web browser, go to https://On-Premises-Appliance-IP-address/ui/admin.
- Log in as the root user.
- In the left pane, under the System section click L2 Stretch.
- On the NSX Autonomous edges page, click L2 VPN Sessions.
- If more than one NSX Autonomous Edge instance is registered with the On-Premises to Cloud Director Replication Appliance, from the NSX Autonomous Edge drop-down menu, select the correct NSX Autonomous Edge name to use for the client L2 VPN session.
- To create a client L2 VPN session, click New and complete the New Client L2 VPN Session wizard.
If your user session is not currently extended to the cloud site, enter credentials to authenticate to the cloud site.
- On the VDC and edge Gateway page, select the cloud site virtual data center and the edge gateway.
- On the Settings and networks page, configure the L2 VPN and click Next.
- In the Name text box, enter a name for this client L2 VPN session.
- From the Server session drop-down menu, select the cloud side L2 VPN server session.
- In the Local Address text box, enter the on-premises IP address at the client side of the L2 VPN session.
The local IP address must be the same as the uplink port IP address of the NSX Autonomous Edge hosting the client L2 VPN session.
- In the Remote Address text box, enter the cloud IP address at the server side of the L2 VPN session.
Usually the remote IP address is the endpoint IP address of the server L2 VPN session. For more information, see Create a Server L2 VPN Session with NSX in the Cloud.
- Under the Client Network column, to create an L2 stretch across the networks select an on-premises VLAN network against each server network in the cloud site.
The number of available client networks for selection, depends on the cloud site version of VMware Cloud Director. For information about the versions of VMware Cloud Director, see the prerequisites in Create a Server L2 VPN Session with NSX in the Cloud.
- On the Ready To Complete page, to create the L2 VPN stretch click Finish.
The client L2 VPN session on-premises is created and the L2 stretch across the cloud site is complete.
What to do next
You can now use this stretched network when migrating some virtual machines to the cloud that are a part of a single on-premises workload, keeping the network connectivity between the migrated virtual machines in the cloud site and the non-migrated virtual machines on-premises. You can easily manage the L2 stretch by using the management interface of the On-Premises to Cloud Director Replication Appliance, or directly by using the management interface of the NSX Autonomous Edge.