System requirements

Last Updated : Dec 01, 2025 |
Prolog information
Metadata
Keywords:
The Avaya Aura® MS appliance is deployed using a Linux command line shell.
The KVM on Red Hat® hypervisor host (ASP 130 R6 or higher) must meet the following system requirements:
KVM on Red Hat® host resource
Requirement
Red Hat® version
8.10
CPU
The core processor speed must be at least 2.2 GHz.
For all VM deployed on a host with an Avaya Aura® MS, the total number of vCPUs must not exceed the number of logical CPUs.
Only 4,8, and 16 vCPU instances are supported.
Memory
Memory is allocated based on the number of vCPUs.
  • 4 vCPUs require 4608 MB of memory.
  • 8 vCPUs require 8192 MB of memory.
  • 16 vCPUs require 16384 MB of memory.
Disk space
Instances require 50 GB of KVM datastore. A one-time increase of 200 GB is allowed either at VM creation or post VM creation.
Network bandwidth
A dedicated pair of 1 Gbps network interfaces must be available in a bonded, active-backup configuration. Alternatively, 1 Gbps of dedicated bandwidth on a pair of 10 Gbps network interfaces must be available in a bonded, active-backup configuration.
IOPS
The system must support 100 Input/Output Operations per Second (IOPS).
The following requirements are also mandatory:
  • It is mandatory to ensure the KVM on Red Hat® host is not oversubscribed. Logical cores on the host must not be oversubscribed with respect to vCPU count across all VMs that share the host with the media server. For example, the total number of vCPUs across all VMs on a KVM host that has 24 logical cores (12 physical cores with hyper-threading enabled), must not exceed 24.
    Note:
    This recommendation prevents CPU oversubscription.
  • For maximum system performance, ensure that:
    1. Energy saving features are disabled.
    2. Maximum performance settings are enabled in the server BIOS.
  • KVM on Red Hat® feature support is detailed in the following table:
KVM on Red Hat® Feature
Avaya Aura® Media Server Support
RHEL Versions
Supported Versions: 8.10
Clone Virtual Machine
Supported.
VMs must be shut down before copying.
Note that cloning shouldn’t be used to create additional AAMS server instances. This will result in software failures since multiple AAMS 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. A one time resizing to add 200 GB is allowed (max 250GB)
Live Storage Migration
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.
Live Migration
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.
KVM Snapshots (CLI only)
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.
KVM High Availability (HA)
Not supported.
Fault Tolerance (FT)
Not supported.
KVM Overcommitting of Resources
The KVM hypervisor automatically overcommits CPUs and memory. This means that more virtualized CPUs and memory can be allocated to virtual machines than there are logical resources on the system (see Best Practices Recommendation section).
Power Management
Not supported.
KVM Secure Boot
Not supported prior to 10.2.0 SP1.