1

Aviatrix Multi-Cloud Gateway Sizing

Aviatrix gateways are deployed in multiple clouds on the cloud-native instances/VMs. Every public cloud (CSP) provides different sizes and types of instances/VMs. Aviatrix provides the recommended gateway/instances sizes based on the CSP.

Aviatrix gateway sizing is based on the features one enables on the gateway. Sizing guidelines will change based on the features added. For example, an Aviatrix gateway can be Egress FQDN and spoke at the same time.

Reference: https://docs.aviatrix.com/HowTos/insane_mode_perf.html

AWS

AWS instance size recommendation based on throughput needs (non-InsaneMode)

 

AWS instance size recommendation based on throughput needs (InsaneMode)

 

AWS T3 instance series performance in InsaneMode

 

Azure

Azure instance size recommendation based on throughput needs (non-InsaneMode)

 

Azure instance size recommendation based on throughput needs (InsaneMode)

 

GCP

GCP instance size recommendation based on throughput needs (non-InsaneMode)

 

GCP instance size recommendation based on throughput needs (InsaneMode)

 

OCI

OCI instance size recommendation based on throughput needs (non-InsaneMode)

 

OCI instance size recommendation based on throughput needs (InsaneMode)

 

How to check MTU size

On controller use Trace Path. Go to Troubleshoot -> Diagnostics -> Network. Select a gateway and destination IP address, click Trace Path. It should display MTU of the devices along the path

Aviatrix Controller Size

NOTE:- In general, the minimum required system resources for the Controller with Co-Pilot are 4CPU + 16GB Memory.
Please note: For larger environments, the CoPilot-related resource consumption is increased and the Controller will need to be resized accordingly
.

Controller size is defined according to the footprint, controller size varies based on the number of gateways it has to support. We can always adjust the controller size based on future requirements and enhancements.

As an example - We deployed t3.2xlarge in AWS if we need to manage less than 30 Aviatrix gateways (t3.small) to start with and increase sizing as needed when expanding the footprint.

Aviatrix CoPilot Size

CoPilot size is defined according to the footprint, it depends on network topology size. We can always adjust the CoPilot size based on future requirements and enhancements.

As an example - We deployed m5.2xlarge in AWS if we need to manage less than 30 Aviatrix gateways (t3.small) to start with and increase sizing as needed when expanding the footprint.

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like1 Follow
  • 1 Likes
  • 3 wk agoLast active
  • 44Views
  • 3 Following