Cisco 6500 with SUP 720 - Invalid boot Image

[kcgeorge]

Diagnostic sanity check on the 6500 reports Invalid boot image "bootdisk:<output omitted>

The boot statement on the 6500 is :-

boot system bootdisk:<filename.bin> and the 6500 boots fine.

Please advise.

Thank You.

[smothuku]

hi ,

check the below link..it may be helpful.

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/ol_5631.htm

Thanks,

satish

[Georg Pauwen]

Hello,

can you post the output of ?show system sanity?? Also, which IOS or CatOS (or both) version(s) are you running on your 6500 ?

Regards,

GP

[kcgeorge]

It's running IOS 12.2(18)SXF4.

show sup-bootdisk shows the code listed but show diagnostic sanity lists it as an invalid code.

Not sure if it's a bug issue or something else.

[smothuku]

Hi ,

I have found bug which is internally found by cisco.The bug is CSCsc98471 and following are details of bug .

The command "show diagnostic sanity" checks amongst other things, if the current bootstring is matching pointing to an existing file.

Since ION bootstring format has been extended (assuming an installed image) this check fails although the bootstring is correct.

Can be easily reproduced by entering the "show diagnostic sanity" command.

6500-6#show diagnostic sanity

Pinging default gateway 172.26.197.33

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.26.197.33, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Could not verify boot image "sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm," specified in the boot string.

...

6500-6#show bootvar

BOOT variable = sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm,12;

6500-6#dir sup-bootflash:/newsys/s72033/base/

Directory of sup-bootdisk:/newsys/s72033/base/

84 -rwx 1375696 Jan 5 2006 20:51:24 -08:00 imf.tar

85 -rwx 12873200 Jan 5 2006 20:51:22 -08:00 s72033-adventerprisek9_wan_dbg-vm

It is found in 12.2(18.09.20)SX3.39.

*** open a TAC case so that the same bug is fixed in 12.2(18)SXF4.

Hope it helps you.Plz rate it.

Thanks,

satish

[kcgeorge]

I checked the SP ROMMON version on the SUP 720 & it has the correct release, 8.4(2)

Let me see if works if I change the boot sequence to sup-bootdisk rather than bootdisk

Thx for the all help