<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
  • There are no suggestions because the search field is empty.

Aruba (HPE) VNFs

Aruba is available as the EdgeConnect Virtual SD-WAN edge, managed through Aruba Orchestrator. Each device is offered customer-managed, Tata Communications-managed, or both. Sizes, interfaces, access methods and supported versions are below, with links to Aruba (HPE)’s own documentation and support.

Devices

EdgeConnect SD-WAN

The Aruba EdgeConnect Virtual SD-WAN edge.

Function: SD-WAN

Available: Customer-managed and Tata Communications-managed

Size

vCPU cores

Memory

Software package

Tiny

2 Cores

8GB

EdgeConnect-V Standard

Small

4 Cores

16GB

EdgeConnect-V Standard

Medium

8 Cores

32GB

EdgeConnect-V Standard

Large

16 Cores

64GB

EdgeConnect-V Standard

  • Virtual data interfaces (default / max): 10 / 32

  • Supported OS versions: 9.3.8.1, 9.4.3.7, 9.4.4.1, 9.5.3.4, 9.1.4.2, 9.2.4, 9.2.5, 9.2.9, 9.3.2, 9.4.2.3

  • Access methods: Web Console, SSH via Orchestrator

  • Deployment options: Single, Redundant

Licensing and management

Devices from Aruba (HPE) are offered under two models. With customer-managed (BYOL), Tata Communications hosts the VNF and you provide and manage your own Aruba (HPE) licence, configuration and patching; you are responsible for obtaining a valid Aruba (HPE) licence, so contact Aruba (HPE) or a Aruba (HPE) partner to purchase a licence and support contract. With Tata Communications-managed, Tata Communications provides the licence (subscription) and runs configuration, management, patching and renewals.

Deploying with or without a public IP address

A VNF can be deployed with a public IP address on IZO™+ Multi Cloud Connect or without one; where no public IP is assigned, plan management access over the private path in your solution. Device-side configuration (interfaces, routing, policy) is performed in the vendor’s own management tooling using the access methods listed for each device. This page stays at parameter-handoff level and does not reproduce vendor command-line configuration; see the vendor documentation below.

Aruba (HPE) documentation and support

For device configuration, feature detail and throughput figures, use Aruba (HPE)’s own resources. For a customer-managed device you obtain support from Aruba (HPE) or a Aruba (HPE) partner; for a Tata Communications-managed device, raise a request on the TCx Portal and Tata Communications handles it.

Related pages