From: Barney Gaumer (bagaumer@yahoo.com)
Date: Thu Aug 07 2003 - 14:04:16 GMT-3
Usage Guidelines
Not all platforms support the o command.
To get to the ROM monitor prompt, use the reload EXEC
command if the configuration register has a boot value
of 0. (For systems with a software configuration
register, a value can be included on the o/r command
line.) Use the i command in conjunction with the o/r
command to initialize the router. (The i command is
documented in the hardware installation and
maintenance publication for your product.) The o/r
command resets the configuration register to 0x141,
which disables the Break key, ignores the NVRAM
configuration, and boots the default system image from
ROM.
Examples
The following is a sample display from the o command:
> o
Bit# Configuration register option settings:
15 Diagnostic mode disabled
14 IP broadcasts do not have network numbers
13 Do not boot default ROM software if network
boot fails
12-11 Console speed is 9600 baud
10 IP broadcasts with ones
09 Do not use secondary bootstrap
08 Break enabled
07 OEM disabled
06 Ignore configuration disabled
03-00 Boot to ROM monitor
>
The following is an example of the o/r and i commands
used to reset and boot the default system image from
ROM:
Hope this helps!
Cheers,
Barney
--- Yuki Hisano <yukyhisano@hotmail.com> wrote:
> Matijevic,
>
> I beleive it will solve the issue.
> I just wanna know why and whats wrong with 0x102
>
> Thanks!
>
> Yuki
> ----- Original Message -----
> From: "John Matijevic" <matijevi@bellsouth.net>
> To: "Yuki Hisano" <yukyhisano@hotmail.com>; "Jim
> Dixon"
> <JDixon@communigroup.com>; <ccielab@groupstudy.com>
> Sent: Thursday, August 07, 2003 11:24 AM
> Subject: Re: Break-key & _continue_
>
>
> Hello Yuki,
> The reason you cant login, is because its not a
> public document, there are
> some sections on Cisco's website thats only
> accessable if you are a cisco
> reseller. I am very confident that the suggestion I
> gave you will solve your
> issue.
> Sincerely,
> Matijevic
> ----- Original Message -----
> From: "Yuki Hisano" <yukyhisano@hotmail.com>
> To: "Jim Dixon" <JDixon@communigroup.com>; "John
> Matijevic"
> <matijevi@bellsouth.net>; <ccielab@groupstudy.com>
> Sent: Thursday, August 07, 2003 11:19 AM
> Subject: Re: Break-key & _continue_
>
>
> > I cant log in the link below.
> >
> > ??
> >
> > Yuki
> >
> > ----- Original Message -----
> > From: "Jim Dixon" <JDixon@communigroup.com>
> > To: "'Yuki Hisano'" <yukyhisano@hotmail.com>;
> "John Matijevic"
> > <matijevi@bellsouth.net>; <ccielab@groupstudy.com>
> > Sent: Thursday, August 07, 2003 11:03 AM
> > Subject: RE: Break-key & _continue_
> >
> >
> >
>
http://www.cisco.com/en/US/customer/products/hw/switches/ps708/prod_release_
> > note09186a008015c76a.html
> > 0x2102 should be correct for autoboot
> > per the excerpt below from the link above.
> > Upgrading a Nonredundant Configuration
> >
> >
>
--------------------------------------------------------------------------
> --
> > ----
> > Step 1 As a precaution, save the system
> configuration.
> >
> > Step 2 Copy the Cisco IOS system software image
> (for example,
> > c6sup12-jsv-mz.121-8b.EX5 or later) to either
> sup-bootflash or slot0.
> >
> > Step 3 Remove the old boot commands:
> >
> > Router(config)# no boot system flash
> slot0:old_image_name
> > or:
> >
> > Router(config)# no boot system flash
> sup-bootflash:old_image_name
> > Step 4 Configure the switch to autoboot the new
> image:
> >
> >
> >
>
--------------------------------------------------------------------------
> --
> > ----
> > Note To avoid boot failure, include the device
> name (slot0 or
> > sup-bootflash) in the following commands.
> >
> >
>
--------------------------------------------------------------------------
> --
> > ----
> >
> > Router(config)# boot system flash
> slot0:c6sup12-jsv-mz.121-8b.EX5
> > or:
> >
> > Router(config)# boot system flash
> sup-bootflash:c6sup12-jsv-mz.121-8b.EX5
> > Step 5 Set the configuration register parameter
> to autoboot:
> >
> > Router(config)# config-register 0x2102
> > Step 6 Copy the running configuration to the
> startup configuration in
> > NVRAM:
> >
> > Router# write memory
> > Step 7 Reload the switch:
> >
> > Router# reload
> >
> > -----Original Message-----
> > From: Yuki Hisano [mailto:yukyhisano@hotmail.com]
> > Sent: Thursday, August 07, 2003 09:54
> > To: John Matijevic; ccielab@groupstudy.com
> > Subject: Re: Break-key & _continue_
> >
> >
> > John, Joe,
> >
> > It is 0x102.
> > Is this OK?
> >
> > Thanks!
> >
> > Yuki
> > ----- Original Message -----
> > From: "John Matijevic" <matijevi@bellsouth.net>
> > To: "Yuki Hisano" <yukyhisano@hotmail.com>;
> <ccielab@groupstudy.com>
> > Sent: Wednesday, August 06, 2003 6:05 PM
> > Subject: Re: Break-key & _continue_
> >
> >
> > Yuki,
> > I had a similar experience take a look at your
> config register and make
> sure
> > that its set to 2102.
> > You can do a sh ver, also if you need to you may
> need to change using the
> > config command.
> > Sincerely,
> > Matijevic
> > ----- Original Message -----
> > From: "Yuki Hisano" <yukyhisano@hotmail.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Wednesday, August 06, 2003 5:11 PM
> > Subject: Break-key & _continue_
> >
> >
> > > Hi,
> > >
> > > I have a 7603 router that is acting funny.
> > > A while ago, someone rebooted the router
> remotely. It started to restart
> > > over and over till the command "continue" was
> entered after the break
> key.
> > > It just happened again when we try to upgrade
> the code and memory.
> > > This time, the procedure did not help and had to
> put everything in the
> way
> > > it wasand enered
> > > "cotinue".
> > >
> > > I am worried that if this happens again.
> > >
> > > Anyone has any solution to this?
> > >
> > > Thanks!
> > >
> > > Yuki
> > >
> > >
> > >
>
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:55 GMT-3