Specifications

Managing Redundancy Clusters About Redundancy Clusters
16
ShoreTel Mobility Router Administration Guide 228
About Redundancy Clusters
A redundancy cluster consists of two ShoreTel Mobility Router 4000 or 6000 Series appliances. Each
redundancy cluster must have a unique cluster name.
Failover occurs due to the following:
 The active node is powered off.
 The eth0 interface cable of the active node is removed or disconnected.
 SIP server, Mobility server, Remote Access server, Session Logger server or HMP server failure
on the active node.
In a redundancy cluster, a “heartbeat” packet is sent every two seconds from the active node to the
standby node. If the standby node fails to receive five consecutive heartbeats, it becomes the
active node, and a failover occurs.
Redundancy clusters provide the following:
 Synchronization of configuration and state information between the active and standby nodes. The
active node sends this information to the standby node. Synchronization occurs due to the
following events:
 A standby node joins the cluster.
 The standby node becoming the active node.
 The transition as an active node becomes a standby node.
 The following information is not synchronized:
 Interface settings
 Mobility Router certificate
 Mobility Router logs
 Active calls are not dropped during a failover, including multiple separate calls and three-way
conference calls. Calls on hold remain on hold during failover.
 Users retain their registration state after failover.
 CDR information is retained after failover.
Note
Clustering is not supported on ShoreTel Mobility Router 2000 Series appliances.