Cisco 1720: Boot failure, hang, not accepting inputs

[PanzerBoxb]

Having been out of the Cisco world since my days with a couple of AGS+ boxes I find myself dealing with a problematic 1720. I have the device connected via the console port to a Windows box running HyperTerm 6.3. With all components installed the device boots, decompresses the image, and produces the following results:

Cisco Internetwork Operating System Software
IOS (tm) C1700 Software (C1700-OY-M), Version 12.0(3)T3, RELEASE SOFTWARE (fc1)

Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 15-Apr-99 13:40 by kpma
Image text-base: 0x80008088, data-base: 0x8053D1D8

cisco 1720 (MPC860) processor (revision 0x501) with 15360K/5120K bytes of memory
.
Processor board ID JAD042603R6 (1808620819), with hardware revision 0000
M860 processor: part number 0, mask 32
Bridging software.
X.25 software, Version 3.0.0.
1 FastEthernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
WIC T1-DSU
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)

Building configuration...



Press RETURN to get started!

Passed
00:00:07: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
00:00:07: %LINK-3-UPDOWN: Interface Serial0, changed state to down
00:00:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed
state to up
00:00:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state
to down
00:00:18: %SYS-5-CONFIG_I: Configured from memory by console
00:00:18: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) C1700 Software (C1700-OY-M), Version 12.0(3)T3, RELEASE SOFTWARE (fc1)

Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 15-Apr-99 13:40 by kpma

At this point the system sits and does not respond to any input, even sending breaks during the boot sequence. After searching this site and others I attempted boots without the T1 interface, DRAM, and flash in an effort to isolate any potential defective hardware. After removing the flash the device errors out and presents me the rommon prompt, but it does not appear to be accepting any input. I've double checked my terminal settings and all appears to be in order there so I am at my wits end. Any thoughts or recommendations would be most welcome.

 

[rajunvm]

Hi,

I had faced a similar situation when i had loaded a new IOS and the router did not detect the ports.

I had to load the previous IOS through the console port using the xmodem feature.

Raj

 

[PanzerBoxb]

But how can I do the IOS install via xmodem if I cannot get the router to respond to any input and thus cannot reach a working rommon prompt?

 

[tiremd]

Can't get [control][break] to work during boot...very odd. I'm using HPterm 6.3 and work with 1720's on occasion and have had no problems. Do you have another cisco router to try to assure that HPterm is working properly and you can communicate with that router? That would be the first thing I'd try.

If so, and hpterm is working properly, your approach to remove the wic is a good start. Looks like your router has 16D, so there is nothing installed in the DRAM slot (16 built in). If you don't have another piece of flash to try, then it looks like you are out of luck. Sounds then like a defective router...

 

[trevorh13]

I had the same with two 2501's from Cisco. The system would not even respond to a boot rom mode either it would simply hang after you had done the ctrl break. I tried reloading The IOS using the cisco upgrade tool on the IOS feature pack CD and it would allow me to restore the IOS however this did not solve the problem. Ultimately the two devices were returned to Cisco and replacements issued.

 

[trevorh13]

I had the same with two 2501's from Cisco. The system would not even respond to a boot rom mode either it would simply hang after you had done the ctrl break. I tried reloading The IOS using the cisco upgrade tool on the IOS feature pack CD and it would allow me to restore the IOS however this did not solve the problem. Ultimately the two devices were returned to Cisco and replacements issued.

One other thought - you do have enough DRAM to run the IOS don't you?

 

[PanzerBoxb]

Problem found. Believe it or not it was the console cable. It was pulled from a working 2600, where it worked fine, for use on the 1720. After much headbanging I grabbed another console cable (not a planned solution) and it friggin worked. Sad thing is the first cable still appears to work on the 2600. Damn gremlins!