06-05-2008 07:00 AM - last edited on 03-25-2019 04:01 PM by ciscomoderator
Can someone tell me what I could be doing wrong here. I'm running 6500 with two sup720 in the sso mode, if upgraded the ios on the active sup and updated the boot system command with the thought that active sup will synch it with the standby sup but i got the following warining/error message when i saved config or when i reloaded the active sup.
00:02:53: %PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin is present on the active supervisor but not on the standby
Do I have to install the ios file on the standby sup individually? will it not synch with the standby sup?
Second I updated the boot system command
boot system flash sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin and my dir on sup-bootdisk show this
Router#dir sup-bootdisk:
Directory of sup-bootdisk:/
1 -rw- 74328548 Jan 25 2008 16:12:16 +00:00 s72033-ipservicesk9_wan-mz.122-33.SXH.bin
2 -rw- 33554432 Jan 25 2008 02:27:40 +00:00 sea_log.dat
3 -rw- 80075300 Jun 5 2008 14:13:48 +00:00 s72033-adventerprisek9_wan-mz.122
06-05-2008 07:07 AM
Hi Nawas,
Both the sups boot from their respective bootflash.
Thus, you should copy the image first to the standby bootflash .
Ex:
copy disk0: slavedisk0:
HTH
Raj
06-05-2008 07:39 AM
I loaded the code in the slavedisk0: and reloaded the router but it still is boots up with the old code, i have boot system command enable and my config-register valus is 0x2102.
06-05-2008 09:24 AM
Pls update with :
dir disk0:
dir slavedisk0:
sh boot
06-05-2008 11:53 AM
sh boot
BOOT variable = sup-bootdisk:,1;bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby is up
Standby has 1048576K/65536K bytes of memory.
Standby BOOT variable = sup-bootdisk:,1;bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin,1;
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
Router#dir sup-bootdisk:
Directory of sup-bootdisk:/
1 -rw- 74328548 Jan 25 2008 16:12:16 +00:00 s72033-ipservicesk9_wan-mz.122-33.SXH.bin
2 -rw- 33554432 Jan 25 2008 02:27:40 +00:00 sea_log.dat
3 -rw- 80075300 Jun 5 2008 14:13:48 +00:00 s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin
1024065536 bytes total (836091904 bytes free)
Router#slavesup-bootdisk:
% Unknown command or computer name, or unable to find computer address
Router#dir slavesup-bootdisk:
Directory of slavesup-bootdisk:/
1 -rw- 74328548 Jan 25 2008 16:18:40 +00:00 s72033-ipservicesk9_wan-mz.122-33.SXH.bin
2 -rw- 33554432 Jan 25 2008 02:32:36 +00:00 sea_log.dat
3 -rw- 80075300 Jun 5 2008 15:24:54 +00:00 s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin
1024065536 bytes total (836091904 bytes free)
Router#dit slavedisk0:
^
% Invalid input detected at '^' marker.
Router#dir slavesup-bootflash:
Directory of slavesup-bootdisk:/
1 -rw- 74328548 Jan 25 2008 16:18:40 +00:00 s72033-ipservicesk9_wan-mz.122-33.SXH.bin
2 -rw- 33554432 Jan 25 2008 02:32:36 +00:00 sea_log.dat
3 -rw- 80075300 Jun 5 2008 15:24:54 +00:00 s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin
1024065536 bytes total (836091904 bytes free)
Router#dir sup-bootflash:
Directory of sup-bootdisk:/
1 -rw- 74328548 Jan 25 2008 16:12:16 +00:00 s72033-ipservicesk9_wan-mz.122-33.SXH.bin
2 -rw- 33554432 Jan 25 2008 02:27:40 +00:00 sea_log.dat
3 -rw- 80075300 Jun 5 2008 14:13:48 +00:00 s72033-adventerprisek9_wan-mz.122-33.SXH2a.bin
06-05-2008 08:18 PM
Try this,
no boot sys all
boot system sup-bootdisk:
wr mem
verify - sh boot
reload
This is a bug from previous versions, but it is said to have been fixed in 12.2.32 SXH2a. You might have to open a SR with tac if this doesnt works.
HTH
Raj
06-06-2008 05:58 AM
I have opened the SR but the engineer has been no help. Can you provide me the bug ID? I have tried searching for bug i couldn't find one.
Thanks.
06-05-2008 07:11 AM
You will have to copy an image of the new IOS to the standby sup720.
If during bootup, the image version information does not match, the system runs in RPR mode, instead of SSO.
Please see the following link for Fast Software Upgrade information for your configuration:
Use this link for info on upgrading SRM/DRM to SSO:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide