Prerequisites for Edge Spoke Gateway Deployment on Megaport Virtual Edge

The following are the prerequisites to deploy an Aviatrix Edge Gateway on Megaport Virtual Edge.

1. Obtain a Megaport Portal Account

If you do not already have a Megaport Portal account, refer to Creating an Account in the Megaport documentation.

2. Set Up the Network Service Provider Platform Account

To deploy Aviatrix Edge Gateways on Megaport Virtual Edge, you will need to first set up a Network Service Provider platform account in CoPilot. To set up the platform account, see Setting up Accounts for Edge Platforms .

3. Provide Network Access

Aviatrix Edge Gateway requires outbound access to communicate with the Aviatrix Controller, Aviatrix CoPilot, and other Aviatrix Gateways. You must allow access on the specified ports on your firewall. For all Edge Gateway outbound access requirements, see Aviatrix Products: Required Access for External Sites on the Aviatrix Customer Support website.

4. Obtain Edge Gateway Interface Configuration Information

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. For each WAN interface that you want to configure, you will need to provide the following information during Edge gateway creation for the primary and secondary HA Edge gateways.

WAN Interface	Description
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 you need to setup BGP underlay connection to cloud service provider (CSP), you will need to provide the following information.

BGP Configuration	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).
Remote LAN IP	The IP address of the CSP VNG or VGW peering PTP IP. (GCP is not supported).

LAN Interface	Desciption
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.

MGMT Interface	Desciption
Management Interface IP	The Management IP address (in the format of management_ip_address/netmask). Not required for DHCP.
Management Default Gateway	The Default Gateway IP address for the Management interface. Not required for DHCP.
Management Egress IP	The Management Egress IP address to be allowed in the Controller Security Group.
Primary DNS Server	The Primary DNS server IP address for the Management interface. Not required for DHCP.
Secondary DNS Server	(Optional) The Secondary DNS server IP address for the Management interface. Not required for DHCP.

Concepts & Architecture

Guides

Reference

Prerequisites for Edge Spoke Gateway Deployment on Megaport Virtual Edge

1. Obtain a Megaport Portal Account

2. Set Up the Network Service Provider Platform Account

3. Provide Network Access

4. Obtain Edge Gateway Interface Configuration Information

​1. Obtain a Megaport Portal Account

​2. Set Up the Network Service Provider Platform Account

​3. Provide Network Access

​4. Obtain Edge Gateway Interface Configuration Information

1. Obtain a Megaport Portal Account

2. Set Up the Network Service Provider Platform Account

3. Provide Network Access

4. Obtain Edge Gateway Interface Configuration Information