----- Original Message -----
From: John Neiberger
To:
Sent: Wednesday, June 20, 2001 7:46 AM
Subject: Config Register Weirdness, again... [7:9181]
> Okay, what's the deal here? Look at this output:
>
> Configuration register is 0x2102 (will be 0x4000 at next reload)
>
> RARAP#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> RARAP(config)#config-reg 0x2102
> RARAP(config)#end
> RARAP#sho ver
> Cisco Internetwork Operating System Software
>
> [lotsa trimming]
>
> Configuration register is 0x2102 (will be 0x3922 at next reload)
>
> Why is the config register going to reload at 0x3922?? I just set the
> darn thing to 0x2102 and you can see that change occurred. I was trying
> to get rid of the 'will be 0x4000 at next reload'. I have no idea why
> that was there to begin with but it should not be there. Is this
> something that I'll have to fix from the console port? I can't reload
> the router because it was put into production this morning. Why is it
> set to 0x3922?
>
> I'm guessing that the guy who installed this was playing around with
> the confreg utility in rommon and we'll have to go back to rommon to fix
> it.
>
> Any ideas?
GREMLINS, or 2102 instead of 0x2102, or it's broken
go in and config it *again* for config-reg 0x2102 and see if sh ver gives
you yet another value 'at next reload' - maybe the config-reg statement on
*your* router is really a random-number generator...
:-)
-e-
>
> Thanks,
> John
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9227&t=9181
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
