Supported footprints for Session Manager

Last Updated : Sep 27, 2024 |
Prolog information
The following table summarizes single Session Manager capacities for all Session Manager footprints:
Note:
Avaya Aura® Session Manager supports VMware hosts with Hyperthreading enabled at the BIOS level.
The terms mebibyte and megabyte are closely related and often used as synonyms, though they don't technically refer to the same amount of capacity. However, they are close in size, One mebibyte equals 1.048576 megabytes.
Session Manager Device Footprints
Up to 2K Devices
2K to 4.5K Devices
4.5K to 7K Devices
7K to 10K Devices
(R1 footprint)
10K to 23.3K Devices
(R2 footprint)
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
5132 MiB
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 Software-Only ISO (GiB)3
100
100
135
135
210
210
Note:
  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. You can deploy the Session Manager software-only ISO image on VMware, KVM, Hyper-V, Amazon Web Services, Google Cloud Platform, and Microsoft Azure platforms.