I have just experienced this yesterday. Thanks for the heads-up.
I am a little irked that the speed on the console interface has anything to
do
with the value shown for the config register.
Has cisco got an answer for this????????? If not seems a fix is necessary.
Jim
>>> "Chuck Larrieu" 21/06/01 10:40:01 >>>
This message has been scanned by MAILSweeper.
************************************************************
A well known trick of evil lab proctors making for fewer CCIE's in this
world :->
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Priscilla Oppenheimer
Sent: Wednesday, June 20, 2001 11:01 AM
To: [EMAIL PROTECTED]
Subject: RE: Config Register Weirdness, again... [7:9181]
A well-known trick of evil students making trouble for the Cisco networking
instructor. ;-)
Priscilla
At 01:25 PM 6/20/01, John Neiberger wrote:
>This was happening on a 2621 running 12.1(5)T5 but I saw something
>similar happen on a 2650 running 12.2(2)T. I discovered that the cause
>of the behavior was a speed change on the console port in the config.
>Somehow this was changing the config register settings and those changes
>didn't always make much sense. I changed the speed back to 9600 and the
>config register was set back to 0x2102.
>
>John
>
> >>> "Kane, Christopher A." 6/20/01 10:58:11
>AM >>>
>I haven't seen that before. What series of router is it? Could it be a
>jumper setting?
>
>
>
>-----Original Message-----
>From: John Neiberger [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, June 20, 2001 10:47 AM
>To: [EMAIL PROTECTED]
>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?
>
>Thanks,
>John
________________________
Priscilla Oppenheimer
http://www.priscilla.com
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9285&t=9181
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
