Create the Primary Edge Spoke Gateway ZTP Cloud-Init File (Megaport)

The Edge gateway cloud-init ZTP file is used to provision the Edge gateway virtual machine and create the Edge Gateway in Megaport Virtual Edge (MVE).

To create the primary Edge Gateway, follow these steps.

Step 1: Gateway Configuration

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

  2. Click Spoke Gateways, then click +Spoke Gateway and provide the following information.

    Field

    Description

    Name

    A name for the Edge Gateway.

    The name must start with a letter and contain only letters, numbers, and dashes (no special characters or spaces) and it can be up to 50 characters long.

    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.

    See Edge site.

    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.

    See Edge Spoke Gateway High Availability.

  3. Click Next to configure the edge gateway interfaces.

Step 2: Interface Configurations

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

Configuring the WAN Interface

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

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

  3. If BGP is turned On, in Gateway Configuration, enter the Local AS Number of the Edge Gateway.

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

Configuring the LAN Interface

To configure the Edge Gateway LAN interface, click + LAN Interface, 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 Megaport fabric, the MGMT interface of the Edge Gateway is assigned the Public IP address that is allocated by Megaport.

  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 Megaport 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 image file expires after 24 hours. You cannot download it again and will have to repeat the above steps to recreate the file. You must launch an Edge MVE on the Megaport platform and deploy the Edge Gateway within the 24 hours.

Step 3: Interface Mapping

Interface Mapping is provided for reference purposes (view only).

The table shows a mapping of the Edge Gateway’s logical interface names to the Edge Gateway’s Linux interface names. These interface names are used in the Aviatrx log files and error messages. When performing diagnostic or troubleshooting on the Aviatrix Platform, you can refer to this mapping for the interface name.

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.