what does mean by Invalid boot string,

[sivaprakasam81]

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

[sivaprakasam81]

Thank you Jon for all your help,

Now i get boot string on the slave is invalid

6513-01#show diagnostic sanity

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.

How i can change the Slave boot image configuration?

[Jon Marshall]

Savi

Do you have 2 supervisors in your chassis ?

If so what method are you using to sync between the 2 supervisors ?

Jon

[sivaprakasam81]

Hi Jon,

Yes, we have two sup720 and we use SSO for redudancy sync.,

[Jon Marshall]

Well with SSO it should automatically copy the configuration. Are you sure you have a copy of the IOS in the sup-bootflash on the standby supervisor ?

Jon

[sivaprakasam81]

Yes, i do, How can i check on that?

Let me input you few outputs

6513-01#show slavesup-bootflash:

-#- ED ----type---- --crc--- -seek-- nlen -length- ---------date/time--------- name

1 .. image 78D92427 2957E84 39 42827268 Jan 14 2008 17:02:55 -05:00 s72033-ipservicesk9-mz.122-18.SXF11.bin

=============================

6513-01#show boot

BOOT variable = sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin,1;

CONFIG_FILE variable does not exist

BOOTLDR variable =

Configuration register is 0x2102

Standby is up

Standby has 458720K/65536K bytes of memory.

Standby BOOT variable = sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin,1;

Standby CONFIG_FILE variable does not exist

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

Do you get few details from this?

[Jon Marshall]

Siva

Easiest thing may be to login to the stanby sup and do the same change as you did on the active sup.

Jon

[sivaprakasam81]

Well Jon,

Do i need to force switchover to standby and do the necessary changes?

or other way to login and configure stanby sup720?

[Jon Marshall]

Siva

Do you have physical access ie. you can just connect into the console port on the standby supervisor.

Jon

[sivaprakasam81]

Sorry, No, i don't have physical access to the Switch. I can only ssh(remotely) to the 6500 Switch.

[Jon Marshall]

Siva

Sorry, it's been a while since i have had to do this and i can't remember if there is a command to access the standby sup.

If nobody else jumps in i will have a look at the upgrade docs tomorrow.

Jon

[sivaprakasam81]

Thank you for all your time and effort Jon!

Will see you tomorrow. Thanks again!!

[sivaprakasam81]

Hi Jon,

Do you have any update for me, how can i do boot image configuration for slave.

Thank you.

[Jon Marshall]

Siva

It should automatically update when you changed it on the active supervisor. Only thing i can suggest is

1) remove boot string altogether from active sup

2) Save you config and then see if the slave sup is still reporting the error.

3) Reenter boot string on active supervisor and see if that propogates to the slave.

If not you could as you say force the switchover and update the slave that way.

Jon

[sivaprakasam81]

Hi Jon,

I tired with Doing Forced Switchover and also removed and realod, still get the same error, invalid boot image string for slave. Follows the configuration and output,

6513-01(config)#do show run | inc boot

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

6513-01(config)#$ash:s72033-ipservicesk9-mz.122-18.SXF11.bin

6513-01(config)#do show run | in boot

6513-01(config)#do write

Building configuration...

[OK]

6513-01(config)#do show run | inc boot

01(config)#boot system flash sup-boot

6513-01(config)#boot system flash sup-bootflash:s72033-ipservicesk9-mz.122-18.SXF11.bin

6513-01(config)#do write

Building configuration...

[OK]

6513-01(config)#do show run | inc boot

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

6513-01(config)#do 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/1 ms

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.

Thank you.

[sivaprakasam81]

Hi Jon,

(ref with previous post, remove and reload the boot string command****)

Will this help you?

6513-01#show run | begin sso

mode sso

main-cpu

auto-sync running-config

spanning-tree mode pvst

spanning-tree extend system-id

Thank you,