Supported footprints of Session Manager on VMware

Last Updated : Oct 07, 2024 |
The following table summarizes single Session Manager capacities for all Session Manager footprints.
Note:
The capacities listed here are only for Session Manager. For information about capacity limits for AADS, see the AADS documentation.
Note:
Avaya Aura® Session Manager supports VMware hosts with Hyperthreading enabled at the BIOS level.
Session Manager Device Footprints
Up to 2K Devices
2K to 4.5K Devices
4.5K to 7K Devices
7K to 10K Devices
10K to 23.3K Devices
23.3K to 66.7K Devices
CPU Minimum
2200MHz
vCPUs
3
5
8
12
20
53
CPU MHz Reservation
3300
5500
8800
13200
22000
58300
Memory Reservation
5132MiB
7828 MiB
10552 MiB
13368 MiB
24370 MiB
74064 MiB
SIP Devices1 (Normal/Failure) 2
2K/2.4K
4.5K/5K
7K/8K
10K/12K
23.3K/ 25K
66.7K/72K
CC Agents (Normal/Failure)
1.6K/2K
3.75K/4166
5.8K/6666
8333/10K
18K/21K
21.6K/25.2K
Presence Users (Normal/Failure)
2K/2.4K
4.5K/5K
7K/8K
10K/12K
18K/21K
21.6K/25.2K
Sessions (Sec/Hour/Max)
20/72K/ 17.9K
45/162K/37.4K
70/256K/59.8K
100/360K/90K
150/540K/170K
180/648K/510K
HDD for VMware OVA (GiB)3
100
100
135
135
210
210
HDD for Software-Only ISO (GiB)4
100
100
135
135
210
210
Notes:
  1. SIP devices: It includes all hard endpoints, soft clients, AST/NON-AST SIP endpoints and third-party endpoints.
  2. Normal/Failure: Normal refers to capacity of the Session Manager in Sunny Day scenario and Failure refers to capacity of the Session Manager in Rainy Day scenario. A Session Manager in a rainy day scenario can have more number of users registered as it has registrations from the users whose Primary Session Manager is down.
  3. HDD for VMware OVA: When deployed with SDM. Other deployment methods require that disk size be resized manually.
  4. You can deploy Session Manager software-only ISO image on VMware, KVM, Hyper-V, Amazon Web Services, Google Cloud Platform, and Microsoft Azure platforms.
Session Manager instances are intended to operate as redundant, homogeneous servers to provide high reliability if a Session Manager failure or a network component failure occurs. Each Session Manager should have similar system resources and a balanced number of devices.
Session Manager instances must be similarly sized in both processing power and available memory to accommodate distributions of devices during failover. Small and large footprints are not intended to be mixed in a solution. However, closely sized footprints, such as one size with the next size down in the table above, can be mixed temporarily as capacities increase. You must ensure that the number of devices failing over to a smaller footprint does not exceed the device capacities of that footprint.
You can implement a system that consists of a mixture of Session Manager instances hosted on VMware platforms as well as Session Manager instances hosted on the existing non-VMware platforms. You must configure the VMware-based Session Manager to be similar to the non-VMware-based Session Manager across the enterprise. Similar configurations ensure the best use of system resources and handling failover scenarios. Be careful when configuring the system where a large non-VMware Session Manager can failover to Session Manager running in VMware environment. You must ensure that the target Session Manager can handle the total capacities.
Avaya Aura® deployment supports a geo-redundant Session Manager configuration of up to 28 Session Manager instances that are interconnected and aware of each other. Configurations that exceed this limit are not expected to have problems, but these configurations are not guaranteed to be supported.
The following table summarizes the number of soft clients supported per Session Manager when the soft clients are using Avaya Aura® Device Services.
Session Manager profile
Total SIP devices
Number of Workplace devices
Previous Workplace devices
Profile 1
2,000
1,200
750
Profile 2
4,500
2,700
1350
Profile 3
7,000
4,200
2100
Profile 4
10,000
6,000
3000
Profile 5
23,300
13,900
5240
Profile 6
66,700
13,900
-