Skip to main content

Versa SD-WAN Gateway - Specifications

Versa Networks VOS NFA​

This page describes the main technical specifications and provisioning parameters for the Versa Networks VOS NFA SD‑WAN Gateway appliance as provided by the Evolution Platform blueprint.

Flavors & software​

Choose an IaaS flavor and a supported software image before provisioning. The available compute profiles are shown below.

Standard
Medium
4 vCPU
8 GB Mem
64 GB Disk
Medium
4 vCPU
16 GB Mem
64 GB Disk
Large
8 vCPU
32 GB Mem
64 GB Disk

Software images​

  • 22.1.3

Interfaces​

The diagram shows a single Versa VM with two Internet-facing interfaces that receive platform-allocated public IPs, plus optional MPLS and VLAN-based LAN/technical VPN interfaces. VLAN sub-interfaces are grouped for readability; see the per-interface sections below for configuration guidance.

Common interface notes:

  • Public IP addresses shown for Internet interfaces are platform-generated informational outputs, not customer-provided inputs.
  • BGP settings are available per interface or sub-interface and are optional. When BGP is not enabled, BGP-specific fields have no effect.
  • VLAN sub-interfaces are presented as a grouped concept; provide per‑VLAN VPN entries only when required by your deployment.

#1 - Internet Interface - management​

  • Role: Management & Internet (public).
  • The platform allocates a public IPv4 address for this interface and displays it as an informational output after provisioning.
  • No customer address input is required for the public IP allocation.

#2 - Internet Interface - access​

  • Role: Internet access (public).
  • The platform allocates a public IPv4 address for this interface and displays it as an informational output after provisioning.
  • No customer address input is required for the public IP allocation.

#3 - MPLS-VPN interface (optional)​

  • Role: connect the VNF to an MPLS‑VPN link.
  • Customer-provided addressing is required for this interface: Subnet, Gateway address, and VNF address must be provided during provisioning and are not updatable afterwards.
  • Optional fields:
    • Activate interface (boolean, default: true) — enable or disable the MPLS interface.
    • VPN list — select one or more MPLS VPN aliases to attach to this interface (1..99 entries when provided).
    • BGP block (optional): Enable BGP (boolean) and AS prepend (integer 1..6). AS prepend is an advanced option used in specific backup scenarios.
    • Static routes — optional list of prefixes to configure on the VNF for this interface.

#4 - MPLS LAN interface (VLAN sub-interfaces)​

  • Role: LAN connectivity delivered through VLAN sub-interfaces.
  • Sub-interfaces are optional and typically configured per customer VLAN. For each sub-interface you can provide a VPN list and optionally enable BGP and set AS prepend.
  • The documentation collapses many VLAN entries into a grouped description; provide individual VLAN configuration only when required by your deployment.

#5 - Technical VPNs interface (VLAN sub-interfaces)​

  • Role: dedicated technical VPN connectivity via VLAN sub-interfaces.
  • Similar behavior to interface #4: sub-interfaces are optional, and each can select a VPN list and optionally enable BGP with AS prepend.

Service parameters​

These are service-level values required during provisioning (not VM-level or interface IP inputs).

  • Versa controller IP address (mandatory, not updatable): IPv4 address of the Versa controller used to stage/register the VNF. The platform passes this value to the staging script during provisioning.
  • versa controller ID (mandatory, not updatable): identifier of the controller instance used for staging/registration; treated as an opaque string by the platform.
  • versa local ID (mandatory, not updatable): local identifier used by the controller or management context; provided by the customer.
  • Versa serial number (mandatory, not updatable): serial string used by the staging procedure to register the device with the controller.
  • Versa IP address (mandatory, not updatable): primary IP address for the VNF on a configured subnet (provide IPv4 or IPv4/CIDR as required by the blueprint).
  • Gateway IP address (mandatory, not updatable): gateway address for the subnet used by the VNF.

Platform-generated outputs​

  • Public IP address (Interface #1) — platform-allocated IPv4 shown after provisioning as an informational output.
  • Public IP address (Interface #2) — platform-allocated IPv4 shown after provisioning as an informational output.
Versa Networks product documentation

Software device versions​

The supported software image versions are shown above in the Software images list.

Licence​

Only Bring Your Own Licence (BYOL) type is supported for Fortinet SD-WAN. You need to purchase your software licence with Fortinet sales.

Security group​

No default security group configured for Fortinet VNE model.