[c-nsp] Weird error
Ziv Leyes
zivl at gilat.net
Mon Feb 25 05:00:19 EST 2008
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.
************************************************************************************
More information about the cisco-nsp
mailing list