Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

HSRP Change discovered from logs

Hi Experts,

DO you know what is this error message?

.Jun 3 00:42:27.304 GMT: %HSRP-6-STATECHANGE: GigabitEthernet0/1.2 Grp 2 state Active -> Speak

.Jun 3 01:06:46.446 GMT: %HSRP-6-STATECHANGE: GigabitEthernet0/2.22 Grp 34 state Standby -> Active

.Jun 3 01:06:46.522 GMT: %HSRP-6-STATECHANGE: GigabitEthernet0/1.2 Grp 2 state Standby -> Active

.Jun 3 01:06:50.634 GMT: %HSRP-6-STATECHANGE: GigabitEthernet0/2.22 Grp 34 state Active -> Speak

I found quite a number of this in the router..

Is this normal?

cindy

1 ACCEPTED SOLUTION

Accepted Solutions

Re: HSRP Change discovered from logs

As per cisco there is no action required for this error.

If still theres problems in the network you may need to do some troubleshooting.

These error messages describe a situation in which a standby HSRP router did not receive three successive HSRP hello packets from its HSRP peer. The output shows that the standby router moves from the standby state to the active state. Shortly thereafter, the router returns to the standby state. Unless this error message occurs during the initial installation, an HSRP issue probably does not cause the error message. The error messages signify the loss of HSRP hellos between the peers. When you troubleshoot this issue, you must verify the communication between the HSRP peers. A random, momentary loss of data communication between the peers is the most common problem that results in these messages. HSRP state changes are often due to High CPU Utilization. If the error message is due to high CPU utilization, put a sniffer on the network and the trace the system that causes the high CPU utilization.

There are several possible causes for the loss of HSRP packets between the peers. The most common problems are physical layer problems or excessive network traffic caused by spanning tree issues. As with Case Study #1, all the troubleshooting modules are applicable to the resolution of HSRP state changes, particularly the Layer 3 HSRP Debugging.

below is the link.

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094afd.shtml#t1

Hope this helps.

regards,

pravin

7 REPLIES

Re: HSRP Change discovered from logs

HI Cindy, [Pls Rate if HELPS]

%HSRP-6-STATECHANGE: [chars] Grp [dec] state [chars] -> [chars]

The router has changed state

Recommended Action: No action is required.

Hope I am Informative.

Pls Rate if HELPS

Best Regards,

Guru Prasad R

Community Member

Re: HSRP Change discovered from logs

this is an indication of a problem with your HSRP reachability. Your active HSRP speaking router transitions from active to standby meaning it is swaping its role as the default gateway for your hosts on the segment to a different router which is the HSRP standby router.

This would indicate a L2 or L3 problem with your network if it is happening often it is defanitily a problem... it should not transition too often, so check your interfaces where HSRP and preemtion is configured.

Bronze

Re: HSRP Change discovered from logs

This indicates HSRP being transitioning states between active - standby.this basically mean the routers invovled in hsrp groups are tryin to move out from its assigned role (either active or standby) & go for a different role.

The cause could be possible flap of the interface on which hsrp is running or the one which is being tracked for hsrp to change states.

Pls check the interfaces involved for any logical or physical disruption for this happen.Repetitive messages of this kind are not healthy for the network.

Pls rate if this helps!!!

Re: HSRP Change discovered from logs

As per cisco there is no action required for this error.

If still theres problems in the network you may need to do some troubleshooting.

These error messages describe a situation in which a standby HSRP router did not receive three successive HSRP hello packets from its HSRP peer. The output shows that the standby router moves from the standby state to the active state. Shortly thereafter, the router returns to the standby state. Unless this error message occurs during the initial installation, an HSRP issue probably does not cause the error message. The error messages signify the loss of HSRP hellos between the peers. When you troubleshoot this issue, you must verify the communication between the HSRP peers. A random, momentary loss of data communication between the peers is the most common problem that results in these messages. HSRP state changes are often due to High CPU Utilization. If the error message is due to high CPU utilization, put a sniffer on the network and the trace the system that causes the high CPU utilization.

There are several possible causes for the loss of HSRP packets between the peers. The most common problems are physical layer problems or excessive network traffic caused by spanning tree issues. As with Case Study #1, all the troubleshooting modules are applicable to the resolution of HSRP state changes, particularly the Layer 3 HSRP Debugging.

below is the link.

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094afd.shtml#t1

Hope this helps.

regards,

pravin

Community Member

Re: HSRP Change discovered from logs

Pravin,

You are very right..looks like the Router having high cpu util of 65percent..and once rectified the problem..the log not showing of those info any more.

Re: HSRP Change discovered from logs

Hi cindy,

Its good to know that the problem has been resolved.

Thanks for the rating.

Community Member

Re: HSRP Change discovered from logs

Hi Cindy,

I have the same problem..

Can you share how to rectify cpu problem..?

Thanks..

206
Views
0
Helpful
7
Replies
CreatePlease to create content