On the 2600 series the console port can go up to 115200. I've done this
from rommon several times when I had to load an IOS using xmodem...which
really sucks. I believe the 3600 series can also go to 115k but I'm not
positive. I don't know of any other Cisco routers that support that console
speed.
| You bad boys and girls should read and save my posts. Lots of good
| information.
|
| http://home.nc.rr.com/quiggle/ConfigReg.xls
| courtesy of Adam Quiggle
|
| the console port speed is determined by the values of two bit positions
in
| the config register. Convert from hex to binary. Bits 11 and 12 from the
| right ( start at 0, as all good computer folk do )
|
| a bug of one sort or another in the IOS? So far as I know, console speeds
| greater than 9600 are not supported.
|
| Chuck
|
| -----Original Message-----
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
John
| Neiberger
| Sent: Wednesday, June 20, 2001 8:21 AM
| To: [EMAIL PROTECTED]
| Subject: RE: Config Register Weirdness, again... [7:9181]
|
| Alright, I figured it out! The guy who configured this router (and the
last
| one that was acting strangely) set the line speed on the console port to
| 115200 by adding 'speed 115200' in the config. After playing around a
bit
| I've noticed that speed changes to the console port automatically adjust
the
| configuration register, but not always in expected ways.
|
| In this case, the config register was changed to 0x3922 which sets the
speed
| to 2400. Changing the speed to 38400 sets the config register to 0x2922
| which will set the port speed to 4800 upon reboot. Weird, huh? I don't
get
| the correlation.
|
| Why does 115200 = 2400 upon reboot? And 38400 = 4800? Hmm....
something's
| fishy, but at least that explains the weirdness I've noticed lately.
|
| Moral of the story: beware of changing the line speed on your console
| port! It may cause behavior you don't expect!
|
| And I still haven't figured out why the register was set to 0x4000 in the
| beginning.
|
| Oh well, back to work...
|
| John
|
| John Neiberger wrote:
| >
| > 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
|
|
|
|
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9301&t=9181
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
