Aviatrix Gateway to Aviatrix Gateway
This section describes how to configure an IPsec tunnel between an Aviatrix Gateway and another Aviatrix Gateway using Aviatrix Site2Cloud.
| There are only a couple of reasons to use Site2Cloud when connecting two Aviatrix Gateways: |
-
You have overlapping CIDR blocks but need to peer two VPC/VNets.
-
The two Aviatrix Gateways are not part of the same Controller (i.e., one is at your customer and the other one is in your environment).
If you don’t have one of these use cases, you can likely use Aviatrix Encrypted Peering.
Deployment
There are two Aviatrix Gateways for this scenario. Since you are using the Site2Cloud feature, you must configure each side of the tunnel individually.
In this procedure the gateways are referred to as Gateway A and Gateway B. You can pick either gateway to be Gateway A or Gateway B.
Configure Tunnel from Gateway A to Gateway B
-
Follow the steps in Site2Cloud Tutorial. Use this table for specific field values.
Field Description VPC ID/VNet Name
Select Gateway A VPC or VNet from the drop down.
Remote Gateway Type
Aviatrix
Registered
Leave unchecked
Primary Cloud Gateway
Select Gateway A from the list
Remote Gateway IP Address
Enter the public IP address of Gateway B.
Pre-shared Key
Leave blank and Aviatrix will generate
-
Once complete, select the newly created tunnel in the list.
-
Select Aviatrix for Vendor, UCC for Platform and 1.0 for Software.
-
Click Download Configuration. You will use this file to create the other side of the tunnel.