11-06-2012 07:32 PM - edited 03-07-2019 09:54 AM
Hi Guys,
I have having two Cisco 6509 both working are my main Core Switches with which I have all my Layer 2 VLANs configured and then distributed thru the trunks links to all the Access Switches. I have L3- Vlans also configured on them with which one switch in primary and the other is secondary. All of sudden last night I got this message on my core switch 2 this for VLAN 1 which is my users LAN, how can I check as to what would have caused the core switch 2 HSRP to be active and then in standby
*Nov 5 23:33:29.296: %HSRP-5-STATECHANGE: Vlan1 Grp 5 state Standby -> Active
*Nov 5 23:33:29.796: %HSRP-5-STATECHANGE: Vlan1 Grp 49 state Standby -> Active
*Nov 5 23:33:29.804: %HSRP-5-STATECHANGE: Vlan1 Grp 49 state Active -> Speak
*Nov 5 23:33:29.920: %HSRP-5-STATECHANGE: Vlan1 Grp 5 state Active -> Speak
*Nov 5 23:33:40.144: %HSRP-5-STATECHANGE: Vlan1 Grp 5 state Speak -> Standby
*Nov 5 23:33:41.280: %HSRP-5-STATECHANGE: Vlan1 Grp 49 state Speak -> Standby
Also last night i got call from office saying that we are getting huge delay in pinging the default gateway of the user LAN which is the same vlan as the above and it was just for few minutes and then it was back to normal and now when I came to office and check there were no logs in both the core switches. When I checked the cpu utlization it was showing me high on both the switches how can I check as to what would have caused the CPU utilisation to go high all of suddedn can someone please help me. If need any more information please do let me know
INPMHCORS01#$ sh processes cpu his
11111 11111 11111 1111111111
8885555588888666669999922222666665555511111777773333300000
100
90
80
70
60
50
40
30
20 *****
10 **********************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
11
1111111110011111111111112111111111111111111111111111111111
3932444730053465722845850238575885556666623362443336645536
100 **
90 **
80 **
70 **
60 **
50 #*
40 #*
30 #*
20 * * ##* *** * **** ************** * ** ** *
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
1212121112281221333333321222111191181222333399322111211121181212121211
9280709780448039453324488320888898989101754234561787198717998092907088
100 *
90 * * ** *
80 * * * ** *
70 * * * ** *
60 * * * ** *
50 * * * ** *
40 * * * * ** *** *
30 * ******** * * ******** *
20 *****************######******************######***********************
10 ######################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
11-06-2012 09:34 PM
Hi Kevin,
Seems like you don't have enough info on your 6500's to troubleshoot.
Just check couple of these, if it helps:
1. Check the other 6500 which is in hsrp pair, may be it can give you some hints.
2. Is HSRP also linked to track ? If yes, just check if the link which was been tracked, showed something in NMS ( maybe).
3. Check the devices which are connected to 6500's. They can also give you some hints.
PS: Since you are doing post-incident analysis, troubleshooting is never straight forward.
Regards,
Smitesh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide