Router does not respond in console

I just got three used 2501 Cisco routers and am trying to connect to through the console. I had a RJ-45/DB9 cable hooked up, fired up Hyperterminal, and turned on the router. I see all the bootstrap messages but it does not respond to any of my keystrokes. I've tried each router thinking the first one may have just been defective, but they all do the same thing. My settings in Hyperterminal were 9600-8-n-1. I tried it with XON/XOFF, Hardware, and NO flow control but nothing worked. My current thought is that there is still some Hyperterminal setting I need to change or there is something wrong with my consle cable (but then why can I see the router output?). I'll paste the Bootstrap below. I hope someone can help.

Thanks.

------------------ System Bootstrap, Version 11.0(10c)XB1, PLATFORM SPECIFIC RELEASE SOFTWARE (fc1)

Copyright (c) 1986-1997 by cisco Systems

2500 processor with 16384 Kbytes of main memory

F3: 9286440+846656+770252 at 0x3000060

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706

Cisco Internetwork Operating System Software IOS (tm) 2500 Software (C2500-IO-L), Version 12.2(26), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Sat 31-Jul-04 03:32 by eaarmas Image text-base: 0x03050A44, data-base: 0x00001000

cisco 2500 (68030) processor (revision A) with 16384K/2048K bytes of memory. Processor board ID 01432873, with hardware revision 00000000 Bridging software. X.25 software, Version 3.0.0.

1 Ethernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read ONLY)

Press RETURN to get started!

00:00:07: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up 00:00:07: %LINK-3-UPDOWN: Interface Serial0, changed state to down 00:00:08: %LINK-3-UPDOWN: Interface Serial1, changed state to down 00:00:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed sta te to down 00:00:20: %SYS-5-CONFIG_I: Configured from memory by console 00:00:23: %LINK-5-CHANGED: Interface Serial0, changed state to administratively down 00:00:23: %LINK-5-CHANGED: Interface Serial1, changed state to administratively down 00:00:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down 00:00:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down 00:01:04: %SYS-5-RESTART: System restarted -- Cisco Internetwork Operating System Software IOS (tm) 2500 Software (C2500-IO-L), Version 12.2(26), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Sat 31-Jul-04 03:32 by eaarmas 00:01:04: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoing a cold star t
Reply to
Thread7
Loading thread data ...

One more note. I found this thread that seems to state that console ports get partially fried when hooking them up to an ISDN line and then I may get the problem I have now. Someone suggested using a NULL modem adapter or breakout box. I have neither at the moment and would like to get this working soon without having to acquire one of these things. So I just snipped PIN 1 on my console cable. Nothing changed. I can still see bootstrap but no response from the keyboard.

Thanks. Here is the link to that thread:

formatting link

Reply to
Thread7

Hook your console cable to the AUX port and try that and make sure the config-register is set to 0x2102.

Jonathan

Reply to
Jonathan

This was actually a very simple problem. My DB9 to RJ45 cable just had the wrong pinouts. When I built the cable from scratch everything worked fine.

Reply to
Thread7

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.