redundancy group is comprised of two
IM and Presence Service nodes from the same cluster. Each
node in the presence redundancy group monitors the status, or heartbeat, of the peer node. You can configure a presence redundancy group to provide both redundancy and recovery for
IM and Presence Service clients and applications.
Failover—Occurs in a presence redundancy group when one or more critical services fails
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 CLI or Cisco Unified Communications Manager during either of these conditions:
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.
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.
For example, if you are using
presence redundancy groups, Cisco Jabber clients will fail over to a backup
IM and Presence Service node if the services or
hardware fail on the local
IM and Presence Service node. When the failed node
comes online again, the clients automatically reconnect to the local
IM and Presence Service node if you have configured automatic fallback. If you have not configured automatic fallback, you can manually initiate the fallback when the failed node
In addition to redundancy and recovery, presence redundancy groups also allow you to configure high availability for your cluster.
The IM and Presence Service supports high availability for multiple-node deployments.
After you configure a
presence redundancy group, you can enable high availability for
the group. A pair
of nodes is required for high availability. Each node has an
independent database and set of users operating with a shared
availability database that is able to support common users.
All IM and Presence
Service nodes must belong to a presence redundancy group,
which can consist of a single IM and Presence Service
node or a pair of IM and Presence Service nodes.
You can configure high availability using two different modes:
Balanced mode: This mode provides redundant high availability with automatic user load balancing and
user failover in the event that one nodes fails because of component
failure or power outage.
Active/standby mode: The standby
node automatically takes over for the active node if the active
node fails. It does not provide automatic load balancing.
We recommend that you configure your IM and Presence Service deployments as high availability deployments. Although you are permitted to have both high availability and non-high availability presence redundancy groups configured in a single deployment, this configuration is not recommended.
Presence Redundancy Group Prerequisites
For deployments over the WAN, a minimum of 10 megabits per second of dedicated bandwidth is required for each IM and Presence Service cluster, with no more than an 80-millisecond round-trip latency. Any bandwidth less than this recommendation can adversely impact performance.
Redundancy Group Task Flow
IM and Presence Service node can be assigned to only
one presence redundancy group. For high availability, you must assign two nodes
from the same cluster to the presence redundancy group and enable high
availability for the group.
critical services are running on the nodes that you plan to add to a presence redundancy group. Critical services must be running before you
turn on high availability. If critical services are not running
on either node, the presence redundancy group will go into a Failed state when you turn on
high availability. If critical services are not running on one node, then that
node fails over to the other node when you turn on high availability.
Use Cisco Unified Communications Manager to configure redundancy for IM and Presence Service nodes.
Each presence redundancy group can contain two IM and Presence Service nodes. Each node can be assigned to only one presence redundancy group. 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 Service provides an automatic failure detection mechanism for presence redundancy groups. Each node in the presence redundancy group monitors the status, or heartbeat, of the peer node. You can configure the intervals at which the nodes monitors its peer.
In Cisco Unified CM IM and Presence Administration, choose System > Service Parameters > Server Recovery Manager (service).
Under General Server Recovery Manager Parameters (Clusterwide), configure the following parameters:
Heart Beat Interval: This parameter specifies how often in seconds the Server Recovery Manager sends a heartbeat message to the peer Server Recovery Manager in the same presence redundancy group. The heartbeat is used to determine network availability. The default value is 60 seconds.
Connect Timeout: This parameter specifies how long in seconds the Server Recovery Manager waits to receive a response from a connection request to the peer Server Recovery Manager. The default value is 30 seconds.
Cisco recommends that you configure these parameters with the default values.
What to Do Next
If you did not enable high availability when you configured the presence redundancy group, Enable High Availability now.
Enable High Availability
Failure to set up replication in the
IM and Presence Service cluster and ensure that all critical services are running may result in an immediate failover when high availability is enabled for the presence redundancy group.