Re: what does mean by Invalid boot string, - Page 3

sivaprakasam81 · ‎03-12-2009

Hi All,

What does mean by invalid boot string, how can i set the correct boot string.

6513-01#show diagnostic sanity

Pinging default gateway 192.168.30.1

Type escape sequence to abort.

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

!!!!!

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

Invalid boot image "sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin," specified in the boot string.

Please check your boot string.

None of the images specified in the boot string are valid.

Please specify at least one valid image in the boot string to ensure the

switch is in a bootable state.

Invalid boot image "sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin," specified in the boot string on the slave.

Please check your boot string on the slave.

None of the images specified in the boot string on the slave are valid.

Please specify at least one valid image in the slave boot string to ensure the

slave is in a bootable state.

UDLD has been disabled globally - port-level UDLD sanity checks are being

bypassed.

Thank you,

Siva

Jon Marshall · ‎03-13-2009

When you switched over to the standby what was the boot string in the running-config showing ?

You need to change it to match what you have put on your active supervisor.

Jon

sivaprakasam81 · ‎03-13-2009

How can i access the stanby one? i did redundancy force-switchover. The active becomes standby and vice-versa. The boot string remain says, that the boot image string is good for (present) active. The invalid boot image for the (present) Stanby. It doesnot matter, which sup720 it is.

By default, it shows the right one in the boot string.

6513-01#show run | inc boot

boot system flash sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin

Thank you Jon!

Jon Marshall · ‎03-13-2009

"By default, it shows the right one in the boot string"

Then maybe it's just a cosmetic warning message you because if you can reload both Supervisors it looks like it using the correct boot variable.

I don't have access to any 6500 switches so i can't really helpo you much more. If you can reload both supervisors independtly and they both come up ie. neither gets stuck in ROMMON then you should be okay.

Jon

sivaprakasam81 · ‎03-13-2009

Hi Jon,

How can i reload both the sup720, will that affect the running Switch?.

I do see some configuration guidelines for sup but not clear.

What is the boot string, do i need use for slave with reference to the following link :

http://www.cisco.com/en/US/docs/ios/11_3/configfun/configuration/guide/fcreboot.html#wp20212

sivaprakasam81 · ‎03-13-2009

Step 6 : Also, add a boot system command that specifies the slave's boot image and location. This is the boot image that the slave uses when it becomes the master RSP and boots the system. Note that the because the slave will boot this image when the slave is actually the new master RSP, the command syntax does not use a "slave" prefix.

boot system flash bootflash:[filename]

boot system flash slot0:[filename]

boot system flash slot1:[filename]

Do i use,

boot system flash sup-bootflash:filename

or

boot system flash slavesup-bootflash:filename

or boot system flash slavebootflash:filename

Thank you Jon!

sivaprakasam81 · ‎03-13-2009

I tried with all, still getting the same.

6513-01(config)#do show diagnostic sanity