Aller au contenu principal

Aviatrix Edge Cluster - Create

To create an Aviatrix Edge Cluster, follow the console steps below in order. Prepare the required VM details and the service network values before starting the provisioning flow.

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​

The create journey presents the three numbered interfaces defined for this blueprint. Interfaces #1 - Internet Interface and #3 - Internet management interface are marked informational in the blueprint: public IPv4 addresses for these interfaces are produced by the platform and shown in the provisioning results. The portal may present an IP allocation step depending on platform behavior; the blueprint itself records those addresses as platform-generated outputs.

IP allocation

IP allocation (console view).

IP allocation success

IP allocation success (console view).

For the #2 - MPLS-VPN interface you can configure whether the interface is active, provide one or more VPN entries (VPN Name and VPN role) and, if required, enable BGP sub-parameters such as AS prepend. Use the interface editor in the portal to add VPN entries and roles.

Configure Aviatrix interfaces

Interface configuration editor.

Virtual device configuration​

During creation you must provide the per-VM values required by the blueprint: vm_name, image, flavor and userdata (cloud-init). Userdata must be provided as base64-encoded content.

Upload cloud-init userdata

Upload your cloud-init userdata (base64).

Step 5 - Service specific parameters​

5.1 Fill in the following service parameters:

  • VM AS number (VM 1): AS number assigned to the VM. The specification notes that both 2- and 4-byte AS numbers are allowed. min:1, max:4294967295.
  • VM AS number (VM 2): AS number assigned to the VM. The specification notes that both 2- and 4-byte AS numbers are allowed. min:1, max:4294967295.
  • Transit gateways networks: Provide the transit gateway network ranges in CIDR notation that the service should be aware of during provisioning. This is a service-level input, not an interface IP address. minArraySize:1, maxArraySize:9, items must match IPv4 CIDR pattern.
  • Controllers network: Provide the Controller network in CIDR notation as requested by the service-specific parameters. Must match IPv4 CIDR pattern..
  • Copilots network: Provide the Copilots network in CIDR notation as requested by the service-specific parameters. Must match IPv4 CIDR pattern..

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