[c-nsp] 7206VXR w/ Process Memory Parity Error

[Kim Onnel]

How about if i got
System returned to ROM by error - a Software forced crash, PC 0x60377264.

twice, associated with a self reload, on an RPM 

Cisco Internetwork Operating System Software
IOS (tm) RPM Software (RPM-JS-M), Version 12.2(14.4)T,  MAINTENANCE INTERIM SOF
WARE
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 13-Jan-03 22:17 by ccai
Image text-base: 0x60008954, data-base: 0x61748000

ROM: System Bootstrap, Version 12.2(4r)T1, RELEASE SOFTWARE (fc1)
BOOTLDR: RPM Software (RPM-BOOT-M), Version 12.2(8)T4,  RELEASE SOFTWARE (fc1)

RPM(r) uptime is 1 day, 9 minutes
System returned to ROM by error - a Software forced crash, PC 0x60377264
Running default software

cisco RPM-PR (NPE400) processor with 491520K/32768K bytes of memory.
R7000 CPU at 350Mhz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 Cache
Last reset from s/w peripheral
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
1 ATM network interface(s)
125K bytes of non-volatile configuration memory.

Any known bugs, recommended changes ?
On Sat, 26 Mar 2005 23:11:55 -0500, Jeff Kell <jeff-kell at utc.edu> wrote:
> Ted Mittelstaedt wrote:
> > cisco-nsp-bounces at puck.nether.net wrote:
> 
> >> I have a 7206VXR (NPE-300) that has been working fine as a border
> >> router for over two years. It reloaded itself last night, and the
> >> logs say that it was due to a "processor memory parity error".
> 
> >> Does anyone here have any experience with this type of error on the
> >>  7200-series? Should I write this incident off as a random glitch?
> 
> > If you have never updated IOS on this router for the last 2 years
> > it is suceptable to a number of remote attacks.
> 
> I have a 7204VXR/NPE-300 that crashed three times in the last six weeks
> with a "Software forced crash" (Block overrun, corrupted redzone)
> running 12.2(13)T12.  Have upgraded to 12.2(15)T15 (with TAC blessing)
> and so far so good.  It had been running quite some time (though not two
> years) without problems.  The "remote attack" scenario is an interesting
> alternative theory as this is an edge router (fed by DS3).
> 
> Jeff
> _______________________________________________
> 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/
>