[c-nsp] 6500/7600 boot issues

[Jon Lewis]

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

> 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;

A bunch of them.

#sh run | inc boot
boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7b.bin
boot system flash disk1:s72033-pk9sv-mz.122-18.SXD7b.bin
boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7.bin
boot system flash disk0:s72033-advipservicesk9_wan-mz.122-18.SXF7.bin
boot system flash disk0:s72033-advipservicesk9_wan-mz.122-18.SXF4.bin
boot system flash sup-bootflash:s72033-pk9sv-mz.122-17d.SXB10.bin

#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)

This appears to be a bug!  Too many boot statements in the config cause 
the sup BOOT variable to cease to exist.  I found this be removing all but 
the first, wr me, rem com sw sh boot.  Then I started adding boot 
statements back, wr me, rem com sw sh boot until BOOT emptied.

#sh run | inc boot
boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7b.bin
boot system flash disk1:s72033-pk9sv-mz.122-18.SXD7b.bin
boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7.bin
#remote command switch sh boot

BOOT variable = 
disk0:s72033-pk9sv-mz.122-18.SXD7b.bin,1;disk1:s72033-pk9sv-mz.122-18.SXD7b.bin,1;disk0:s72033-pk9sv-mz.122-18.SXD7.bin,1
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2142 (will be 0x2102 at next reload)

#conf t
boot system flash disk0:s72033-advipservicesk9_wan-mz.122-18.SXF7.bin
exit
wr me
#remote command switch 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)

If I remove that last boot statement and wr me, the sup BOOT variable is 
populated again.

What's odd is another of our 6500's has the following boot statements in 
config:

boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7b.bin
boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7.bin
boot system flash disk0:s72033-advipservicesk9_wan-mz.122-18.SXF7.bin
boot system flash disk0:s72033-advipservicesk9_wan-mz.122-18.SXF4.bin
boot system flash sup-bootflash:s72033-ipservicesk9-mz.122-18.SXE1.bin

and it has no issue with the sup BOOT variable clearing.  Obviously, we 
don't really need all these boot statements.  I tend to leave several 
"fall backs" when doing upgrades/downgrades.

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