Antonio, Were crashinfo files generated by the RP & SP? If yes, feel free to unicast and I'll take a look.
eninja www.multiven.com - simple, efficient & affordable maintenance for all networks™ On Nov 5, 2010, at 3:27 PM, "Antonio Soares" <[email protected]> wrote: > The active crashed, that’s why it was not responding to the standby. The > standby also crashed what was bad since the 6500 went completely down. Both > SUPs went to rommon… > > > > I’m the maintenance service provider here J > > > > > > Thanks. > > > > Regards, > > > > Antonio Soares, CCIE #18473 (R&S/SP) > [email protected] > > > > From: Eninja [mailto:[email protected]] > Sent: sexta-feira, 5 de Novembro de 2010 20:24 > To: Antonio Soares > Cc: cisco-nsp > Subject: Re: [c-nsp] %PFREDUN-SP-STDBY-6-STANDBY: Failure of ACTIVE processor > detected, resetting > > > > The question is why did the active SP fail to respond to heartbeat messages > from the standby? > > > > Grab the sh tech, crashinfo files from the former active SP and contact your > maintenance service provider to troubleshoot. > > > > eninja > > > > www.multiven.com - simple, efficient & affordable maintenance for all > networks™ > > > > > > On Nov 5, 2010, at 10:46 AM, "Antonio Soares" <[email protected]> wrote: > > Hello group, > > Another problem I have my hands: > > ++++++++++++++++++++++++++++++++++++++++++++++ > 00:02:43: %PFREDUN-SP-STDBY-6-STANDBY: Active not responding, will be taken > down in 15 sec > 00:02:43: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to > ensure console debugging output. > > 00:02:58: %PFREDUN-SP-STDBY-6-STANDBY: Failure of ACTIVE processor detected, > resetting > 00:02:43: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to > ensure console debugging output. > > 00:02:58: %PFREDUN-SP-STDBY-6-STANDBY: Failure of ACTIVE processor detected, > resetting > 00:02:58: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to > ensure console debugging output. > > %Software-forced reload > > 00:04:31: SP-STDBY: Failed to send heartbeat poison message > > Breakpoint exception, CPU signal 23, PC = 0x402DF304 > ++++++++++++++++++++++++++++++++++++++++++++++ > > The Standby crashed because it lost contact with the active ??? In fact the > active crashed, but I was expecting to have the Standby to take the > ownership of the box, not crashing as well. Do we call this redundancy ? :) > > I don't find anything with bug toolkit. > > 6500 running 12.2.18SXF15a. > > Is this a new bug ? > > > Thanks. > > Regards, > > Antonio Soares, CCIE #18473 (R&S/SP) > [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/
