System requirements

Last Updated : Feb 27, 2026 |
Prolog information
Metadata
Keywords:
The Avaya Aura® MS appliance is deployed using a vSphere Web Client or a VMware Host Client.
The ESXi host must meet the following system requirements:
ESXi host resource
Requirement
CPU
The core processor speed must be at least 2190 MHz and Intel® processors are strongly recommended, or performance cannot be guaranteed. Intel® and AMD processors require minimum SSE 4.1 support.
For all VM deployed on a host with an Avaya Aura® MS the total number of vCPU must not exceed the number of physical CPUs.
Configuration profile 1 and 2 require 4 vCPUs.
Configuration profile 3 and 4 require 8 vCPUs.
Configuration profile 5 and 6 require 16 vCPUs.
Memory
Configuration profile 1 and 2 require 4608 MB of memory.
Configuration profile 3 and 4 require 8192 MB of memory.
Configuration profile 5 and 6 require 16384 MB of memory.
Disk space
Configuration profile 1, 3, and 5 require 50 GB of ESXi datastore.
Configuration profile 2, 4, and 6 require 250 GB of ESXi datastore.
Network bandwidth
A dedicated pair of 1 Gbps network interfaces must be available in a teamed, failover configuration. Alternatively, 1 Gbps of dedicated bandwidth on a pair of 10 Gbps network interfaces must be available in a teamed, failover configuration.
IOPS
The system must support 100 Input/Output Operations per Second (IOPS).
The following requirements are also mandatory:
  • Physical CPUs on the host must not be oversubscribed with respect to vCPU count across all VMs that share the host with the media server. A physical CPU refers to a physical CPU core and not to a hyper-thread. For example, the total number of vCPUs across all VMs on an ESXi host that has 12 physical cores with 24 hyper-threads, must not exceed 12.
    Note:
    This recommendation prevents CPU oversubscription. Therefore, the CPU reservation of the media server VM effectively enforces the minimum CPU core speed of the underlying hardware. The VM fails to start if the underlying hardware does not meet the core speed requirements.
  • Do not modify the CPU or memory reservations that are set for Avaya Aura® MS OVA.
    Note:
    Reservations are not permitted for Avaya Solutions Platform 4200 series solutions (formerly known as CPOD/PodFx) deployment. It is mandatory to ensure the ESXi host is not oversubscribed (pCPU <= vCPU for all VMs deployed to that host).
  • For maximum system performance, ensure that:
    1. Energy savings features are disabled.
    2. Maximum performance settings are enabled in the server BIOS.
  • When deploying the OVA file, select Thick Provision Lazy Zeroed option for the VM virtual disks.
  • ESXi feature support is detailed in the following table:
ESXi Feature
Avaya Aura® Media Server Support
ESXi Versions
Supported Versions: 7.0 or 8.0
Clone Virtual Machine
Supported. VMs must be shut down before copying.
Caution:
Cloning should not be used to create additional Avaya Aura® MS server instances. This will result in software failures since multiple Avaya Aura® MS servers are assigned to the same UUID.
Large Receive Offload (LRO)
Supported.
Resize Virtual Machine
Not supported when the VM is powered ON.
Supported when the VMs are shut down and resized to match one of the supported Avaya profiles, unless otherwise instructed by Avaya.
VMware Storage vMotion
Not supported.
To migrate to a different storage system, you must first shut down the VM. For 1+1 HA Clusters, both VMs must be shut down.
VMware vMotion
Not supported.
To migrate to a different physical host, you must first shut down the VM. For 1+1 HA Clusters, both VMs must be shut down.
VMware Snapshots
Not supported on production servers outside of maintenance windows.
Supported for temporary use when applying feature packs, service packs, or patches during maintenance windows.
The VM must be shut down before creating, deleting, or reverting a snapshot. For 1+1 HA clusters, both VMs must be shut down for any snapshot operation on either server.
Snapshots adversely impact the VM disk and CPU performance and must be removed before returning the server to production.
VMware High Availability (HA)
Not supported.
VMware Distributed Resource Scheduler (DRS)
Not supported.
Distributed Power Management (DPM)
Not supported.
VMware Fault Tolerance (FT)
Not supported.
vSphere Standard Switch
Supported when the media server has a dedicated pair of 1 Gbps NICs or 1 Gbps of dedicated bandwidth on a pair of 10 Gbps NICs.
vSphere Distributed Switch
Supported if the vSphere Distributed Switch is engineered to provide same bandwidth as the vSphere Standard Switch. The media server requires a dedicated pair of 1 Gbps NICs or 1 Gbps of dedicated bandwidth on a pair of 10 Gbps NICs.
CPU and Memory Reservations
Supported. Reservations are mandatory.
VSAN support
Supported if the VSAN meets media server Input/Output Operations Per Second (IOPS) requirements.
Thin Provisioning
Supported.