[c-nsp] Mysterious 7513 reboot

[Rodney Dunn]

The RSP4 doesn't have parity correction.

Monitor and replace on a second occurrence.

Rodney

On Tue, Apr 25, 2006 at 11:58:51PM -0700, Jeff Chan wrote:
> We had a 7513 RSP4 reboot itself mysteriously with the memory
> parity error message:
> 
> __
> 
> #sh ver
> Cisco Internetwork Operating System Software
> IOS (tm) RSP Software (RSP-PV-M), Version 12.3(13), RELEASE SOFTWARE (fc2)
> Technical Support: http://www.cisco.com/techsupport
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Thu 10-Feb-05 05:26 by ssearch
> Image text-base: 0x40010AFC, data-base: 0x41D0E000
> 
> ROM: System Bootstrap, Version 11.1(8)CA1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
> BOOTLDR: RSP Software (RSP-BOOT-M), Version 12.0(25)S, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
> 
> supranet01 uptime is 13 minutes
> System returned to ROM by processor memory parity error at PC 0x407783D0, address 0x0 at 00:30:50 CDT Wed Apr 26 2006
> System restarted at 00:33:32 CDT Wed Apr 26 2006
> System image file is "disk0:rsp-pv-mz.123-13.bin"
> 
> cisco RSP4 (R5000) processor with 262144K/2072K bytes of memory.
> R5000 CPU at 200MHz, Implementation 35, Rev 2.1, 512KB L2 Cache
> Last reset from power-on
> G.703/E1 software, Version 1.0.
> G.703/JT2 software, Version 1.0.
> X.25 software, Version 3.0.0.
> Bridging software.
> Primary Rate ISDN software, Version 1.1.
> Chassis Interface.
> 4 VIP2 R5K controllers (2 FastEthernet)(16 Serial)(4 HSSI)(2 Channelized T3).
> 2 FastEthernet/IEEE 802.3 interface(s)
> 71 Serial network interface(s)
> 4 HSSI network interface(s)
> 2 Channelized T3 port(s)
> 123K bytes of non-volatile configuration memory.
> 
> 47040K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
> 40960K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
> 8192K bytes of Flash internal SIMM (Sector size 256K).
> 
> Slave in slot 7 is running Cisco Internetwork Operating System Software
> IOS (tm) RSP Software (RSP-DW-M), Version 12.3(13), RELEASE SOFTWARE (fc2)
> Technical Support: http://www.cisco.com/techsupport
> Copyright (c) 1986-2005 by cisco Systems, Inc.
> Compiled Thu 10-Feb-05 05:35 by ssearch
> Slave: Loaded from system
> Slave: cisco RSP4 (R5000) processor with 262144K bytes of memory.
> 
> Configuration register is 0x2102
> 
> __
> 
> 
> which according to anecdotes we should perhaps attribute to Cosmic
> rays.
> 
> However we're also seeing these error messages on an attached
> 5000 switch with RSM:
> 
> Apr 26 00:36:19 switch01 2006 Apr 26 00:15:51 %MLS-4-RESUMESC:Resume MLS
> after detecting too many moves
> Apr 26 00:36:19 switch01 2006 Apr 26 00:15:51 %MLS-4-MOVEOVERFLOW:Too
> many moves, stop MLS for 5 sec(40000000)
> Apr 26 00:36:24 switch01 2006 Apr 26 00:15:56 %MLS-4-RESUMESC:Resume MLS
> after detecting too many moves
> Apr 26 00:36:24 switch01 2006 Apr 26 00:15:56 %MLS-4-MOVEOVERFLOW:Too
> many moves, stop MLS for 5 sec(40000000)
> Apr 26 00:36:29 switch01 2006 Apr 26 00:16:01 %MLS-4-RESUMESC:Resume MLS
> after detecting too many moves
> Apr 26 00:36:29 switch01 2006 Apr 26 00:16:01 %MLS-4-MOVEOVERFLOW:Too
> many moves, stop MLS for 5 sec(40000000)
> Apr 26 00:36:34 switch01 2006 Apr 26 00:16:07 %MLS-4-RESUMESC:Resume MLS
> after detecting too many moves
> Apr 26 00:36:34 switch01 2006 Apr 26 00:16:07 %MLS-4-MOVEOVERFLOW:Too
> many moves, stop MLS for 5 sec(40000000)
> 
> Should we be using MLS?   It's currently disabled on the router.
> 
> 
> We also have JFFNMS monitoring the router and under CPU, TCP we
> logged 2G in outbound connection attempts around the time of
> the reboot.
> 
> Clues, pointers, hints gratefully accepted.
> 
> Jeff C.
> -- 
> Jeff Chan
> mailto:cisco-nsp at jeffchan.com
> http://www.supranet.net/
> 
> _______________________________________________
> 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/