Deploy an Edge Transit Gateway on Equinix Network Edge

This document provides instructions to deploy a primary Edge Transit Gateways on Equinix Network Edge. For an overview of Aviatrix Edge, see About Aviatrix Hybrid Cloud Edge.

Topology

The following diagram shows an example of network connectivity for Edge Transit Gateway to Transit Gateways in the cloud and Edge Spoke Gateway at remote site.

Prerequisites

Before you deploy an Edge Transit Gateway on the Equinix platform, ensure the prerequisite steps are complete.

Deploy the Primary Edge Transit Gateway (Equinix)

To deploy an Edge Transit Gateway, first you need to generate the cloud-init file in CoPilot, then deploy the Edge gateway in Equinix using the cloud-init file:

Modify the Edge Transit Gateway (Equinix)

Some fields cannot be changed once a gateway is created. Fields that cannot be changed are disabled.

Step 1: Gateway Configuration

Field	Description
Name	A name for the Edge Gateway. The name must begin with a letter, may include only letters, numbers, and dashes (excluding special characters or spaces), and must not exceed 50 characters in length.
Platform	The platform account where you want to deploy the Edge gateway. You can create and edit platform accounts in CoPilot by going to Cloud Fabric > Hybrid Cloud > Platforms tab.
Site	Identifies the edge location. You can select an existing name or enter a new name for the edge location.
ZTP File Type	This is set to cloud-init.
High Availability	High Availability is set to Off for the primary Edge gateway. You can turn High Availability to On after the primary Edge gateway is created.

Step 2: Interface Configuration

WAN Interface

Field	Description
Interface	This is set to the Edge Gateway’s logical interface. Adding multiple WAN interfaces is applicable when the Edge Gateway is set up for BGP underlay to cloud service provider (CSP) or other Edge Transit Gateways. Add an interface per CSP underlay (such as Direct Connect or Express Route). When Edge Gateway is not terminating CSP underlay, use one interface per Edge Gateway to connect to upstream router.
Interface Labels	A name to identify the WAN interface.
BGP	Enables BGP underlay connection to cloud service provider (CSP) or other Edge Transit Gateways on the WAN interface. Set BGP toggle On to set up BGP connection to cloud routers such as VGW, VNG, and Google cloud router. Edge Gateway WAN support for BGP underlay to CSP is supported for AWS, Azure, and GCP.
Interface Primary CIDR	The CIDR for the WAN interface. DHCP for dynamic IP address assignment is not supported. Interface CIDR must be in the format interface_ip/netmask (for example, 192.18.20.1/24). Interface CIDR cannot be link-local CIDR. If you need to create a BGP underlay connection to cloud service provider (CSP) with a link-local IP address, you must enter the link-local IP address in the Link-local Underlay CIDR setting of the WAN interface.
Interface Secondary CIDRs	The secondary CIDRs for the WAN interface. Interface CIDR must be in the format interface_ip/netmask (for example, 192.18.20.1/24). The secondary CIDRs are used for High Performance Encryption (HPE) attachment peering connections over a private network between the Edge Transit Gateway to another Edge Transit Gateway or Edge Spoke Gateway. The secondary IP addresses (based on the secondary CIDRs) are automatically assigned to create the peering connections. You can define /32 CIDR for specific secondary IP address. Secondary CIDR cannot be link-local CIDR.
Default Gateway IP	The Default Gateway IP address for the WAN interface. For CSP underlay, this is the remote side IP address of the BGP session on CSP VNG or VGW. If Link-Local Underlay CIDR is configured, the Default Gateway IP should be in the same subnet as the Link-Local Underlay CIDR, otherwise, it should be in the same subnet as the WAN Interface CIDR.

WAN BGP

Field	Description
Link-Local Underlay CIDR (GCP only)	The Link-Local Underlay CIDR is used for BGP underlay connections to cloud service provider (CSP). If you need to create a BGP underlay connection to CSP with a link-local IP address, you must provide the Link-Local Underlay CIDR for the WAN interface in the format of link_local_underlay_ip/netmask (for example 169.254.100.3/24). This is required for GCP. If terminating GCP Interconnect and using BGP underlay on Edge, provide the WAN Default Gateway of the peer IP address. If Link-Local Underlay CIDR is configured, the Default Gateway IP should be in the same subnet as the Link-Local Underlay CIDR, otherwise, it should be in the same subnet as the WAN Interface CIDR.
Local ASN	The Local AS Number of the Edge Gateway.
Remote ASN	The AS Number of the CSP side peering connection such as private VIF on VGW (AWS) and VNG ASN (Azure).
Local LAN IP	The IP address of the Edge Gateway. This is the local peering PTP IP for BGP.
Remote LAN IP	The IP address of the CSP VNG or VGW peering PTP IP. (GCP is not supported).
Password (optional)	The MD5 authentication key.

MGMT Interface

Field	Description
Interface	The Edge Gateway’s logical interface name.
Private Network	Leave this setting to Off. In the Equinix Platform, the MGMT interface of the Edge Transit Gateway is assigned the Public IP address that is allocated by Equinix.
Egress CIDR (Primary)	The Egress CIDR is the public IP address which the Management interface uses. In Equinix, the Public IP is auto assigned. Configure the Equinix provided public IP as the CIDR. The CIDR is then added to the Controller security group to allow incoming traffic from the Edge Gateway.
Egress CIDR (Secondary)	The Egress Public IP for the secondary Edge Gateway’s Management interface when High Availability is configured.

Step 3: Interface Mapping

The Interface Mapping shows how the Edge Gateway’s logical interface names maps to the Edge Gateway’s Linux interface names. These interface names are used in the Aviatrix log files and error messages. The mapping is provided for your reference when performing any diagnostic or troubleshooting on the Aviatrix Platform.

Field	Description
Interface	The Edge Gateway’s logical interface name.
Primary Gateway Ethernet Interface	The primary Edge Gateway’s Linux interface name.
Secondary Gateway Ethernet Interface	The secondary (HA) Edge Gateway’s Linux interface name. The secondary gateway interface mappings are shown only when high availability is configured for the primary Edge Gateway.

Next Steps

For high availability (HA) and redundancy, you can create and deploy HA Edge Transit Gateway. See Deploy a HA Edge Transit Gateway (Equinix).
For hybrid, multicloud, or LAN-side connectivity, you can attach the Edge Transit Gateway to multiple Aviatrix gateways. See Edge Gateway Attachments.
For remote site connectivity, you can connect the Edge Transit Gateway to remote devices. See Edge Gateway External Connection.

Concepts & Architecture

Guides

Reference

Deploy an Edge Transit Gateway on Equinix Network Edge

Topology

Prerequisites

Deploy the Primary Edge Transit Gateway (Equinix)

Modify the Edge Transit Gateway (Equinix)

Step 1: Gateway Configuration

Step 2: Interface Configuration

Step 3: Interface Mapping

Next Steps

​Topology

​Prerequisites

​Deploy the Primary Edge Transit Gateway (Equinix)

​Modify the Edge Transit Gateway (Equinix)

​Step 1: Gateway Configuration

​Step 2: Interface Configuration

​Step 3: Interface Mapping

​Next Steps

Topology

Prerequisites

Deploy the Primary Edge Transit Gateway (Equinix)

Modify the Edge Transit Gateway (Equinix)

Step 1: Gateway Configuration

Step 2: Interface Configuration

Step 3: Interface Mapping

Next Steps