[c-nsp] Weird error

[Ziv Leyes]

Just another detail, now I've switched the router back on while connected to console and after passing the bootstrap and image decompression its running millions of lines saying

Corrected ECC from L2 cache or memory

Could anyone shed some light here?
Thanks,
Ziv



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Ziv Leyes
Sent: Monday, February 25, 2008 12:00 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Weird error

Hi,
One of our border routers (7200 VXR NPE-G1) went down and when we connected console and restart it it gave this weird error:

%SYS-1-MTNOTFENCED: Expired timer is not fenced, timer = 0, type 0
*** System received a Software forced crash ***
Signal= 0x17, code= 0x24, context= 0x63059804
 PC = 0x607f156c, SP = 0x80007d10, RA = 0x607ef5b4
 Cause Reg = 0x00000024, Status Reg = 0x3400ff03

The only thing I could find on Cisco is a reference to different platforms

Here http://www.cisco.com.ru/univercd/cc/td/doc/product/ong/on_15300/ons15304/rn15304.htm it says this:
Symptom: The system will reboot after printing a message similar to:
%SYS-1-MTNOTFENCED: Expired timer is not fenced, timer = 0, type 0
%Software-forced reload
Condition: This has only been observed when repeated equipment protection switching has occurred due to operator input.
Workaround: There are no known workarounds for this problem. The system will automatically switch to the standby SAM when the affected SAM reboots.

Here http://www.cisco.com.ru/univercd/cc/td/doc/product/ong/on_15300/ons15304/rn15304.htm it says:
Under rare circumstances, the system may reboot with the following error message.
%SYS-1-MTNOTFENCED: Expired timer is not fenced, timer = 0,
type 0

%Software-forced reload
There are no known workarounds.


"NO KNOWN WORKAROUNDS"??? Does it mean I need to put the router in the trash bin and buy a new one???
C'mon Cisco guys, your  programmers created that error to be printed in a specific circumstance and you can't tell what is the reason nor a workaround??? What are those "rare" circumstances???




************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

_______________________________________________
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/





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************





 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************