[c-nsp] 6500/7600 boot issues

Church, Charles cchurch at multimax.com
Thu Jun 7 16:11:41 EDT 2007


Do you have a boot system command in the running config?  If you put one
in and 'wri mem', that should get pushed down to the SP as well:


boot system flash disk0:s222-advipservicesk9_wan-mz.122-18.SXF6.bin

Router#rem com sw sh boot

BOOT variable = disk0:s222-advipservicesk9_wan-mz.122-18.SXF6.bin,1;

Without a boot variable, I think the SP will try to boot the first image
it finds.  Now whether it's from Disk0, bootflash:, etc is a question
I'm not sure about.  We always explicitly put ours in.

Chuck 

-----Original Message-----
From: Jon Lewis [mailto:jlewis at lewis.org] 
Sent: Thursday, June 07, 2007 4:05 PM
To: Church, Charles
Cc: cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] 6500/7600 boot issues

On Thu, 7 Jun 2007, Church, Charles wrote:

> Do a 'conf-reg 0x2102' from the normal CLI.  Then do a 'wri mem'.  The
> wri mem should push the config register setting down to the switch
side.
> The remote command method you listed won't work, since it's a one-line
> command only.  Do a 'show boot' and 'rem comm sw sh boot' when done to
> verify.

Another oddity in rem com sw sh boot:

#rem com sw sh boot

BOOT variable does not exist
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2142 (will be 0x2102 at next reload)

On all our others, the BOOT variable reflects the list of IOS's for
which 
we have boot system statements in the config.  Is the BOOT variable
empty 
because the confreg was 0x2142 (ignore config) at bootup, and next time
we 
boot, assuming the 0x2102 sticks, the BOOT variable will show up
properly 
populated?

----------------------------------------------------------------------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________


More information about the cisco-nsp mailing list