From: Sean C (Upp_and_Upp@xxxxxxxxxxx)
Date: Tue Mar 05 2002 - 15:22:53 GMT-3
Every so often we'll get in a 2501 router that'll not respond to teraterm,
CRT, hyperterm, etc. When we disable RTS/CTS - then we can get into the
router. Don't know the reason, my co-worker said he found some link on CCO
about it.
Sean
----- Original Message -----
From: <steven.j.nelson@bt.com>
To: <dmadlan@qwest.com>; <Craig.Columbus@columbusconsulting.com>
Cc: <cisco@groupstudy.com>; <ccielab@groupstudy.com>
Sent: Tuesday, March 05, 2002 12:36 PM
Subject: RE: Stupid 2500 confreg question
> Try setting the flow control in Hyperterm to None, that should do the
trick.
>
> Steve
>
> -----Original Message-----
> From: MADMAN [mailto:dmadlan@qwest.com]
> Sent: 05 March 2002 16:46
> To: Craig Columbus
> Cc: cisco@groupstudy.com; ccielab@groupstudy.com
> Subject: Re: Stupid 2500 confreg question
>
>
> Yes, a few times. Way back I hd that problem with hypeterm, switched
> to terterm and things worked better. I know have a couple of 2500's in
> the lab that I cannot talk to via the console but that otherwise work
> fine, I think they're just old and tired and I don't feeled inclined to
> spend much time trying to figure out why though you may want to stick a
> breakout box on the console and check the output.
>
> Dave
>
> Craig Columbus wrote:
> >
> > Has anyone run into an issue where a 2500 series router won't respond to
> > console input?
> > Here's the deal:
> > The PC is running 9600-8-N-1 and is connected to the 2500 console port.
> > The router has had nvram erased and is being booted for the first time.
> > Upon boot, the normal boot process is seen on the monitor screen.
> > When prompted to enter configuration dialogue, it's not possible to
input
> > anything on the router. Typing does nothing and there is no response
from
> > the router.
> > If Ctrl-F6-Break is pressed during boot, the router goes to the >
prompt,
> > but after that, the router still won't accept any input from the console
> port.
> >
> > Has anyone experienced this issue? Is this a config register problem?
If
> > so, is there a fix other than experimenting with different settings on
the
> > PC side? If not, does anyone have an answer? Could it be bad boot ROM?
> >
> > Thanks,
> > Craig
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:53 GMT-3