Skip to main content

Aviatrix Secure Edge Wan Connect - Specifications

Aviatrix Edge WAN Connect​

This section describes the specifications for deploying Aviatrix Edge WAN Connect.

Aviatrix Edge WAN Connect VNF

Aviatrix Edge WAN Connect VNF.

Flavors​

The available VM sizes are shown below. Choose the flavor that matches expected throughput and image requirements.

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

Interfaces​

Simplified topology: single Aviatrix VM with eight numbered interfaces. #1 and #2 connect to Orange-managed VPNs; #3 is the Internet management interface and shows the platform-allocated public IP. #4–#8 are optional extra WAN interfaces.

Common interface parameters (explained once):

  • Activate interface — enable or disable the interface (default: true).
  • VPN list — select one or more VPN entries to attach (minimum 1 entry).
  • VPN Name — choose the VPN alias (must match the allowed pattern).
  • VPN role — select the role for each VPN entry (any-to-any, client, server).
  • BGP — optional per-interface setting to enable BGP sessions.
  • AS prepend — optional integer (1..6) for AS path prepend; an advanced option used only when requested.

Per-interface notes:

#1 - Technical-VPN interface​

Mandatory interface used to attach one or more VPNs from the VPN list. Provide at least one VPN Name and assign a VPN role. You may enable BGP and set an AS prepend value if required.

#2 - MPLS-VPN interface​

Mandatory interface for connecting to Orange MPLS-VPN. Same customer inputs as #1: VPN list, VPN Name, VPN role and optional BGP/AS prepend.

#3 - Internet management interface (optional)​

Platform allocates a Public IP address for management. This public IP is a platform-generated output; customers reserve or accept it during IP allocation.

#4 - Extra WAN interface (optional)​

Optional additional WAN link. If enabled, configure VPN list, VPN Name and VPN role. BGP and AS prepend are optional.

#5 - Extra WAN interface (optional)​

Optional additional WAN link. Same configuration options as #4.

#6 - Extra WAN interface (optional)​

Optional additional WAN link. Same configuration options as #4.

#7 - Extra WAN interface (optional)​

Optional additional WAN link. Same configuration options as #4.

#8 - Extra WAN interface (optional)​

Optional additional WAN link. Same configuration options as #4.

Routing and BGP​

The BGP setting is optional and configurable per interface. When BGP is not enabled, no BGP-specific configuration is applied through this setting. AS prepend is an advanced, optional integer (1..6) used only when requested for AS path manipulation.

Virtual device parameters​

  • VM name — hostname used for the VM. Must match pattern [a-zA-Z0-9-]* and have a maximum length of 22 characters.
  • VM image — choose one of the supported images shown in the Software device versions section.
  • VM flavor — select a flavor from the Flavors table that fits your performance needs.
  • Cloud-init (userdata) — Upload cloud-init during creation; the platform expects base64-encoded content for userdata.
  • VM AS number — provide the Autonomous System number for the VM (1..4294967295).

Software device versions​

Below are the software image versions available on the platform:

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

Service specific parameters​

Service provisioning requires a small set of service-level values:

  • Transit gateways networks — list of one to nine IPv4 CIDR ranges. These represent upstream transit networks used by the service and are required at creation time (they are service-level values, not interface addresses).
  • Controllers network — single IPv4 CIDR identifying the controller network required by the Aviatrix service. Required at creation time.
  • Copilots network — single IPv4 CIDR identifying the copilot network required by the Aviatrix service. Required at creation time.

Provide these values in CIDR notation during the Create journey; they are service-level inputs used by the blueprint and are not platform-generated outputs.

Platform outputs (informational)​

  • Public IP address (management) — the platform allocates and reports a public IPv4 address for the Internet management interface after IP allocation. This is an informational output.

Licence​

Only Bring Your Own Licence (BYOL) type is supported for Aviatrix Secure Edge. You need to purchase your software licence with Aviatrix sales.

Aviatrix Documentation
Aviatrix Support