From: Adam Quiggle (aquiggle@xxxxxxxxx)
Date: Mon Jan 08 2001 - 05:11:40 GMT-3
Chuck,
I know it's a little late, but feel free to help yourself to
this configuration register setting thing that I received
and have since modified to suit my needs. It has all of the
corresponding values in the configuration register and what
they mean.
http://home.nc.rr.com/quiggle/ConfigReg.xls
There is a place to convert the configuration register to
binary, so that you can easily see the configuration. In
addition there is a place to enter the binary values you want
and it'll spit out the configuration register for you. :-)
Not that you can't find what you need on CCO, but sometimes its
just more convenient to have it on a laptop that can travel
with you. :-)
If anyone sees any errors, please let me know.
Thanks,
AQ
At 01:57 AM 1/8/01, Chuck Larrieu wrote:
>Well that wasn't nearly so bad as it could have been. The low life who
>trashed my router, not to mention spoiled it for a lot of folks on these
>lists, could have been more malicious. But he was deliberate. No doubt about
>it.
>
>So here is today's troubleshooting lesson - not really password recovery,
>but configuration register setting recovery. I have done a bit of password
>recovery practice, but not much.
>
>1) cannot get into rommon mode. Not that I can tell. Gibberish of various
>sorts on screen. Check to be sure my version of HyperTerminal sends the
>correct control-break sequence, using another router. it does. I was sure I
>had upgraded this particular version, but these days, when moving between so
>many different computers at home and on the job, one never can tell.
>
>2) Ok, with gibberish on the screen, what are some things to check? A quick
>look through CCO confirms that baud rate is the only terminal setting that
>can be changed in the register. Thank goodness one cannot also change the
>data, stop, and parity.
>
>3) OK. Brute force this thing. 9600 does not work. Let's work down the
>scale, and see..... 4800 does not work. 1200 did not work earlier this
>afternoon. But 2400 does work. I see clear text and I see I am in rommon
>after all.
>
>4) Check the current config register setting. E/s 2000002 [enter] reveals
>the setting as 0x3942 you bad boy!
>
>5) Use the o/r 0x2102 to reset the register and reload.
>
>6) Rommon again! Hhmmm.........
>
>7) OK, this time do a config mem ( I probably should have looked at this
>last time anyway, but I did not )
>
>8) Well, what did the yo-yo do here? Hostname rommon> interesting.
>Certainly explains the console message I was seeing last time I reloaded.
>Well, I don't have time to fool around any more. Erase start, reload, things
>come up ok. I will copy my saved configuration later.
>
>9) Too bad garbage-head inserted himself into this weekend. Someone was
>doing a very interesting IPSec tunnel between my pod and theirs. I was
>looking forward to seeing the result.
>
>10) End result - learned a few more things which will be valuable in the
>lab - troubleshooting portion.
>
>Extra credit - with a configuration register setting of 0x3942, what was
>happening at boot time?
>
>Chuck
>----------------------
>I am Locutus, a CCIE Lab Proctor. Xx_Brain_dumps_xX are futile. Your life as
>it has been is over ( if you hope to pass ) From this time forward, you will
>study US!
>( apologies to the folks at Star Trek TNG )
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:23 GMT-3