Orchestrator Host System Requirements — On-Prem for Release 9.6.0 and Later

This document outlines the recommended resources for running Orchestrator release 9.6.0 and later when deployed on prem.

  • These requirements do not include the resources needed by the hypervisor itself, which requires additional dedicated core CPU, memory, and storage to operate.

  • Reserve allocated RAM for virtual appliances to function optimally.

  • Reserve vCPU sockets and vCPU clock settings for virtual appliances to function optimally.

  • For non-VMware hypervisors, an extra core should be reserved for hypervisor tasks.

Main Orchestrator VM

Supported Version EdgeConnect Gateways vCPU Processors (Recommended) Memory in Gigabytes (Recommended) SSD Disk Requirements (Orch + SC)
R9.6+ Up to 25 4 24 500 GB - 1 TB
R9.6+ Up to 50 8 32 500 GB - 1 TB
R9.6+ Up to 100 24 64 500 GB - 1 TB
R9.6+ Up to 200 32 84 1 TB
R9.6+ Up to 500 48 128 2 TB
R9.6+ Up to 1000 72 144 3 TB
R9.6+ Up to 2000 128 512 5 TB
R9.6+ Up to 3000 192 768 6 TB
R9.6+ Up to 4000 192 768 6 TB - 7 TB
R9.6+ Up to 5000 192 768 7 TB

NOTE: Numbers are rounded to the next value. Resources and tuning parameters are based on approximately 1000 tunnels per appliance.

Upgrade Requirements (Rocky Linux and Memory)

If you are upgrading from an earlier Orchestrator version to 9.6.0 or later, ensure that the system is running Rocky Linux and that at least 24 GB of memory is allocated.

Starting with Orchestrator 9.6.0, the MySQL configuration database and the Statistics database are on the same virtual machine, which increases overall memory requirements compared to previous versions.

Supported Hypervisor Versions

This table shows exact versions tested by HPE Aruba Networking. Newer versions are verified, but not officially tested.