Deploy a HA Edge Transit Gateway (Megaport)

  • 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 on the same site without HA configuration.

  • Edge Transit Gateway high availability on the Megaport platform is supported on the latest Aviatrix Controller release version.

To create the secondary HA Edge Transit Gateway, first you need to set the high availability mode for the primary Edge Transit Gateway, then configure the secondary HA gateway settings. The workflow below guides you through these steps.

Step1: Set the Primary Edge Gateway High Availability Mode

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

  2. Click Transit Gateways.

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

  4. In Gateway Configuration, from the High Availability dropdown menu, select Active-Active mode.

  5. Click Next and configure the gateway interfaces.

Step 2: Configure the Secondary Edge Gateway Interfaces

You can configure multiple WAN interfaces on the Edge gateway. Megaport MVE supports a maximum of 5 interfaces. Aviatrix Edge Transit Gateway requires at least one WAN and one MGMT interface, additional three interfaces can be WAN interfaces.

Configure the WAN Interfaces

To configure the secondary Edge Gateway’s WAN interfaces:

  1. In Interface Configuration, 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) 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.

  2. If BGP is turned On, provide the following information:

    Field

    Description

    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.

Configure the Management Interface

To configure the secondary Edge Transit Gateway Management interface:

  1. In Interface Configuration, click MGMT.

  2. Leave the default settings and click Next.

    Leave the Private Network setting to Off. In Megaport, the MGMT interface of the Edge Transit Gateway is assigned the public IP address that is allocated by Megaport.

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

  3. Click Next to view the interface mapping.

Step 3: Interface Mapping

Interface Mapping shows how the Edge Gateway’s logical interface names maps to the Edge Gateway’s Linux interface names.

Use the interface mapping as a reference when performing any diagnostic or troubleshooting on the Aviatrix Platform. These interface names are used in the Aviatrx log files and error messages.

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.

Backup Peering

In Backup Peering:

  1. Select a WAN interface to use to establish the attachment peering between the primary and HA Edge Transit Gateway.

  2. Select whether the attachment is over a Private Network or Public Network.

  3. Click Done to create the ZTP cloud-init image file. 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 and deploy the Edge Gateway on your Megaport platform within that time. You will not be able to download the cloud-init file again and will have to recreate a new file.

Step 4: Deploy the Edge Gateway in MVE using the cloud.init file

See, Deploy the Edge Gateway in Megaport Virtual Edge.

Step 5: Verify the Edge Gateway Creation

See, Verify the Edge Gateway Creation.