That means the supervisor have crashed, reloaded and became the standby. You should look for "crashinfo" files on the bootflash: of the supervisor which have crashed (now standby). Looking into those crashinfo files you might either find some clue about the reason, or you can upload it to the Output Interpreter on Cisco.com, or open a TAC case attaching those files.
Best regards, Andras On Tue, Mar 26, 2013 at 5:19 PM, Peter Kranz <[email protected]> wrote: > Had a 6506-E running redundant Sup2T's perform a failover from ACTIVE to > HOT > STANDBY yesterday with nothing showing in the logs right after the hourly > RANCID collection completed. Running > s2t54-advipservicesk9-mz.SPA.122-50.SY3.bin > > Anyone seen this? > > > > Peter Kranz > Founder/CEO - Unwired Ltd > www.UnwiredLtd.com <http://www.unwiredltd.com/> > Desk: 510-868-1614 x100 > Mobile: 510-207-0000 > [email protected] <mailto:[email protected]> > > > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
