Avaya Analytics™ hardware requirements for High Availability deployment

Last Updated : Mar 18, 2026 |
Prolog information
Metadata
Keywords:

High Availability (HA) deployment

The following table provides information about the memory, storage, and vCPU requirements for each component of Avaya Analytics™ HA deployment without messaging:
You must install Avaya Analytics™ software on each master node. You must deploy each master node on separate physical servers. Cluster Control Manager (CCM) can reside on any physical server instance. You require a total of four virtual machines for an Avaya Analytics™ solution deployment, which includes HA.
The following table shows the default footprint sizes. Adding more feature capabilities, such as Routing Service by Group reporting, Async, or Agent Trace, increases these default footprint configurations.
Other:
Do not delete nodes or VMs from your VMware.
Deployment size
Component
Number of physical servers
VMs
vCPU
RAM (GB)
IOPS
vCenter data store storage (GB)
100 agent
Totals
3
4
49
118.5
5000
3404
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
16
39
-
1582
Master node 2 - server 2
1
16
39
-
1582
Master node 3 - server 3
1
16
39
-
0
500 agent
Totals
3
4
55
142.5
5000
5742
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
18
47
-
2751
Master node 2 - server 2
1
18
47
-
2751
Master node 3 - server 3
1
18
47
-
0
1000 agent
Totals
3
4
61
181.5
5000
8060
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
20
60
-
3910
Master node 2 - server 2
1
20
60
-
3910
Master node 3 - server 3
1
20
60
-
0
2000 agent
Totals
3
4
73
229.5
10000
8420
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
24
76
-
4090
Master node 2 - server 2
1
24
76
-
4090
Master node 3 - server 3
1
24
76
-
0
4500 agent
Totals
3
4
91
325.5
10000
11,418
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
30
108
-
5589
Master node 2 - server 2
1
30
108
-
5589
Master node 3 - server 3
1
30
108
-
0
Important:
  • You must create a data store specifically for Avaya Analytics™ usage. You can create additional data stores in vCenter for use by third-party applications. However you must ensure that the IOPS for the Avaya Analytics™ components are not affected.
  • You can deploy your Avaya Analytics™ on the same VMware cluster as Avaya Oceana®. See VMware supported features as mentioned in this document.
  • You can install a single Avaya Analytics™ deployment on a VMware cluster.
  • VMware ESXi 7.0 is supported.
  • You must enable VMware High Availability at the VMware cluster level.
  • You must enable VMware DRS to ensure that the virtual machines are deployed on different physical hosts.
    Note:
    Disabling VMware DRS at the cluster level removes all the existing resource pools. Then these resource pools need to be manually added into the system again. VMware displays a warning to the administrator about the impacts of turning off DRS and resource pools with the option to save a snapshot if required.
  • Avaya Analytics™ can be deployed using thin provisioning of the disk space. For the Avaya Analytics™ application, thin provisioning of the disk storage within VMware is supported for all agent configurations. For more information on specifics of thin provisioning, see Thin provisioning of disk storage in VMware.
  • Avaya Analytics™ supports LDAP version 3.
  • Solid State Drives (SSD) are supported in addition to SATA, 15000 RPM.
  • Only external storage is supported for HA configurations.
    The external shared storage is a datastore that must be available for use during the installation of Avaya Analytics™. The automated deployment of Avaya Analytics™ for setting up volumes for the database uses external storage. The external storage is required to persist the historical data, logging, and kafka storage, located in the vCenter datastore. The external storage configured must be separate to the CCM and Kubernetes VM’s disks.

Analytics and Messaging deployment

The following table provides information about the memory, storage, and vCPU requirements for each component of Avaya Analytics™ and Messaging deployment:
Deployment size
Component
VMs
vCPU
RAM (GB)
IOPS
vCenter data store storage (GB)
100 agent
Totals
4
55
124.5
5000
3404
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
18
41
-
1582
Master node 2 - server 2
1
18
41
-
1582
Master node 3 - server 3
1
18
41
-
0
500 agent
Totals
4
61
148.5
5000
5742
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
20
49
-
2751
Master node 2 - server 2
1
20
49
-
2751
Master node 3 - server 3
1
20
49
-
0
1000 agent
Totals
4
67
190.5
5000
8060
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
22
63
-
3910
Master node 2 - server 2
1
22
63
-
3910
Master node 3 - server 3
1
22
63
-
0
2000 agent
Totals
4
79
235.5
10000
8420
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
26
78
-
4090
Master node 2 - server 2
1
26
78
-
4090
Master node 3 - server 3
1
26
78
-
0
4500 agent
Totals
4
91
337.5
10000
11,418
CCM - server 1, 2, or 3
1
1
1.5
-
240
Master node 1 - server 1
1
30
112
-
5589
Master node 2 - server 2
1
30
112
-
5589
Master node 3 - server 3
1
30
112
-
0
Note:
The Messaging deployment is applicable for customers who deploy Avaya Analytics™ and Messaging on the same platform. It does not apply to the non-HA/Lab deployment of Avaya Analytics™.
For hardware requirement details of Avaya Analytics™ on non-High Availability (HA), see the relevant section in this document.