Redundant Sup720 Error Message After IOS Upgrade

[john.pepper]

Hi,

I just upgraded the IOS on dual Sup720's in a 6509 chassis. I FTP'd the new IOS on both fine, updated the Boot system to load the new IOS. Reloaded switch and all seemed to work ok.

However, every time I do a wr mem I get the following error message:

%PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slave is not present in standby

22:57:01: %PFINIT-SP-5-CONFIG_SYNC: Sync'ing the startup configuration to the standby Router. [OK]

I've checked both Sup's and their consistent with the IOS installed on both of them. Also, the 'show bootvar' indicates all looks ok as well:

CORE-SWITCH-01#show bootvar

BOOT variable = sup-bootdisk:s72033-adventerprisek9_wan-vz.122-18.SXF7.bin,1;sup-bootdisk:s72033-ipservices_wan-mz.122-18.SXF9.bin,1;,1;

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby is up

Standby has 524288K/32768K bytes of memory.

Standby BOOT variable = sup-bootdisk:s72033-adventerprisek9_wan-vz.122-18.SXF7.bin,1;sup-bootdisk:s72033-ipservices_wan-mz.122-18.SXF9.bin,1;,1;

Standby CONFIG_FILE variable =

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

Had a quick look on CCO and couldn't find anything relevant.

Has anyone come across this error and have a solution.?

Many thanks

John

[john.pepper]

I managed to resolve this problem by opening a TAC case. The problem relates to CSCef44077 as follows:

When syncing the configuration of redundant sup720s, you may get the following error message if the statement "boot system flash" is in the configuration and does not specify a file:

%PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slave is not present in st andby

Workaround: Delete "boot system flash" from the configuration or specify a filename

This is a cosmetic issue due to the boot system commands in the configuration which do not specify an image name.

Hope this helps.

Thanks

John

[sivaprakasam81]

Hi

How can i do, slave boot image configuration?

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 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