Link Search Menu Expand Document

Orchestrator 9.3 System Requirements Guide – Hub and Spoke Overlays

This guide outlines the minimum system requirements for hosting Orchestrator and Stats Collector version 9.3.x, used for managing EdgeConnect gateways. It covers Processor, Memory, and Disk requirements for self-hosted Orchestrator and Stats Collector and describes sizing processes for specific network configurations.

To create the host requirement tables for the self-hosted Orchestrator and Stats collector, we assumed the following to help us get an SD-WAN fabric tunnel count:

  • 4 hub-and-spoke overlays
  • 2 underlays
  • 1 internet breakout or SSE service
  • data was accumulated with 1) backup of network statistics and 2) without backup of network statistics
  • Used 1 Hub for ECs of 25, 100, 200, 300, 500
  • Used 4 Hubs for ECs of 1000, 2000, and 3000

If you need to deploy Orchestrator with a different configuration, please reach out to your Aruba technical representative for assistance.

The process for selecting the appropriate system configuration for a self-hosted Orchestrator and stats collector is aided by a flow chart with steps. The chart directs users to the appropriate Orchestrator and stats collector configuration table based on the deployment size of EdgeConnect gateways.

img

It is important to note that as of release 9.3, the maximum number of tunnels that an SD-WAN fabric can support is 3 million. This limitation has been considered for large deployments that include over 1000 Edgeconnect gateways. The tunnel count within the SD-WAN fabric is a critical factor for the Orchestrator host requirement, which will be explained further in the document.

Step 1. Orchestrator VM requirements

The Orchestrator requires the implementation of the following without exception for proper functioning:

  • CPU and Memory must be reserved for virtual appliances.
  • Recommended CPU requirements of 2.4GHz or greater with hyperthreading enabled.
  • These requirements do not include the resources needed by the hypervisor itself, which will require additional dedicated core CPU, memory, and storage to operate.
  • For non-VMware hypervisors, an extra core should be reserved for hypervisor tasks.
  • When using Hyper-V, Windows Server 2019 is needed for a virtual machine to use 8 or more virtual processors.
  • Ensure the CPU hardware Virtualization Technology (VT) feature is enabled in the BIOS and the BIOS is set to maximize performance. Refer to the CPU vendor’s documentation for guidance on enabling VT in the BIOS. When using VMware vSphere, an Enterprise Plus license is needed for a virtual machine to use 8 or more virtual processors.

Step 2.Supported Hypervisor and Cloud as-a-Service

Make sure to check the hypervisor compatibility list to ensure that HPE Aruba Networking has validated the Orchestrator with the hypervisor version you plan to use or deploy.

Hypervisor Hardware Compatibility List Comments
VMware ESXi 6.7/7.0 (VMware link) Fedora Core (2.6.38 Kernel)
Yocto 2.7.3 Warrior (4.19.87 Kernel)
Microsoft Hyper V 10.0 (Microsoft link) Fedora Core (2.6.38 Kernel)
Yocto 2.7.3 Warrior (4.19.87 Kernel)
Red Hat KVM 8.x (Red Hat link) Fedora Core (2.6.38 Kernel)
Yocto 2.7.3 Warrior (4.19.87 Kernel)
KVM, QEMU 4.x (KVM link) Fedora Core (2.6.38 Kernel)
Yocto 2.7.3 Warrior (4.19.87 Kernel)
Citrix XEN Server 8.1 (Citrix link) Fedora Core (2.6.38 Kernel)
Yocto 2.7.3 Warrior (4.19.87 Kernel)

The table shows the exact versions tested and validated by HPE Aruba Networking. Newer versions may be verified but are not officially tested.

Step 3 Determine the number of EdgeConnect gateways planned for deployment

To determine the virtual machine system requirements for the Orchestrator and stats collector, it’s important to know the number of EdgeConnect gateways that will be deployed. Additionally, collecting statistics for monitoring the network is crucial. When using the self-hosted Orchestrator, a stats collector (also known as a local stats collector) is automatically deployed during the initial deployment. This collector gathers key performance indicators and backs them up. For smaller to medium EdgeConnect deployments, the local stats collector is best suited. The local stats collector can support up to 300 gateways for hub and spoke overlays.

If there are more than 300 EdgeConnect gateways with hub-and-spoke overlays, it’s recommended to disable the local stats collector and create new ones based on the number of EdgeConnect gateways deployed. From release 9.2 of the Orchestrator, a new method for distributing a load of statistics for each EdgeConnect appliance is available. The stats collector and the EdgeConnect gateway are assigned by the Orchestrator administrator to help alleviate some performance issues. This method ensures an even load of EdgeConnect gateways across the several stats collectors. For hub-and-spoke overlays, it’s recommended to have 300 EdgeConnect gateways per stats collector.

Instructions on disabling the local stats collector and creating new ones in the Orchestrator are documented here (link). The configuration of the new stats collector depends on the number of EdgeConnect gateways to be deployed and the topology. For networks using a hub-and-spoke overlay and deploying over 300 EdgeConnect gateways, refer to Steps 5a and 5b for Orchestrator requirements.

The following table provides a guideline based on the overlay topology to provide the maximum of EdgeConnect gateways, the required CPU, and memory per stats collector.

Table: Stats Collector VM Requirements based on topology

Overlay Topology Gateways Per stats collector vCPU per stats collector Memory per stats collector
Mesh up to 150 6 16 GB
Hub-and-Spoke up to 300 6 24 G

Step 4. The two tables below will provide the recommended Orchestrator and Local Stats collector system requirements for a hub-and-spoke topology.

  • Table 4a provides CPU, Memory, and Disk and includes backup of network statistics.
  • Table 4b provides CPU, Memory, and Disk and does not include backup of network statistics.

Step 4a. Host Requirements Table: Orchestrator and Local Stats Collector with backup of network statistics

Ideal for small-medium deployments up to 300 EdgeConnect gateways in a hub-and-spoke topology.

EdgeConnect Gateways vCPU (Recommended) Memory GB (Recommended) Orch & Stats Collector Disk
Up to 25 4 24 512 GB
Up to 100 6 24 691 GB
Up to 200 6 24 1 TB
up to 300 6 24 1.4 TB

Step 4b. Host Requirements Table Orchestrator and local stats collector without backup of network statistics

EdgeConnect Gateways vCPU (Recommended) Memory GB (Recommended) Orch & Stats Collector Disk
Up to 25 4 24 512 GB
Up to 100 6 24 512 GB
Up to 200 6 24 527 GB
Up to 300 6 24 707 GB

Step 5. The following two tables will provide the recommended Orchestrator and Stats collector system requirements when deploying over 300 EdgeConnect gateways in a hub-and-spoke topology.

  • Table 5a provides CPU, Memory, and Disk and includes backup of network statistics.
  • Table 5b provides CPU, Memory, and Disk and does not include backup of network statistics.

Step 5a. Host Requirements: Orchestrator and Distributed Stats Collector with backup of network statistics for statistics retention.

img

Step 5b. Host Requirements: Orchestrator and Distributed Stats Collector without backup of network statistics for statistics retention.

img

The document outlines Orchestrator host requirements for release 9.3+, covering small to large-scale deployments with hub-and-spoke overlays. For Mesh overlay topology, please refer to the Orchestrator 9.3 Sizing Guide Mesh Overlays


Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to HPE Aruba Networking EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America