[c-nsp] Rancid causing reload SUP2T 12.2.50-SY3

Tóth András diosbejgli at gmail.com
Tue Mar 26 17:42:20 EDT 2013


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 <pkranz at unwiredltd.com> 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
> pkranz at unwiredltd.com <mailto:pkranz at unwiredltd.com>
>
>
>
>
>
> _______________________________________________
> 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/
>


More information about the cisco-nsp mailing list