> ## 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 Transit Gateway Deployment on Equinix Network Edge > The following are the prerequisites to deploy an Aviatrix Edge Transit Gateway on Equinix Network Edge. The following are the prerequisites to deploy an Aviatrix Edge Transit Gateway 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 Equinix Platform Account To enable access to provision the edge virtual device on the Equinix platform, you will need to first set up an Equinix 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 Configurations 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 your 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. | | 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. | | 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. | ### IPv6 on WAN (Controller 9.0+) For Aviatrix Edge Transit Gateways on Equinix, enable IPv6 on the **WAN** interface in **Step 2: Interface Configuration** during Gateway creation. On **WAN 0**, enable **Support for IPv6** and provide **Interface IPv6 CIDR** and **Default Gateway IPv6** when you deploy dual-stack connectivity. | Field | Description | | -------------------- | -------------------------------------------------------------------------- | | Support for IPv6 | Enables IPv6 on the WAN interface. | | Interface IPv6 CIDR | IPv6 subnet CIDR for the WAN interface (for example, 2001:db8:85a3::1/64). | | Default Gateway IPv6 | IPv6 default gateway address for the WAN interface. | If you need to setup BGP underlay connection to the 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). | For the Management interface, you will need the Egress IP. | **Management Interface** | **Description** | | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Egress CIDR (Primary) | 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) | The Egress Public IP for the secondary Edge Gateway's Management interface when High Availability is configured. |