Specifications

Managing Redundancy Clusters Monitoring Cluster Status
16
ShoreTel Mobility Router Administration Guide 244
Monitoring Cluster Status
After you have configured the redundancy cluster, you can monitor its status. The Redundancy
monitoring page allows you to check the state of each Mobility Router and which one is the active
node.
Troubleshooting
The following lists issues you might encounter after implementing redundancy clusters and how to
verify your configuration.
The second Mobility Router fails to join the cluster and is in the Unknown state.
Both Mobility Routers are in the active state.
Communication between the active and standby nodes is required to maintain the redundancy
cluster and provide stateful high availability. Verify that the communication between the two
Mobility Routers is active by using the following troubleshooting commands:
 Troubleshooting > Commands > ping
 Troubleshooting > Commands > traceroute
Also verify that PortFast is enabled on the switch ports to which the Mobility Routers are
connected.
ShoreTel Mobility Client cannot communicate with the Mobility Router.
During initial provisioning, reprovisioning, or upgrading of the ShoreTel Mobility Client, verify that the
Mobility Router IP address specified is the virtual IP address of the redundancy cluster.
In the ShoreTel Mobility Client, verify that the IP address of the Mobility Router in the General
preferences is set to the virtual IP address of the redundancy cluster.
End users’ mobile devices cannot register to the Mobility Router.
End users do not get a registration icon on the mobile device.
This happens for one of the following reasons:
 The SIP server lost the PBX registration state of the user.
 The standby Mobility Router became the active node in the cluster without a failover occurring.
 The SIP server failed after the user was created but before responding to the registration
request to the PBX for the user.