The platform enables you to create site-to-site VPNs between virtual datacenter networks, and other entities. These VPNs use the IPsec framework.
To work with VPNs, go to Virtual datacenters → select a Virtual datacenter → Network → VPN
...
Initial support for VPNs requires you to create a VPN entity site for each side of a VPN that connects to connected virtual datacenter network. Both sides sites of a VPN must have the same encryption and authentication settings, and inverse local and remote network configurations.
...
It may be helpful to complete this table to record your network values before you create your VPN:
VDC name | VDC1 ________________ | VDC2 ________________ |
---|---|---|
VPN entity name | ||
NAT IP | ||
Private networks |
For example:
VDC name | VDC1 ________________ | VDC2 ________________ |
---|---|---|
VPN entity name | axsdTOaxsd2 | axsd2TOaxsd |
NAT IP | 10.200.100.8 | 10.200.100.23 |
Private networks |
|
|
To work with VPNs from connect private cloud to with public cloud, define the VPN entity site in private cloud first.
To create the first VPN entitysite:
- Go to Virtual datacenters → select a Virtual datacenter → Network → VPN
- Click the + Add button and enter the VPN details
The platform will create the VPN entitysite.
Include Page | ||||
---|---|---|---|---|
|
To create the other side of the VPN site in another VDC:
- Select the Virtual datacenter
- Add another VPN entity site using the remote network configuration of the first VPN site as the local values.
So in this example, the local network endpoint for the second VPN entity site would be 10.200.100.23 and the local network would be 192.168.200.0/24. The remote endpoint would be 10.200.100.8 and the remote network would be 192.168.0.0/24.
...
After you have created both sides of the VPN sites, on the VPNs tab, to check the connection in the network virtualization system, click the Check link in the VPN Status column, or when you edit the a VPN site.