Aviatrix CloudN Hardware Appliance

Datacenter deployment is shown in the diagram below with redundancy, where R1 and R2 are two edge routers that connected to VGW or VPN Gateway over DX. R3 and R4 are two routers connect to the inside of the datacenter. Aviatrix CloudN also runs a BGP session with R3 and R4 to collect datacenter routes. VGW is only used to terminate DX. Aviatrix Gateway and on-prem appliance CloudN run a BGP session to propagate on-prem routes to the Transit VPC/VNet. IPsec tunnels are also built between the two.

A logical deployment layout is described as below.

To deploy CloudN in your datacenter, follow the instructions in Managed CloudN Workflows.

Aviatrix High Performance Encryption Mode high speed encryption feature works on top of your existing WAN link, and it is agnostic to the type of connection used (Direct Connect/ExpressRoute/FastConnect/InterConnect). As long as you have a pipe that’s large enough to allow for high throughput data transfer, using High Performance Encryption Mode will offer superior performance to regular IPsec.

Yes. A CloudN appliance can build multiple of HPE connections to different Aviatrix Transit Gateways over multiple Direct Connect or ExpressRoute.

Yes. When a Managed CloudN device attaches to an Aviatrix Transit gateway with HA function enabled, High Performance Encryption mode tunnels to both primary and backup transit gateways are built automatically.

No. We don’t support this mixed topology. Once you decide to deploy Managed CloudN solution, you need to make sure there is no IPsec tunnel between Aviatrix Transit Gateway and Standalone CloudN before registering the Standalone CloudN to Aviatrix Controller.

Yes. An Aviatrix Transit Gateway can build multiple HPE connections to different Managed CloudNs.

Yes. While this is not recommended practice, an Aviatrix Transit Gateway is able to build mixed connections to different Standalone CloudN and Managed CloudN. This deployment is for migration stage only.