About Presence Redundancy Group Setup
In Cisco Unified CM Administration user interface, use the menu path to create a presence redundancy group consisting of two IM and Presence Service nodes from the same cluster.
For information about how to enable high availability for the presence redundancy group, or to initiate a manual node failover, fallback, and recovery, see the Cisco Unified Communications Manager Features and Services Guide.
Presence Redundancy Groups and High Availability
-
Failover - Occurs in a presence redundancy group when one or more critical services fails on an IM and Presence Service node in the group or a node in the group fails. Clients automatically connect to the other IM and Presence Service node in that group.
-
Fallback - Occurs when a fallback command is issued from the Command Line Interface (CLI) or Cisco Unified Communications Manager during either of these conditions:
-
The failed IM and Presence Service node comes back into service and all critical services are running. The failed over clients in that group reconnect with the recovered node when it becomes available.
-
The backup activated IM and Presence Service node fails due to a critical service failure, and the peer node is in the Failed Over state and supports the automatic recovery fallback.
-
-
A critical service on Node A fails—A critical service (for example, the Presence Engine) fails on Node A. Automatic failover occurs and all users are moved to Node B. Node A is in a state called "Failed Over with Critical Services Not Running". When the critical service recovers, the node state changes to "Failed Over." When this occurs Node B tracks the health of Node A for 30 minutes. If no heartbeat is missed in this timeframe and the state of each node remains unchanged, automatic fallback occurs.
-
Node A is rebooted—Automatic failover occurs and all users are moved to Node B. When Node A returns to a healthy state and remains in that state for 30 minutes automatic fallback will occur.
-
Node A loses communications with Node B—Automatic failover occurs and all users are moved to Node B. When communications are re-established and remain unchanged for 30 minutes automatic fallback will occur.
You can manually initiate a node failover, fallback, and recovery of IM and Presence Service nodes in the presence redundancy group. A manual fallback operation is required unless the automatic fallback option is set.
For instructions to set up presence redundancy groups and high availability, see Cisco Unified Communications Manager Administration Guide.
Presence Redundancy Groups and High Availability Considerations
Presence Redundancy Group Interactions and Limitations
Consider the following when configuring presence redundancy groups using Cisco Unified CM Administration:
-
Each presence redundancy group requires at least one IM and Presence Service node assigned to it, and each can support up to two IM and Presence Service nodes.
-
An IM and Presence Service node can be assigned to only one presence redundancy group.
-
Both nodes in the presence redundancy group must be running the same version of IM and Presence Service software.
-
Both nodes in the presence redundancy group must be on the same cluster and have the same IM and Presence Service database publisher node.
-
The IM and Presence node does not need to be collocated with the Cisco Unified Communications Manager publisher node.
-
For WAN deployments, a minimum of 10 megabits per second of dedicated bandwidth is required for each IM and Presence cluster, with no more than an 80 millisecond round-trip latency. Any bandwidth less than this recommendation can adversely impact performance.
-
The Cisco Jabber client can be either local or remote to the IM and Presence Service node.