> ## Documentation Index > Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt > Use this file to discover all available pages before exploring further. # Prerequisites for Edge Spoke and Edge Transit Deployment on Edge Platforms > The following are the prerequisites to deploy an Aviatrix Edge Spoke and Edge Transit Gateways on the Aviatrix Edge Platform, Equinix Network Edge, Megaport, and Aviatrix Edge Spoke on-premises VMware ESXi and KVM. This section covers the prerequisites to deploy Aviatrix Edge Spoke and Edge Transit Gateways on: * Aviatrix Edge Platform (AEP) * Equinix Network Edge * Megaport Virtual Edge * Self-Managed On-Premises VMware ESXi and KVM (**Edge Spoke only**) This section is for Edge Spoke and Edge Transit Gateways deployment on Aviatrix Edge Platform. ## 1. Procure and Onboard the Edge Device Before you can deploy an Aviatrix Edge Spoke Gateway, you must procure and onboard your edge device onto the Aviatrix Edge Platform. For more information, see Installing Edge OS and Onboarding Dell Hardware. ## 2. Obtain Edge Gateway Interface IP Addresses The Edge Spoke Gateway on the Aviatrix Edge Platform supports one WAN, one LAN, and one Management interface. The Edge Transit Gateway on the Aviatrix Edge Platform supports one Management and up to 4 WAN interfaces. You will need to provide the following information during Edge Gateway creation for your primary and secondary HA Edge Gateways. | WAN Interface | Applies to | Description | | ------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Interface CIDR | Edge Spoke | The CIDR for the WAN interface. Interface CIDR must be in the format *interface\_ip/netmask* (for example, 192.18.20.1/24). | | Interface Primary CIDR | Edge Transit | 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 | Edge Transit | 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 | Edge Spoke, Edge Transit | 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 | Edge Spoke, Edge Transit | The public IP for the WAN interface. The public IP of the WAN interface is used for peering connections over the public network. | | LAN Interface | Applies to | Description | | -------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Interface CIDR | Edge Spoke | The native VLAN interface IPv4 address. This interface is where untagged packets are sent. | | IPv6 CIDR | Edge Spoke | The native VLAN interface IPv6 address. This interface is where untagged packets are sent. | | VRRP Gateway IP | Edge Spoke | The Virtual IP for the VRRP Gateway, when VRRP is enabled. | | Default Gateway IP | Edge Spoke | The Default Gateway IPv4 address for the native VLAN interface. | | Default Gateway IPv6 | Edge Spoke | The default Gateway IPv6 address for the LAN interface when Support for IPv6 is enabled. Not required if not using Virtual Router Redundancy Protocol (VRRP). | | VLAN ID | Edge Spoke | The VLAN ID of the VLAN segment. VLAN ID must be a number between 2 and 4092. | | VLAN Interface CIDR | Edge Spoke | The VLAN IP address of the VLAN segment. | | Default Gateway IP | Edge Spoke | The Default Gateway IP address of the VLAN segment. | | MGMT Interface | Applies to | Description | | ----------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | IP Assignment | Edge Spoke, Edge Transit | The MGMT interface defaults to **DHCP**. This setting cannot be changed. The Edge Gateway will automatically NAT out of the physical MGMT interface of the edge node when using the Aviatrix Edge platform. Please see the Known Issue regarding the Management interface IP assignment. | | Private Network | Edge Spoke | Leave this setting to **Off**. The Edge Gateway on the edge hardware requires public Internet reachability to connect to the Aviatrix Controller and Aviatrix Edge infrastructure in the cloud. | | Egress CIDR (Primary) | Edge Spoke, Edge Transit | The Egress CIDR is the public IP address which the Management interface uses. If the Public IP is used from Edge Gateway Management interface to establish connectivity to Aviatrix Controller, then configure the Public IP as the CIDR. The CIDR is then added to the Controller security group to allow incoming traffic from the Edge Gateway. | | Egress CIDR (Secondary) | Edge Spoke, Edge Transit | The Egress Public IP for the secondary Edge Gateway's Management interface when High Availability is configured. | ## 3. Provide Network Access Aviatrix Edge Spoke and Edge Transit Gateways require outbound access to communicate with the Aviatrix Platform. 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](https://aviatrix.zendesk.com/hc/en-us/articles/4417312119437-Aviatrix-Products-Required-Access-for-External-Sites) on the Aviatrix Customer Support website. This section is for Edge Spoke and Edge Transit Gateways deployment on Equinix Network Edge. ## 1. Obtain an Equinix Fabric Account If you do not already have an Equinix Fabric account, contact your Equinix representative or visit their website to create an account. ## 2. Set Up the Network Service Provider Platform Account To deploy Aviatrix Edge Gateways on Equinix Network 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](https://aviatrix.zendesk.com/hc/en-us/articles/4417312119437-Aviatrix-Products-Required-Access-for-External-Sites) on the Aviatrix Customer Support website. ## 4. Obtain Edge Gateway Interface IP Configurations The Edge Spoke Gateway on the Equinix platform supports one LAN, one MGMT, and up to eight WAN interfaces. The Edge Transit Gateway on the Equinix Network Edge supports one Management and up to 9 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** | **Applies to** | **Description** | | ------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Interface Primary CIDR | Edge Spoke, Edge Transit | 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 | Edge Transit | 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 | Edge Spoke, Edge Transit | 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 | Edge Spoke, Edge Transit | 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 set up BGP underlay connection to cloud service provider (CSP), you will need to provide the following information. | **BGP Configuration** | **Applies to** | **Description** | | ----------------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Link-Local Underlay CIDR (GCP only) | Edge Spoke, Edge Transit | 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 | Edge Spoke, Edge Transit | The AS Number of the CSP side peering connection such as private VIF on VGW (AWS) and VNG ASN (Azure). | | Remote LAN IP | Edge Spoke, Edge Transit | The IP address of the CSP VNG or VGW peering PTP IP. (GCP is not supported). | | **LAN Interface** | **Applies to** | **Description** | | -------------------- | -------------- | ------------------------------------------------------------------------------------------------- | | Interface CIDR | Edge Spoke | The CIDR for the LAN interface. **DHCP** for dynamic IP address assignment is not supported. | | IPv6 CIDR | Edge Spoke | The IPv6 CIDR for the LAN interface. **DHCP** for dynamic IP address assignment is not supported. | | Default Gateway IP | Edge Spoke | (Optional) The Default Gateway IP address for the LAN interface. | | Default Gateway IPv6 | Edge Spoke | (Optional) The Default Gateway IPv6 address for the LAN interface. | | **MGMT Interface** | **Applies to** | **Desciption** | | -------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Management Interface IP | Edge Spoke | The Management IP address (in the format of *management\_ip\_address/netmask*). Not required for DHCP. | | Management Default Gateway | Edge Spoke | The Default Gateway IP address for the Management interface. Not required for DHCP. | | Management Egress IP | Edge Spoke | The Management Egress IP address to be allowed in the Controller Security Group. | | Primary DNS Server | Edge Spoke | The Primary DNS server IP address for the Management interface. Not required for DHCP. | | Secondary DNS Server | Edge Spoke | (Optional) The Secondary DNS server IP address for the Management interface. Not required for DHCP. | | Egress CIDR (Primary) | Edge Transit | The Egress CIDR is the public IP address which the Management interface uses. In Equinix, the Public IP is auto assigned. Configure the Equinix provided public IP as the CIDR. The CIDR is then added to the Controller security group to allow incoming traffic from the Edge Gateway. | | Egress CIDR (Secondary) | Edge Transit | The Egress Public IP for the secondary Edge Gateway's Management interface when High Availability is configured. | This section is for Edge Spoke and Edge Transit Gateways deployment 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](https://docs.megaport.com/setting-up/registering/) 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](https://aviatrix.zendesk.com/hc/en-us/articles/4417312119437-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. Aviatrix Edge Transit Gateway requires at least one WAN and one MGMT interface, additional three 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** | **Applies to** | **Description** | | ------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Interface Primary CIDR | Edge Spoke, Edge Transit | 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 | Edge Transit | 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 | Edge Spoke, Edge Transit | 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 | Edge Spoke, Edge Transit | 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 the Cloud Service Provider (CSP), you will need to provide the following information. | **BGP Configuration** | **Applies to** | **Description** | | ----------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Link-Local Underlay CIDR (GCP only) | Edge Spoke, Edge Transit | 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 | Edge Spoke, Edge Transit | The AS Number of the CSP side peering connection such as private VIF on VGW (AWS) and VNG ASN (Azure). | | Remote LAN IP | Edge Spoke, Edge Transit | The IP address of the CSP VNG or VGW peering PTP IP. (GCP is not supported). | | **LAN Interface** | **Applies to** | **Desciption** | | ------------------ | -------------- | ---------------------------------------------------------------------------------------------------- | | Interface CIDR | Edge Spoke | The CIDR for the LAN interface.

DHCP for dynamic IP address assignment is not supported. | | Default Gateway IP | Edge Spoke | (Optional) The Default Gateway IP address for the LAN interface. | | **MGMT Interface** | **Applies to** | **Desciption** | | -------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Management Interface IP | Edge Spoke | The Management IP address (in the format of *management\_ip\_address/netmask*).

Not required for DHCP. | | Management Default Gateway | Edge Spoke | The Default Gateway IP address for the Management interface.

Not required for DHCP. | | Management Egress IP | Edge Spoke | The Management Egress IP address to be allowed in the Controller Security Group. | | Primary DNS Server | Edge Spoke | The Primary DNS server IP address for the Management interface.

Not required for DHCP. | | Secondary DNS Server | Edge Spoke | (Optional) The Secondary DNS server IP address for the Management interface.

Not required for DHCP. | | Egress CIDR (Primary) | Edge Transit | The Egress CIDR is the public IP address which the Management interface uses. This is the Public IP of the Edge VM assigned by Megaport, which can be obtained once Megaport Internet VXC is connected to the MGMT interface of the Edge Gateway. The CIDR is then added to the Controller security group to allow incoming traffic from the Edge Gateway. | | Egress CIDR (Secondary) | Edge Transit | The Egress Public IP for the secondary Edge Gateway's Management interface when High Availability is configured. | This section is for Edge Spoke Gateway deployment on self-managed on-premises VMware ESXi and KVM. ## 1. Aviatrix Controller Requirement Upgrade to latest version of the Aviatrix Controller 7.1 or later. See Overview of the Aviatrix Controller and Gateways Upgrade . ## 2. Ensure Edge Gateway Requirements Ensure that you have sufficient resources to run the Edge Gateway and the network port access for the Edge Gateway to communicate with the Aviatrix Controller, Aviatrix CoPilot, and the Aviatrix Transit Gateway. See About Aviatrix Edge Gateway Requirements . ## 3. Ensure VMware ESXi and KVM Requirements Ensure the following requirements are met. * VMware ESXi * OVA image for VMware ESXi (see Downloading the Aviatrix Secure Edge Image File). * VMware ESXi 6.7 or 7.0.1 * (Optional) VMware vCenter Server For information about installing VMware products, refer to the VMware product documentation. * KVM * QCOW2 image for KVM (see Downloading the Aviatrix Secure Edge Image File). * KVM server running in Linux Bare Metal Server * CentOS 7.6-1810 * QEMU Version 1.5.3, Release 160.el7\_6.3 For information about installing KVM products, refer to KVM product documentation. ## 4. Download the Aviatrix Secure Edge Image File Before you begin the deployment of the Edge Gateway, download the Aviatrix Secure Edge image file from the Aviatrix Support Portal. You will use the image file to deploy the Aviatrix Secure Edge virtual machine. 1. Log in to the Aviatrix Support Portal: [https://support.aviatrix.com](https://support.aviatrix.com) 2. From the top navigation menu, click on **Downloads**. 3. Answer the questions that are presented, then click **Download** next to the image that you want. The Aviatrix Secure Edge image file downloads to your Downloads folder. ## 5. Obtain Edge Gateway Interface IP Configurations Obtain the Edge Gateway interface configuration details. You will need to provide the following information during Edge Gateway creation to configure the Edge Gateway interfaces. | Setting | Applies to | Description | | ---------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------- | | WAN Interface IP/Mask | Edge Spoke | The WAN IP address. | | WAN Default Gateway | Edge Spoke | The Default Gateway IP address for the WAN interface. | | LAN Interface IP/Mask | Edge Spoke | The LAN IP address. | | LAN Default Gateway | Edge Spoke | The Default Gateway IP address for the LAN interface. | | Management Interface IP/Mask | Edge Spoke | The Management IP address.

Not required for DHCP. | | Management Default Gateway | Edge Spoke | The Default Gateway IP address for the Management interface.

Not required for DHCP. | | Management Egress IP | Edge Spoke | The Management Egress IP address to be allowed in the Controller Security Group. | | Primary DNS Server | Edge Spoke | The Primary DNS server IP address for the Management interface.

Not required for DHCP. | | Secondary DNS Server | Edge Spoke | The Secondary DNS server IP address for the Management interface.

Not required for DHCP. | | VRRP | Edge Spoke | The VRRP IP address.

Not required if not using VRRP.

VRRP can be configured only if HA gateway is configured. | | VLAN ID | Edge Spoke | The VLAN ID for each VLAN segment. | | VLAN IP | Edge Spoke | The VLAN IP address for each VLAN segment. | | VLAN Default Gateway | Edge Spoke | The Default Gateway IP address for each VLAN segment. | ## 6. Ensure the Transit Gateway BGP ASN is Configured For Edge Gateway attachment to the Aviatrix Transit Gateway, ensure the Transit Gateway BGP ASN is configured. High-Performance Encryption (HPE) is optional for Edge Gateway attachments.