[c-nsp] 6500 - stateful failover, reason?

[Matlock, Kenneth L]

Those log messages are spurious. 

When a supervisor comes online a lot of things are in an 'unknown' state
by the backup (soon to be primary) supervisor. When it initializes as
the Active, it checks the status of everything such as power supplies.
What you're seeing is just the supervisor 'finding' all the gear it's
now responsible for, and marking the current status.

A 'show ver' will show you three things. 

"CAT6509SJHSS1 uptime is 1 year, 33 weeks, 2 days, 23 hours, 50 minutes"

Shows that the chassis has had at least 1 active supervisor for 1 year,
33 week.

"Time since CAT6509SJHSS1 switched to active is 2 weeks, 6 days, 9
hours, 40 minutes"

That shows the current supervisor has been the active for 2 weeks, 6
days. 

"System returned to ROM by Stateful Switchover (SP by power on)"

That shows the reason for the last switchover (in this case we had to
switch to the standby sup because of a nasty memory leak, caused by...
'show run'.

Ken Matlock
Network Analyst
Exempla Healthcare
(303) 467-4671
matlockk at exempla.org


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Drew Weaver
Sent: Tuesday, September 22, 2009 12:38 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] 6500 - stateful failover, reason?

Is there any way to get more information about what caused a fail-over
between two supervisors in a 6500?

All I can appear to get is "Active crashed." from show redundancy
switchover and my syslog doesn't have any information either.

Also, is it normal that during switchover you will lose protocols (OSPF)
and that you will see messages like these in the log?

Sep 22 08:41:17.651 EDT: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
Sep 22 08:41:17.699 EDT: %C6KPWR-SP-4-PSOK: power supply 2 turned on.

The log messages sort of confuse me because show version indicates:

uptime is 10 weeks, 4 days, 1 hour, 35 minutes

So it's been up 10 weeks but the power supplies were just turned on < 12
hours ago? I assume that is just random log-spew from the hot-supervisor
taking over, though?

-Drew

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/