Deploy a HA Edge Spoke Gateway (Equinix)

  • Before you can create the secondary highly available (HA) Edge Gateway, the primary Edge Gateway must be deployed and its status must be Up.

  • When creating the HA Edge Gateway, the primary Edge Gateway cannot have BGP underlay or BGP over LAN external connections. This does not apply when multiple Edge Gateways are created in the same site without HA configuration.

  • Edge Gateway high availability on the Equinix Platform is supported on the latest Aviatrix Controller release version.

To create a highly available secondary (HA) Edge Gateway, follow these steps.

Step 1: Gateway Configuration

  1. Go to Cloud Fabric > Hybrid Cloud > Edge Gateways tab.

  2. Click Spoke Gateways

  3. In the table, locate the primary Edge Gateway for which you want to create the HA gateway and click its Edit icon.

  4. In Edit Edge Gateway, from the High Availability dropdown menu, select Active-Active or Active-Standby mode.

  5. Click Next to configure the edge gateway interfaces.

Step 2: Interface Configuration

By default, an Edge Spoke Gateway has three interfaces: one WAN interface, one LAN interface, and one Management interface.

Configuring the WAN Interface

You can configure multiple WAN interfaces on the Edge Gateway. While up to 8 WAN interfaces is supported, Aviatrix recommends a maximum of 4 WAN interfaces per Edge Gateway.

To configure the WAN interface, click + WAN Interface, then provide the following information.

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).

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) 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.

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.

Public IP

The public IP for the WAN interface.

The public IP of the WAN interface is used for peering connections over the public network.

If BGP is turned On, provide the following information:

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.

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.

To change or update the Edge Gateway WAN connectivity to Transit Gateway, you will need to first detach the Edge-to-Transit gateway attachment, if there is an attachment.

Configuring the LAN Interface

To configure the LAN interface, click LAN, then provide the following information.

Field

Description

Interface

The Edge Gateway’s logical interface name.

Interface Labels

Name to identify the LAN interface.

Interface CIDR

The CIDR for the LAN interface.

DHCP for dynamic IP address assignment is not supported.

Default Gateway IP

(Optional) The Default Gateway IP address for the LAN interface.

Configuring the Management Interface

To configure the Edge Gateway Management interface:

  1. Click MGMT, then click + MGMT Interface.

  2. Leave the default settings and click Save.

    Leave the Private Network setting to Off. In the Equinix Platform, the Management interface of the Edge Gateway is assigned the public IP address that is allocated by Equinix.

  3. To create the ZTP cloud-init image file, click Done.

    CoPilot downloads the ZTP cloud-init file to your downloads folder.

    Next, log in to your Equinix Portal and deploy the Edge Gateway VM instance and attach the cloud-init image file to complete the Edge Gateway creation and authentication with the Aviatrix Controller.

    The cloud-init file is valid for 24 hours after you create it, so you must launch an Edge VM and deploy the Edge Gateway on the Equinix platform within that time. You will not be able to download the file again and will have to repeat the steps to recreate a new cloud-init file.

Step 3: Deploy the Edge Gateway in Equinix using the cloud.init file

Step 4: Verify the Edge Gateway Creation