Aviatrix Secure Edge on Equinix Network Edge Deployment Workflow

This document provides instructions for deploying Aviatrix Secure Edge on Equinix Network Edge.

For an overview of Aviatrix Secure Edge, see Aviatrix Secure Edge Overview.

Aviatrix Secure Edge Network Connectivity

The following diagram shows an example of network connectivity for Aviatrix Secure Edge Gateway to Transit Gateway in AWS. This topology shows Aviatrix Secure Edge connection to an upstream WAN router which is used to terminate CSP underlay private connections.

650

The topology below shows Aviatrix Secure Edge used to terminate CSP underlay private connections (which does not require upstream WAN router).

650
Aviatrix Secure Edge requires the latest version of Aviatrix Controller 7.1 and Aviatrix Secure Edge Image 7.1 to support BGP underlay connectivity to CSP.

Prerequisites

Before you deploy an Aviatrix Edge Gateway on the Equinix Platform:

  1. You must perform the prerequisite steps to set up an Equinix account, Platform account, and provide network access. See Prerequisites for Aviatrix Secure Edge Deployment for Equinix Network Edge.

  2. You should be familiar with Aviatrix Edge Gateway Interfaces and Ports and Protocols. See Edge Gateway WAN, LAN, VLAN, and Management Interface Support.

Aviatrix Secure Edge Deployment Workflow

This workflow provides steps to create a primary and secondary Edge Gateway in Equinix Network Edge, attach the Edge Gateways to a Transit Gateway, and connect the Edge Gateways to an external device.

Creating the ZTP Cloud-Init for the Primary Edge Gateway

The Edge Gateway cloud-init ZTP file is used to provision the Aviatrix Edge Gateway virtual machine and create the Edge Gateway in Equinix Fabric.

To create the Edge Gateway cloud-init ZTP file, follow these steps.

  1. In CoPilot, go to Cloud Fabric > Edge > Gateways tab.

  2. Click + Edge Gateway.

    Provide the following information.

    Parameter Description

    Name

    Name for the Edge Gateway.

    Platform

    The platform where you want to deploy the Edge Gateway.

    You can create and edit platforms in CoPilot by going to Cloud Fabric > Edge > Platforms tab.

    Site

    Select an existing name or enter a new name to identify the edge location.

    Site name cannot contain spaces.

    ZTP File Type

    This is set to cloud-init.

    High Availability

    High Availability is set to Off for the primary Edge Gateway.

    Deploying multiple Edge Gateways for the same site is supported. A maximum of 16 Edge Gateways is supported.

    In the Interface Configuration section, configure the WAN, LAN, and Management interfaces for the Edge Gateway.

    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.

    Click + WAN Interface, then provide the following information.

    Parameter Description

    Edge Gateway Interface

    This is set to eth0.

    Adding multiple WAN interfaces is applicable when Edge Gateway is used for BGP underlay to CSP. Add an interface per CSP underlay (such as Direct Connect or Express Route). Aviatrix recommends a maximum of 4 WAN interfaces per Edge Gateway.

    When Edge Gateway is not terminating CSP underlay, use one interface per Edge Gateway to connect to upstream router.

    DHCP for dynamic IP address assignment is not supported.

    Interface Labels

    Name to identify the WAN interface.

    BGP

    To enable BGP connection on the Edge Gateway, set this switch to On.

    WAN support for BGP underlay to CSP is currently only supported for AWS and Azure.

    Interface CIDR

    The CIDR for the WAN interface.

    Default Gateway IP

    The Default Gateway IP address for the WAN interface.

    If BGP is turned On, provide the following information:

    Parameter Description

    Local ASN

    The ASN of the Edge Gateway.

    Remote ASN

    The ASN of the CSP side peering connection such as private VIF on VGW (AWS) and VNG ASN (Azure).

    Local Tunnel IP

    The IP address of the Edge Gateway. This is the local peering PTP IP for BGP.

    Remote Tunnel IP

    The IP address of the CSP VNG or VGW peering PTP IP. (GCP is not supported).

    Password (optional)

    The MD5 authentication key.

    To add another WAN interface, click + WAN again and provide the required information.

    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.

    LAN Interface

    Click + LAN Interface, then provide the following information.

    Parameter

    Description

    Edge Gateway Interface

    This is set to eth1.

    DHCP for dynamic IP address assignment is not supported.

    Interface Labels

    Name to identify the LAN interface.

    Interface CIDR

    The CIDR for the LAN interface.

    Default Gateway IP

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

    Management Interface

    Click + MGMT interface. Leave the default settings and click Save.

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

    edge equinix mgmt interface

    To create the ZTP cloud-init image file, click Save and Download Configuration.

    If a required field is missing, the interface tab is highlighted to indicate there is an error.

    edge create error message

    Below is an example WAN, LAN, and MGMT configuration for Edge Gateway with BGP underlay to CSPs.

    edge equinix wan interface
    edge equinix lan interface
    edge equinix mgmt interface

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

    The cloud-init file is valid for 24 hours after you create it, so you must launch an Edge VM on Equinix platform within that time, as you cannot download it again and will have to recreate the cloud-init file.

Creating the ZTP Cloud-Init for the Secondary Edge Gateway (Equinix Platform)

  • When creating the highly available Edge Gateway, the primary Edge Gateway cannot have BGP underlay or BGP over LAN external connections.

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

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

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

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

  4. In the Interface Configuration section, configure the WAN, LAN, and Management interfaces of the secondary (HA) Edge Gateway.

    WAN Interface

    Click + WAN Interface, then provide the following information.

    Parameter Description

    Edge Gateway Interface

    This is set to eth0.

    Adding multiple WAN interfaces is applicable when Edge Gateway is used for BGP underlay to 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.

    DHCP for dynamic IP address assignment is not supported.

    Interface Labels

    A name to identify this WAN interface.

    BGP

    To enable BGP on the Edge Gateway, set this switch to On.

    Interface CIDR

    The CIDR for the WAN interface.

    Default Gateway IP

    The Default Gateway IP address for this WAN interface.

    Public IP

    The WAN interface’s egress Public IP address.

    If BGP is turned On, provide the following information:

    Parameter Description

    Local ASN

    The ASN of the Edge Gateway.

    Remote ASN

    The ASN of the CSP side peering connection such as private VIF on VGW (AWS) and VNG ASN (Azure).

    Local Tunnel IP

    The IP address of the Edge Gateway. This is the local peering PTP IP for BGP.

    Remote Tunnel 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.

    LAN Interface

    Click LAN, then provide the following information.

    Parameter

    Description

    Edge Gateway Interface

    This is set to eth1.

    DHCP for dynamic IP address assignment is not supported.

    Interface Labels

    Enter a name to identify this LAN interface.

    BGP

    For BGP over LAN, set this switch to turn BGP mode On.

    Interface CIDR

    The CIDR for the LAN interface.

    Default Gateway IP

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

    Management Interface

    Click + MGMT interface. Leave the default settings and click Save.

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

    edge equinix ha mgmt interface

    To create the ZTP cloud-init image file, click Save and Download Configuration.

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

    The cloud-init file is valid for 24 hours after you create it, so you must launch an Edge VM on Equinix platform within that time, as you cannot download it again and will have to recreate the cloud-init file.

Launching the Edge Gateway in Equinix Network Edge

To launch the Aviatrix Edge Gateway in Equinix Network Edge, see Create an Aviatrix Edge in the Equinix documentation. Demo video: Step-by-Step Guide to Deploy Aviatrix Secure Edge on Equinix Network Edge on Vimeo.

You will need to create an Access Control List Template to allow CoPilot access to the Aviatrix Edge virtual device.

Once the Aviatrix Edge virtual device is created and provisioned, an email is sent to the notification email you provided informing that the Aviatrix Edge virtual device is provisioned.

Creating the Access Control List Template for CoPilot

The Access Control List Template defines the inbound rules for the Aviatrix Edge Gateway virtual device to allow specific inbound traffic. Aviatrix Controller and CoPilot needs to communicate with the Aviatrix Edge Gateway. Inbound traffic from the Controller and CoPilot must be allowed on the Edge Gateway virtual device.

Controller’s IP address will be automatically allowed based on the cloud-init.

To define the inbound rules for CoPilot, in the CreateNew Access Control List Management Template page, provide the following information.

  1. In the Basic Details section, enter a name for the Access Control List template and a description.

  2. In the Inbound Rules section, enter the following information:

    1. For IP Address Subnet, enter the CoPilot public or private IP address.

    2. For Protocol, select IP from the drop-down.

    3. For Description (Optional), enter a description for this rule.

    4. Click Add Rule.

    edge equinix inbound rules
  3. To create the Access Control List template, click Create Template.

Configuring the Edge Gateway Management Egress IP Address

The Management Egress IP address of the Aviatrix Edge Gateway virtual device must be updated from the Aviatrix CoPilot so that the Security Group is updated with the correct Egress IP address.

  1. Locate the public IP assigned by Equinix during Aviatrix Edge virtual device creation.

    1. From Equinix Fabric Portal, go to Network Edge > Virtual Device Inventory > Details and locate the Public IP address of the device.

      edge virtual device ip
  2. In Aviatrix CoPilot, navigate to Cloud Fabric > Edge > Gateways tab.

  3. In the table, locate the Edge Gateway and click its Edit icon on the right.

  4. In the Edit Edge Gateway dialog box, scroll to Interface Configuration section, and click MGMT.

  5. Update the Egress CIDR with the Public IP from the Equinix Fabric Portal.

    edge management egress ip
  6. Click Save.

Attaching the Edge Gateway to the Transit Gateway

Before you attach the Edge Gateway to the Transit Gateway, ensure the Local ASN Number is configured on both gateways.

You can attach an Edge Gateway to multiple Transit Gateways. Each attachment can be configured with different parameters, such as connecting interfaces, connection over private or public network, high-performance encryption, and Jumbo Frame.

  • To create a High Performance Encryption mode attachment, make sure the Transit Gateway is created with High Performance Encryption enabled.

  • If you want Jumbo Frame enabled on the Edge Gateway, make sure to enable Jumbo Frame on the Edge Gateway before you attach it to the Transit Gateway.

In Aviatrix CoPilot:

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

  2. Locate the Edge Gateway, click the three dot vertical menu on the right, and select Manage Transit Gateway Attachment.

    edge-attach-edge-to-transit

    Click + Transit Gateway Attachment, then provide the following information.

    Field Description

    Transit Gateway

    From the dropdown menu, select the Transit Gateway to attach to the Edge Gateway.

    Connecting Edge Interfaces

    From the dropdown menu, select the WAN interface connection(s) to the Transit Gateway.

    Multiple WAN interfaces is supported.

    In the Advanced section, set the advanced gateway settings that apply.

    Field Description

    Attach over Private Network

    If the Edge WAN connection to the Transit Gateway is over a private network, set this toggle to On.

    Leave it Off if the connection is over the public internet.

    Jumbo Frame

    If you want to use Jumbo Frames for the Transit-to-Edge Gateway connection, set this toggle to On.

    High Performance Encryption

    If you want to enable high-performance encryption for the Transit-to-Edge Gateway connection, set this toggle to On.

    In Number of Tunnels, enter the number of HPE tunnels to create.

    • For HPE over private network, setting number of tunnels count to 0 creates maximum tunnels based on the peering gateway size.

    • For HPE over public network, the number of tunnels count supported range is between 2 and 20.

    To attach the Edge Gateway to another Transit Gateway, click + Transit Gateway Attachment again and provide the required information.

  3. Click Save.

Connecting the Edge Gateway to an External Device (BGP over LAN)

To connect the Edge Gateway to the LAN router using BGP over LAN, follow these steps.

  1. Navigate to Networking > Connectivity > External Connections (S2C) tab.

  2. Click + External Connection.

    Provide the following information.

    Parameter Description

    Name

    Name to identify the connection to the LAN router.

    Connect Local Gateway To

    Select External Device radio button, then from the dropdown menu, select BGP over LAN.

    Local Gateway

    The Edge Gateway to connect to the LAN router.

    Local ASN

    The Local AS number the Edge Gateway will use to exchange routes with the LAN router.

    This is automatically populated if the Edge Gateway is assigned an ASN already.

    Remote ASN

    The BGP AS number configured on the LAN router.

    Click + Connection and provide the following information.

    Parameter Description

    Remote LAN IP

    The IP address for the LAN router.

    Local LAN IP

    This is automatically populated with the Edge Gateway LAN interface IP address.

    edge external connection
  3. Click Save.