Re: AS5300 crashes

dboutell · ‎01-10-2003

One of my AS5300's, which has been giving me lots of problems with crashing, is failing to auto-configure modems. The modems are first marked at bad (B) with and error code of 21 or an error code of FFFFFF.

Last night it marked three different blocks of 6 bad and the only way that I could get them back was by doing a system reload.

The system log shows modems being marked bad as soon 1 - 1/2 hours after system reload. It shows the above error codes. It seems that it will mark six as bad and then start a firmware download on 12.

Is this normal? Is it possible that this machine has bad ram or not enough ram?

tepatel · ‎01-10-2003

Modem marked BAD or B on AS5300 is a known issue in the older image now. So need to know which image you have on AS5300 along with modem version too.

Now to troubleshoot crash issues, you can capture "sh stack" and use output interpreter tool to decode that. Pl. visit following url for that

https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl

Select sh stack from the pool down manu.

pakkanen · ‎01-11-2003

I'd like to use the tool as well, but unfortunately plain CCO access doens't qualify for the tool... what is the idea of restricting about all support to the contract customers?? I don't know any other company who restricts even basic support like Cisco.

tepatel · ‎01-11-2003

I can try to decode it if you post sh stack here.

dboutell · ‎01-13-2003

How do I find out what image that I have?

Sh stack:

AS5300#sh stack

Minimum process stacks:

Free/Size Name

5704/6000 Reset ipc queue

5600/6000 Microcom DSP download Process

9492/12000 Init

5296/6000 RADIUS INITCONFIG

10480/12000 Mica board Download

4584/6000 Mica slot Download

4736/6000 Modem Autoconfigure

8144/9000 DHCP Client

10640/12000 Exec

5728/6000 Async tty Reset

9920/12000 Virtual Exec

9936/12000 HTTP Server

Interrupt level stacks:

Level Called Unused/Size Name

2 110752466 7244/9000 Low IRQ Int Handler

3 1543114 7344/9000 High IRQ Int Handler

4 3399954 8640/9000 Console Uart

6 0 9000/9000 Parity interrupt

7 79371974 8604/9000 NMI Interrupt Handler

AS5300#

tepatel · ‎01-13-2003

show version command will tell you that. Looks like you have manually reboot the nas as "sh stack" doesn't have stack trace of the last crash.

Capture "sh stack" once the router reboots itself. stack trace will be lost with Manual reload or power off/on,

dboutell · ‎01-13-2003

Here is show vers

Do I do a show stack the next time that I have modems marked (B) and then post that?

AS5300#show vers

Cisco Internetwork Operating System Software

IOS (tm) 5300 Software (C5300-I-M), Version 12.1(7), RELEASE SOFTWARE (fc1)

Compiled Fri 23-Feb-01 00:22 by kellythw

Image text-base: 0x60008948, data-base: 0x6082C000

ROM: System Bootstrap, Version 12.0(2)XD1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

BOOTFLASH: 5300 Software (C5300-BOOT-M), Version 12.0(4)T1, RELEASE SOFTWARE (fc1)

AS5300 uptime is 3 days, 19 hours, 6 minutes

System returned to ROM by reload

System image file is "flash:c5300-i-mz.121-7.bin"

cisco AS5300 (R4K) processor (revision A.32) with 65536K/16384K bytes of memory.

Processor board ID 17920911

R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache

Bridging software.

X.25 software, Version 3.0.0.

Primary Rate ISDN software, Version 1.1.

Backplane revision 2

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30,

Board Hardware Version 3.1, Item Number 800-2544-3,

Board Revision D0, Serial Number 17920911,

PLD/ISP Version 0.0, Manufacture Date 8-Mar-2000.

1 Ethernet/IEEE 802.3 interface(s)

1 FastEthernet/IEEE 802.3 interface(s)

196 Serial network interface(s)

192 terminal line(s)

8 Channelized T1/PRI port(s)

--More--

tepatel · ‎01-13-2003

You can see that the "System returned to ROM by reload " so that makes the stack info lost. Post sh stack after router reboots on its own and come back up next time.

dboutell · ‎01-13-2003

That's always been my big problem -- it will not reboot on it's own -- It crashes, freezes and will never reboot. I have seen it go over two hours without rebooting itself.