Yeah, it looks like I'll end up going in that direction.  After exhausting 
Cisco and google, I was hoping that someone on the list could give me a 
quick answer.
I'm still not sure that it's not a bad boot ROM.  The boot ROM was recently 
upgraded, and although I'm told that it worked fine after the upgrade, I'm 
beginning to have my doubts.

Thanks!
Craig

At 12:40 PM 3/5/2002 -0500, you wrote:
>like Dave suggested before, put a break out on it and go from there....you 
>may find that the serial port is expecting cts/rts and one of the pins are 
>severed.  I'm not sure what cisco requires to be 'live' on their 
>2500's....an extremely half-assed search on google didn't yield anythign 
>too interesting....but I'm sure you can find it out there...  :)
>
>-Patrick
>
> >>> "Craig Columbus"  03/05/02 
> 12:17PM >>>
>The cable is good and scroll lock isn't on.  Same PC setup and cable work
>fine on other 2500 series.  I haven't run into this particular issue before.
>
>Craig
>
>
>At 11:50 AM 3/5/2002 -0500, you wrote:
> >Have you tried a different cable?
> >
> >
> >----- Original Message -----
> >From: "Craig Columbus"
> >To:
> >Cc:
> >Sent: Tuesday, March 05, 2002 11:18 AM
> >Subject: Stupid 2500 confreg question
> >
> >
> > > 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
> > > _________________________________________________________________
> > > Commercial lab list: http://www.groupstudy.com/list/commercial.html
> > > Please discuss commercial lab solutions on this list.
> >_________________________________________________________________
> >Commercial lab list: http://www.groupstudy.com/list/commercial.html
> >Please discuss commercial lab solutions on this list.
> >>>>>>>>>>>>>  Confidentiality Disclaimer   This email and any files
transmitted with it may contain confidential and
>/or proprietary information in the possession of WellStar Health System, 
>Inc. ("WellStar") and is intended only for the individual or entity to 
>whom addressed.  This email may contain information that is held to be 
>privileged, confidential and exempt from disclosure under applicable law. 
>If the reader of this message is not the intended recipient, you are 
>hereby notified that any unauthorized access, dissemination, distribution 
>or copying of any information from this email is strictly prohibited, and 
>may subject you to criminal and/or civil liability. If you have received 
>this email in error, please notify the sender by reply email and then 
>delete this email and its attachments from your computer. Thank you.
>
>================================================================




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=37293&t=37287
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to