About Edge Transit Gateway Settings

This document describes the Edge Transit Gateway settings that you need to configure to create the gateway.

Site

Site refers to an edge site or edge location. Multiple sites can be created for the same physical site. When Edge Gateway instances are deployed, the gateway instances are associated with the site name for route propagation.

When deploying an Edge Gateway, follow these guidelines to decide whether to use an existing site or create a new one.

  • Use an existing site:

    • If you want to have Active-Standby high availability on 2 Edge Gateways (assign the same site).

  • Edge Gateways with the same site:

    • Can only join the same domain.

    • Can have the same or different local ASN.

  • When multiple Edge Gateways are attached to a common Transit Gateway, the Transit Gateway will propagate routes from Edge Gateways with the same site to other Edge Gateways with a different site but will not propagate routes from the Edge Gateways to other Edge Gateways with the same site.

ZTP File Type

Zero-Touch Provisioning (ZTP) enables network engineers to remotely deploy and provision network devices at remote locations.

ISO ZTP file is supported for VMWare ESXi and open-source Kernel-based Virtual Machine (KVM) deployments.

cloud-init ZTP file is supported for Equinix and Megaport deployments.

The following cloud-init modules have been verified for Edge Gateway deployments: users, write_files, and chpasswd.

High Availability

When deploying a high availability Edge Transit Gateway at a site for redundancy, you have the optionto select Active-Active mode for connectivity between the Edge Transit Gateway and Transit Gateways in the cloud and Edge Spoke Gateways.

In Active-Active mode, all peering connections established between the Edge Transit Gateway and Transit Gateways in the cloud and Edge Spoke Gateways are in active-active mode and perform load sharing and forward network traffic.

Interfaces

WAN Interface

The network interface to connect to the Aviatrix Transit Gateways in the cloud and Aviatrix Edge Spoke Gateways. Requires a default gateway and Layer 3 reachability to Transit Gateway Private or Public IP.

Management Interface

The network interface to connect to the Aviatrix Controller. Requires a default gateway, DNS access and Internet access to Aviatrix Controller, Aviatrix software download, and tracelog upload. Internet access is not required, if Management interface is over a private network.

Jumbo Frame

Jumbo Frame improves the performance throughput between an Aviatrix Transit Gateway and Edge Gateway. Jumbo Frame is supported on all Edge platforms (Equinix, Megaport, Aviatrix Edge, and Self Managed).

There are two Jumbo Frame configuration settings for an Edge Gateway: one for the Edge Gateway and another when you create an Edge Gateway attachment.

  • You must first enable Jumbo Frame on the Edge Transit Gateway. Enabling Jumbo Frame on the Edge Transit Gateway will add “jumbo” MSS value (8870) for TCP MSS clamping in iptables.

  • When you attach an Edge Transit Gateway to a Transit Gateway in cloud, you can choose to enable Jumbo Frame. This will add routes between the gateways over the tunnel connections to the gateway’s ipset “highmss” entry, so that traffic towards these routes will be subject to TCP MSS clamping rule in iptables with jumbo MSS value.

  • Jumbo Frame is supported for AWS and OCI only; it is not supported for Azure and GCP.

  • Jumbo Frame is only supported on private connections that support Jumbo Frame.

  • Jumbo Frame is supported with High Performance Encryption and BGP over LAN connections only. High Performance Encryption and Jumbo Frame must be enabled on all gateways in the end-to-end path of the traffic flow.

  • For BGP over LAN connection, Jumbo Frame is enabled (by default) when the Edge Gateway is created.