CatOS to IOS Conversion

Unanswered Question
May 9th, 2007

A 6500 has been upgraded from CatOS to IOS. And image was installed on bootflash (not in slot0). All upgrade procedures were followed and image was re-installed on sup-bootflash.

Here is the BOOT variable after upgrade:

Router#remote command switch show bootvar

BOOT variable = bootflash:c6sup22-jsv-mz.121-26.E8.bin,1

CONFIG_FILE variable =

BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-11b.E4.bin

Configuration register is 0x0 (will be 0x2102 at next reload)

Should "BOOT varialbe = sup-bootflash:c6sup22-xxx.xxx" format instead of "BOOT variable = bootflash:c3sup22-xxx.xxx".

Dir show no c6sup22-xxx.xxx on bootflash but has c6msfc2-xxx.xxx and other.

PS. switch was rebooted a couple times and everything looks fine.

Thanks,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
ankbhasi Wed, 05/09/2007 - 07:08

Hi Friend,

You issued a command "remote command switch show bootvar" which is displaying you the boot variable set on supervisor. When you are into native ios mode image is stored on bootflash on supervisor engine which is referred to as sup-bootflash from MSFC point of viw. For msfc it is bootflash on sup and that s the reaon we say sup-bootflash but for sup bootflash is local so it is only mentioned as bootflash.

So everything looks fine and good and no issues in your boot variable.

HTH

Ankur

*Pls rate all helpfull post

Amit Singh Wed, 05/09/2007 - 10:12

Everything seems to be fine. You have the correct bootpath set. Just one thing to share that MSFC2 doesnot require a bootloader file and I see that you have a bootloader fine lying in the Sup's bootflash. You can go ahead and remove it from the sup's bootflash as it will occupying extra spce. If you want to keep this file, it has to be on MSFC's bootflash.

-amit singh

Actions

This Discussion