Specifications

Managing Redundancy Clusters Troubleshooting
16
ShoreTel Mobility Router Administration Guide 245
Check the Mobility Router log and search for “503 Policy Check Failure.” If you see this message, the
SIP server needs to reregister with the PBX to get the new registration state to respond to the client’s
registration request. To do this, do one of the following:
 Disable the user, and then enable the user again.
 Wait for the timeout of 180 seconds so that the SIP server sends a new PBX registration
request.
Users on Wi-Fi calls see delayed response after failover.
If a user is on an active Wi-Fi call when failover occurs, the ShoreTel Mobility Client makes a Hold
request to the Mobility Router. It can take at least 6 to 10 seconds for the Mobility Router to receive the
request.
This situation occurs when a WLAN controller filters ARP broadcast requests. After switchover, the
new active Mobility Router ARP broadcast is not received by the ShoreTel Mobility Client. After
multiple attempts, the ShoreTel Mobility Client makes an ARP request to get the MAC address of the
new active Mobility Router. The requests are now received by the active Mobility Router.
To avoid this situation, the active and standby Mobility Routers should not be in the same subnet as
the WLAN controller.
Continuous switchover occurs.
This might be caused by service failure. Look at the Mobility Router log and check if one of the Mobility
Router services has failed.
Access the physical IP address of one of the Mobility Routers and disable the cluster. The other
Mobility Router is still in the cluster and is the active node. Look at the Mobility Router log of the active
node for service failures. Verify the configuration of the active node to make sure that everything is
configured properly. After you have confirmed that the configuration is appropriate and the Mobility
Router services are stable, then add the other Mobility Router back into the redundancy cluster.