Skip to main content

Aviatrix Edge WAN Connect Cluster - Create


To create an Aviatrix Edge WAN Connect Cluster, prepare the required service and VM values listed below and follow the console steps in order. The provisioning creates two virtual machines in cluster mode; the specification does not describe how cluster mode implements availability behavior.

Step 1 - Select project​

Select the project in which you want to deploy your virtual Edge:

Select your project

Select your project.

Step 2 - Deployment configuration​

2.1 Name your Virtual Edge (This name will be displayed on the Virtual Network Edge dashboard)

Set Virtual Edge Name

Set Virtual Edge name.

2.2 Select the implementation mode: Cluster
Select implementation mode

Select implementation mode.

Virtual device configuration​

2.3 Fill the Virtual Device name (This name will be used as hostname for the virtual device).

2.4 Select the Orange POP which correspond to the location of POP.

Fill Virtual Device Name, Region and POP

Fill Virtual Device Name, Region and POP.

For Dual or Cluster Topology

For Dual topology, different POP can be chosen for each virtual Device.

For Cluster topology, the Virtual devices must be on the same POP.

Select Internet and MPLS Bandwidth for each Virtual Device.

Select Internet and MPLS bandwidth for the Virtual Device

Select Internet and MPLS bandwidth for the Virtual Device.

Step 3 - Virtual Edge configuration​

3.1 Select the Software version.

Available software versions are :

  • 7.0-2023-05-18
  • 7.1-2023-04-24
  • 8.0-2025-04-25
  • 8.1-2025-07-29

3.2 Select the Virtual Device flavor.

Available flavors are :

StandardDPDK
Small
2 vCPU
4 GB Mem
64 GB Disk
2 vCPU
4 GB Mem
64 GB Disk
Medium
4 vCPU
8 GB Mem
64 GB Disk
4 vCPU
8 GB Mem
64 GB Disk
Large
8 vCPU
16 GB Mem
64 GB Disk
8 vCPU
16 GB Mem
64 GB Disk
Notes
  • For Dual topology, different flavors can be selected for each Virtual device.
  • DPDK (Data Plane Development Kit) is a set of libraries and drivers designed to acceler- ate packet processing and optimize performance in network applications. It provides a high-performance framework for managing network traffic at a low level, bypassing the traditional kernel network stack to enhance throughput and reduce latency.
    Pay attention the use of an image with DPDK significantly increases energy consumption and therefore the associated carbon footprint.

3.3 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 4 - Interfaces configuration​

Interfaces​

An IP allocation is expected before configuring the interfaces. Public IP addresses for management are platform-generated outputs and will be displayed by the platform after allocation.

IP allocation

IP allocation.

IP allocation success

IP allocation success message.

When configuring interfaces in the console you will complete the following for interfaces #1 and #2 and review interface #3 as informational:

  • For interfaces #1 - Technical-VPN interface and #2 - MPLS-VPN interface: provide a VPN list with at least one VPN entry. Each VPN entry requires a VPN Name (BVPN alias) and a VPN role (choose one of: any-to-any, client, server). You may also toggle the Activate interface boolean (default: active). Optional BGP settings can be provided if required.
Configure Aviatrix interfaces

Configure Aviatrix interfaces.

  • #3 - Internet management interface: this interface is informational in the provisioning schema. Public IP addresses associated to this interface are platform-generated outputs and are displayed by the platform; you do not provide them as input.

Virtual device configuration​

Upload VM-specific values and the cloud-init userdata when prompted by the console. The UI will request a hostname for each VM, an image, a flavor and the userdata content (base64-encoded). VM1 additionally requires a VM AS number during creation.

Provide a configuration file (upload the cloud init file)

Provide a configuration file.

Step 5 - Service specific parameters​

5.1 Fill in the following service parameters:

  • Transit gateways networks: Provide one or more IPv4 CIDR ranges that identify the transit gateway networks used by the service. The platform uses these values during provisioning. minArraySize:1 maxArraySize:9; each item must match IPv4 CIDR pattern per schema.
  • Controllers network: Provide the controllers network as an IPv4 CIDR. This is a service-level network parameter required at creation time. pattern enforced by schema for subnetV4.
  • Copilots network: Provide the copilots network as an IPv4 CIDR. This is a service-level network parameter required at creation time. pattern enforced by schema for subnetV4.

5.2 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 6 - Validation​

After clicking the Continue button, a page summarizing the characteristics of the Virtual Edge will be displayed.

This page is divided into several sections :

  • Projects
  • Deployment
  • Virtual edge configuration
  • Interfaces configuration
  • Service specific parameters

At this stage, it is still possible to modify the characteristics for these sections.

One section is dedicated to display the Carbon footprint of the Virtual Edge :

Carbon footprint for Virtual Edge

Carbon footprint for Virtual Edge.

Click on the Provision button to initiate the provisioning of the Virtual Network Edge. You can also preserve the Virtual Network Edge configuration by clicking the Save and close button and the following toast is displayed.

In this case, you will find the Virtual Network Edge in designed state on the .

correctly saved toast