Core issue
Hot Standby Router Protocol (HSRP) changes its state when it fails to receive three consecutive HSRP hello packets from its peer, indicating the hello packets are getting dropped.
These are the most common issues:
- Physical layer problems or excessive network traffic, which are caused by Spanning-Tree Protocol (STP) problems
- Misconfiguration of HSRP
- High CPU Utilization
Note: The frequent change of HSRP state indicates a configuration issue.
Resolution
To resolve the issue, refer to one of these solutions:
- If the error message is due to misconfiguration of HSRP (standby priority command and standby track command), reconfigure the HSRP on the switch. For more information on standby priority command and standby track command, refer to How to Use the standby preempt and standby track Commands.
- If the error message is due to physical layer problems or excessive network traffic, then check for interface issues. To resolve the interface issue causing this error message, refer to Verify Physical Layer Connectivity.
- If the error message is due to high CPU utilization, put a sniffer on the network and the trace the system that causes high CPU utilization.
To determine if HSRP packets are being sent and received correctly, issue the debug standby packet command.
For more information, refer to the Layer 3 HSRP Debugging section of Understanding and Troubleshooting HSRP Problems in Catalyst Switch Networks.
Error message
%STANDBY-6-STATECHANGE