Has anyone seen the following issue on their 6500 switches with the Boot variable differing from the startup or running config?
SWITCH1#sh bootvar | inc BOOT variable
BOOT variable = sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH3.bin,12;sup-bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12;
SWITCH1#sh run | inc boot system
boot system sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH3a.bin
boot system sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH4.bin
SWITCH1#sh start | inc boot system
boot system sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH3a.bin
boot system sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH4.bin
SWITCH1#wr mem
Building configuration...
[OK]
SWITCH1#sh bootvar | inc BOOT variable
BOOT variable = sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH3a.bin,12;sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH4.bin,12;
Then after a reload it goes back to showing:
SWITCH1#sh bootvar | inc BOOT variable
BOOT variable = sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXH3.bin,12;sup-bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12;
It doesn't affect the operation of the switch, it boots the file called by 'boot system' whether it is reloaded by the CLI or power cycled.
