Virtual machine resource requirements and average utilization

Last Updated : Jun 03, 2025 |
Before deploying a CMS virtual machine, ensure that the host can support the configuration you want. After deployment and during normal operation, monitor the resource usage to ensure that the proper level of resources remains available.
Important:
  • If deploying on a customer provided virtual host platform, you can start with the minimum memory, minimum memory reservation, and minimum disk space allocations. However, Avaya will require you to increase the memory allocations if Avaya finds that reported CMS problems relate to memory usage.
Prolog information
Metadata
Keywords:

Minimum required resources for virtual machine configurations

The following table outlines the virtual machine resource requirements for different CMS profiles.
VM resource
Small
Medium
Large
Extended
Notes
vCPU Cores (CPU)
2
8
16
32
The number of single core virtual CPUs.
Cores per Socket
2
8
16
32
The number of CPUs per socket. All cores are assigned to one socket. Therefore, the number of vCPU cores are the number of logical CPUs.
vCPU reservation
1200 MHz
4800 MHz
9600 MHz
9600 MHz
Guaranteed CPU allocation: 25% of vCPU capacity.
Calculation: vCPUs x processor clock speed (2400Mhz)/4.
Memory
8 GB
32 GB
64 GB
64 GB
The memory size represents the maximum that a CMS deployment might consume.
The medium and large configuration memory sizes match real hardware machines. The real hardware memory configuration considers future memory growth.
" minimum for customer-provided VM
4 GB
16 GB
32 GB
–
Memory reservation
8 GB
32 G
64 GB
64 GB
If the memory is not reserved and there is contention with other VM applications for additional memory resources, sufficient memory might not be available, resulting in CMS failures.
" minimum for customer-provided VM
4 GB
16 GB
32 GB
–
Storage
800 GB
1200 GB
1800 GB
6000 GB
If the recommended storage value on the medium and large configurations is not administered, sufficient storage might not be available resulting in CMS failure.
Note:
For medium and large configurations, you will configure two disks.
IOPS
200
300
600
600
The IOPS data is based on real CMS hardware machines with 50% read and 50% write data.
Shared NICs
Two @ 1000 Mbps
Two @ 1000 Mbps
Two @ 1000 Mbps
Two @ 1000 Mbps
A typical CMS deployment only requires two Ethernet ports, but many hardware options provide a four-port NIC.
The OVA contains many of the virtual machine resource requirements, such as vCPU reservation and memory reservation. The target virtual machine confirms that the required resources in the OVA are available before deploying the OVA.

Average resource and network utilization for standard configurations

Average resource usage
Small
Medium
Large
Notes
CPU consumed
600 MHz
2 GHz
8 GHz
Memory consumed
500 MB
2 GB
4 GB
Network consumed
0.252 Mbps
0.512 Mbps
1.696 Mbps
IOPS
12
18
28
IOPS is higher during nightly summarization.

Requirements for expanding large configurations on customer-provided virtual machines

To accommodate CMS deployments that require larger databases, you must increase the amount of disk space on the virtual machine. Use the following table to determine the amount of disk space required by the database to support a larger number of agent skill pairs at interval lengths of 15 or 30 minutes.
The values in the table assume 62 days of interval storage and five years of daily storage (1825 days) when you have a one time zone. You can configure data storage allocation and view free space allocation information from CMS Supervisor as described in Administering Avaya Call Management System.
Agent skill pairs
200000
400000
600000
800000
1000000
1500000
Interval length (minutes)
15
30
15
30
15
30
15
30
15
30
15
30
Minimum virtual machine disk size (TB)
1.8
2.2
2.2
1.9
2.9
2.6
3.8
3.3
4.0
2.5
5.9
3.7