Multinode Scalability Feature
Multinode Scalability Requirements
IM and Presence Service supports multinode scalability:
-
Six nodes per cluster
-
45,000 users per cluster with a maximum of 15,000 users per node in a full Unified Communication (UC) mode deployment
-
15,000 users per cluster in a presence redundancy group, and 45,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
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. |