Aller au contenu principal

HPE Aruba EdgeConnect - Specifications

HPE Aruba EdgeConnect​

This page describes the HPE Aruba EdgeConnect SD‑WAN Gateway virtual appliance. Provisioning uses EdgeConnect (EdgeConnect Virtual) images and the blueprint supports both single and dual deployment modes.

Deployment modes​

  • single
  • dual

Flavors​

Choose a VM size (flavor) when creating the virtual device. Supported flavor identifiers include std1.c4, std1.c8 and std1.c8m; the available flavors may vary with the selected software image.

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

When deploying in dual mode, select a flavor for each virtual device.

Interfaces​

The diagram above shows the Internet uplink with a platform-assigned public IP on #1 - Internet Interface, and the MPLS connectivity carried on #2 - MPLS‑VPN interface using VLAN sub‑interfaces. VLANs 101..148 are supported and collapsed in the diagram for readability; customers configure VPN and optional BGP settings per VLAN sub‑interface.

Common interface behavior

  • Public IP shown for the Internet uplink is a platform allocation and is presented as a platform-generated output when requested.
  • The MPLS parent interface carries VLAN sub‑interfaces. For each VLAN sub‑interface you provide one or more VPN entries and optional routing settings.

#1 - Internet Interface​

The #1 - Internet Interface is the public uplink. If you request a public IPv4 address during provisioning, the platform will allocate it and inject it into the VM configuration. There are no additional required customer parameters for this interface beyond the public IP allocation option.

#2 - MPLS‑VPN interface​

The #2 - MPLS‑VPN interface is the parent for VLAN sub‑interfaces (for example VLANs 101..148). For each VLAN sub‑interface you typically provide:

  • VPN Name — the MPLS‑VPN alias to attach the VLAN to (use letters, digits, hyphens and underscores).
  • VPN role — optional role inside the VPN (any-to-any, client, server).
  • Optional addressing fields such as subnet or VM IP when requested by the provisioning form.
  • Optional routing settings (see Routing section).

When multiple VLANs are required, provide one VPN entry per VLAN. VLAN sub‑interfaces are optional; add them only when you need MPLS connectivity on that VLAN.

Routing (BGP)​

The blueprint exposes a small set of routing controls per VLAN sub‑interface:

  • Enable BGP — optional and updatable. When Enable BGP is not set, no BGP-specific configuration is applied through this setting.
  • AS prepend — optional integer between 1 and 6. This value is used to prepend the VM AS in the BGP AS path when BGP is enabled; it is an optional tuning parameter described in the blueprint.

Enable BGP only when your MPLS VPN requires BGP peering and coordinate full BGP neighbor details with your MPLS provider.

Virtual device parameters​

When creating the virtual device you provide VM-level parameters such as:

  • VM name — hostname used by the platform (maximum 22 characters; use letters, digits and hyphens).
  • Software image — choose one of the supported EdgeConnect images.
  • Flavor — select the VM size (see Flavors section).
  • VM AS number — optional autonomous system number when BGP is required (supports 2‑byte and 4‑byte AS numbers; valid range 1..4294967295).

Software device versions​

Below are the EdgeConnect software images available for this VNF.

  • 9.3.2.3
  • 9.3.3.2
  • 9.5.3.8

Service specific parameters​

Service specific parameters are service-level values requested during provisioning (they are not VM names, interface IPs, or platform outputs). For this VNF the main service-specific values are:

  • Account name (mandatory) — account name provided by the vendor provisioning team. It is used by cloud-init to register the VM with the EdgeConnect orchestration portal.
  • Account key (mandatory, secret) — secret key used by cloud-init to perform registration. Treat this value as sensitive.
  • VM tag (optional) — short metadata tag to label the VM or site in vendor orchestration records.

Provide the Account name and Account key exactly as supplied by HPE Aruba/Orange during provisioning.

Platform-generated outputs​

  • Assigned public IPv4 address — if you request a public IP for the Internet interface, the platform allocates it and injects it into the VM configuration. Public IPs shown in the console are platform outputs.
HPE Aruba Documentation

Service parameters and cloud-init​

The platform uses a cloud-init template during provisioning to register the VM with the vendor orchestration portal using the Account name and Account key, and to apply the basic interface configuration. Custom user-data uploads are not supported for this VNF.

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.