Multinode Scalability Feature
Multinode Scalability Requirements
IM and Presence Service supports multinode scalability:
-
Six nodes per cluster
-
75,000 users per cluster with a maximum of 25,000 users per node in a full Unified Communication (UC) mode deployment
-
25,000 users per cluster in a presence redundancy group, and 75,000 users per cluster in a deployment with High Availability.
-
Administrable customer-defined limit on the maximum contacts per user (default unlimited)
-
The IM and Presence Service continues to support intercluster deployments with the multinode feature.
Scalability depends on the number of clusters in your deployment. For detailed VM configuration requirements and OVA templates, see Virtualization for Unified CM IM and Presence at the following url: http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CM_IM_and_Presence
OVA Requirements
The following OVA requirements apply:
-
For intercluster deployments, you must deploy a minimum OVA of 15,000 users. It is possible to have different clusters running different OVA sizes so long as all clusters are running at least the 15,000 user OVA.
-
For Persistent Chat deployments, we recommend that you deploy a minimum OVA of 15,000 users.
-
For Centralized Deployments, we recommend the 25,000 user IM and Presence OVA with a minimum OVA of 15,000 users. The 15,000 user OVA can grow to 25,000 users. With a 25K OVA template, and a six-node cluster with High Availability enabled, the IM and Presence Service central deployment supports up to 75,000 clients. To support 75K users with 25K OVA, default trace level for XCP router needs to be changed from Info to Error. For the Unified Communications Manager publisher node in the central cluster, the following requirements apply:
-
A 25,000 IM and Presence OVA (maximum 75,000 users) can be deployed with a 10,000 user OVA installed on the central cluster's Unified Communications Manager publisher node
-
A 15,000 IM and Presence OVA (maximum 45,000 users) can be deployed with a 7,500 user OVA installed on the central cluster's Unified Communications Manager publisher node
-
Note |
If you plan to enable Multiple Device Messaging, measure deployments by the number of clients instead of the number of users as each user may have multiple Jabber clients. For example, if you have 25,000 users, and each user has two Jabber clients, your deployment requires the capacity of 50,000 users. |
Scalability depends on the number of clusters in your deployment. For detailed VM configuration requirements and OVA templates, see Virtualization for Unified CM IM and Presence at the following url: https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-ucm-im-presence.html.
Scalability Options for Deployment
IM and Presence Service clusters can support up to six nodes. If you originally installed less than six nodes, then you can install additional nodes at any time. If you want to scale your IM and Presence Service deployment to support more users, you must consider the multinode deployment model you have configured. The following table describes the scalability options for each multinode deployment model.
Deployment Mode |
Scalability Option |
|||
---|---|---|---|---|
Add a New Node to an Existing Presence Redundancy Group |
Add a New Node to a New Presence Redundancy Group |
|||
Balanced Non-Redundant High Availability Deployment |
If you add a new node to an existing presence redundancy group, the new node can support the same number of users as the existing node; the presence redundancy group can now support twice the number of users. It also provides balanced High Availability for the users on the existing node and the new node in that presence redundancy group. |
If you add a new node to a new presence redundancy group, you can support more users in your deployment. This does not provide balanced High Availability for the users in the presence redundancy group. To provide balanced High Availability, you must add a second node to the presence redundancy group. |
||
Balanced Redundant High Availability Deployment |
If you add a new node to an existing presence redundancy group, the new node can support the same users as the existing node. For example, if the existing node supports 5000 users, the new node supports the same 5000 users. It also provides balanced redundant High Availability for the users on the existing node and the new node in that presence redundancy group.
|
If you add a new node to a new presence redundancy group, you can support more users in your deployment. This does not provide balanced High Availability for the users in the presence redundancy group. To provide balanced High Availability, you must add a second node to the presence redundancy group. |
||
Active/Standby Redundant High Availability Deployment |
If you add a new node to an existing presence redundancy group, you provide High Availability for the users in the existing node in the presence redundancy group. This provides a High Availability enhancement only; it does not increase the number of users you can support in your deployment. |
If you add a new node in a new presence redundancy group, you can support more users in your deployment. This does not provide High Availability for the users in the presence redundancy group. To provide High Availability, you must add a second node to the presence redundancy group. |