Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

2610XM with 12.2.13 - Unknown reason of system restart

Hello,

We have started deployment of 2610XM with 12.2.13(is) on one of our customers network, and after few days running 12.2.13, I have noticed that most of these routers show an unknown reason of restart.

Typically, "show ver" output is :

#sho ver

Cisco Internetwork Operating System Software

IOS (tm) C2600 Software (C2600-IS-M), Version 12.2(13), RELEASE SOFTWARE (fc1)

Copyright (c) 1986-2002 by cisco Systems, Inc.

Compiled Tue 19-Nov-02 23:38 by pwade

Image text-base: 0x8000808C, data-base: 0x810FA00C

ROM: System Bootstrap, Version 12.2(7r) [cmong 7r], RELEASE SOFTWARE (fc1)

pbtv007 uptime is 2 weeks, 1 day, 20 hours, 56 minutes

System returned to ROM by <==No reason

System restarted at 15:23:48 UTC Wed Aug 27 2003

System image file is "flash:c2600xm-is-mz.122-13.bin"

cisco 2610XM (MPC860P) processor (revision 0x100) with 61440K/4096K bytes of memory.

Processor board ID JAD07110RKR (3342348699)

M860 processor: part number 5, mask 2

Bridging software.

X.25 software, Version 3.0.0.

1 FastEthernet/IEEE 802.3 interface(s)

1 Serial network interface(s)

32K bytes of non-volatile configuration memory.

16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

So, TAC engineering says we should not worry about this as there no indication of software or hardware failure.

I was wondering if somebody has already face similar issue, and if there is any explanation to such "unknown" reason of system restart.

You advice will be appreciated...

Thanks & Brgds,

HA

1 REPLY
New Member

Re: 2610XM with 12.2.13 - Unknown reason of system restart

Hi, HA,

This means that the system tried to save information about the crash into NVRAM but didn't succeed.

This is why the stack is empty and the crash is unknown.

Basically, when the box reloads, we set some variable in NVRAM according to why we reloaded. This

could be a bus error, software forced crash, a parity error, or hardware.

TAC needs to collect more info to anylize this. You may upgrade to the next code to see if the problem raise again.

Regards,

/Bessie

190
Views
0
Helpful
1
Replies
CreatePlease login to create content