From: Luan Nguyen (lm_nguyen@xxxxxxxxxxx)
Date: Sat Jul 24 1999 - 22:22:40 GMT-3
What would you do if you cannot enter the router? aren't this childplay?
who would do such a thing ? :) on the production routers that is...this is
unpractical...shouldn't even have to troubleshoot this one. I've never
encounter this problem in real life before. Let me know if anyone has. If
I do, guess what? I'll send that sucker back for a different one :) rather
than trying changing the baud rate.
Has anyone encounter unable to enter enable mode? from console that is.
how to trouble shoot such a thing? And I don't mean you forgot your
password. For example if someone telnet into the router put line con 0 in
no exec, then that person change all the ip addresses on the interfaces.
on the last one he will be kick out but can telnet in again with the new ip
and write mem what can you do to get in without having to reconfigure the
whole router?
Regards,
LMN
>From: "Poston, Barry" <BPoston@Aegonusa.com>
>Reply-To: "Poston, Barry" <BPoston@Aegonusa.com>
>To: "'Eddie M. Parra'" <eparra@rexallsundown.com>, ccielab@groupstudy.com
>Subject: RE: CCIE #4932
>Date: Sat, 24 Jul 1999 12:24:39 -0500
>
>I would agree with Scott's comments concerning troubleshooting. If you
>built it, you should know what possible issues could cause your network to
>not function correctly. It's sort of a reversal of the process you went
>through when you built it. Suppose that when you were creating your
>network, one of your interfaces was in an up/down state. What would you
>have done to correct that? Well, if you enter the troubleshooting stage,
>and see that one of your interfaces is up/down, then you should know what
>could cause that, and how to resolve it.
>
>To prepare for troubleshooting, try to imagine all possible things that
>could go wrong. What would you do if you cannot access a router? What
>would you do if you are unable to enter enable mode? What would you do if
>a
>router is not communicating properly with a neighbor? Review your configs
>to see if there are missing statements that you had configured previously,
>or if there are additional statements that you did not enter. Try to be
>logical with your troubleshooting. Know what your network should do,
>determine if it is doing all that, find the places where it is not, look
>for
>possible causes of that symptom, and apply resolutions to those causes.
>
>Barry Poston, CCIE #4932
>
> > -----Original Message-----
> > From: Scott Morris [SMTP:SMorris@tele-tech.com]
> > Sent: Saturday, July 24, 1999 12:37 AM
> > To: 'Eddie M. Parra'; Derek Fage; 'Poston, Barry';
> > ccielab@groupstudy.com
> > Cc: fningham@worldnet.att.net
> > Subject: RE: CCIE #4932
> >
> > Troubleshooting is troubleshooting. Anything you've designed/built can
>be
> > broken. Need I say more?
> >
> > As for recovery of CAT password, it couldn't be any simpler. When you
> > power
> > the sucker on, the first ... ummm... 30 (I think) seconds of booting
>are
> > sans password, which means you hit enter as quick as you can, and
> > "enable",
> > enter for blank password and change the thing before it continues to
>load
> > the image. Cool, huh? :)
> >
> > Scott Morris, MCSE, CNE (3.x), CCDP, CCIE #4713
> > smorris@tele-tech.com
> >
> >
> > -----Original Message-----
> > From: Eddie M. Parra [mailto:eparra@rexallsundown.com]
> > Sent: Friday, July 23, 1999 11:21 PM
> > To: Derek Fage; 'Poston, Barry'; ccielab@groupstudy.com
> > Cc: fningham@worldnet.att.net
> > Subject: RE: CCIE #4932
> >
> >
> > What types of scenarios are on the troubleshooting part? Has anyone had
> > to
> > perform password recovery on a Cat? Can someone elaborate on the
> > troubleshooting part?
> >
> > -Eddie Parra
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:43 GMT-3