Shawn,
There one other "gotcha" where the "break enabled" bit 8 of the
config-register can bite you. You are correct that having break enabled
and having a console device connected could be dangerous because someone
could inadvertently send a break sequence and drop the router into
Rommon. Be aware that NOT having a console device connected could be even
more dangerous. In a significant number of instances where bit 8 was left
"off" in a router, (0x2002) I have seen the router drop into Rommon when
a console device was connected to the console interface! It turns out
that a "break sequence" can be very closely approximated by the "noise"
generated in plugging or unplugging the console cable! There was even one
report of an extended console cable in a large "NOC" that was plugged
into a console and laying on the floor that was ultimately linked to a
Core router intermittently dropping into Rommon. All I can report for
certain is that once this cable was removed from the console connection
on the router, the problem disappeared.
There are a very limited set of circumstances where having the "break
enabled" is a viable configuration on a Cisco router used for production.
:-( I actually had one person tell me that he left the break enabled so
that he could regain control in the eventuality that his routers went
berserk. I tried to point out that if he was close enough to be connected
to the console in that scenario, he could probably manage to flip the
power switch instead. :-P
I'm not certain the message got through,,,,,,,,,,, :-D
Bruce
Shawn Heisey wrote:
Mark,
Actually, the 'break disabled' is the default setting. It means that
after rommon passes control to the IOS, you can't issue a break to get
back to rommon. You can always issue the break before control is passed
to IOS, regardless of this setting.
If you turn this setting off, you can send a break at any time to get to
rommon -- even after the router is up and running. This can be a Very
Bad Thing (tm), especially if you leave something connected to the
console port all the time.
Thanks,
Shawn
"Mark W. Odette II" wrote:
Set your terminal app's baud rate to 19200 and see if that doesn't fix
ya.
Also, according to the nifty Config-Register calculator (from Boson's
website), the Break Key is disabled. So, you'll need to let the router
boot normally, and then, via the console, go into config mode and change
the config register to your desired setting.
HTH's
Mark
-----Original Message-----
From: Frank Lodato [ mailto:[EMAIL PROTECTED] ]
Sent: Tuesday, October 01, 2002 10:10 AM
To: [EMAIL PROTECTED] Subject: Config-register???? [7:54632]
I broke in to a Cisco 2600 router today, but I didn't have access to my
handy sheet that tells me exactly what config-register setting to type
in.
Instead of 0x2142 I put 0x2124. Now when I hard bott the router it
gives
me'JJJJJJJJJJJJJJJJJJJ^JJJJJJJJJJJJJJJJJJJJ^' .
Now, I've never seen this before so I'm very confused as to what to do
next. I can't really type anything either so it wont take commands that
I
know. What did I do? How can I fix it?
Help!
--
Bruce Enders Email: [EMAIL PROTECTED]
Chesapeake NetCraftsmen o:(410)-757-3050, c:(443)-994-0678
1290 Bay Dale Drive, Suite 312 WWW: http://www.netcraftsmen.net
Arnold, MD 21012-2325 Cisco CCSI# 96047
Efax 443-331-0651
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=54749&t=54632
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
