6500, SUP2: %PFREDUN-SP-4-BOOTSTRING_INVALID

[BSmith2277]

Greetings!

We have an elderly 6506 with redundant SUP2 in SSO mode.
Each SUP2 card sports a flashcard.

We get the following error in the log:

%PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slaveslot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin is not present in standby

However, the image is on both flashcards.

Here are the results from a couple of show commands of my boot settings

Show Boot
JV-CORE#sh boot
BOOT variable = slot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin,12;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102

Standby is up
Standby has 458752K/65536K bytes of memory.

Standby BOOT variable = slot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin,12;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable =
Standby Configuration register is 0x2102

Show sup-bootflash:
JV-CORE#show sup-bootflash:
-#- ED ----type---- --crc--- -seek-- nlen -length- ---------date/time--------- name
1   .. image        6A7B9967 1887B2C   28 25197228 Dec 5 2005 15:22:49 -05:00 c6sup22-dsv-mz.121-26.E4.bin
2   .D ascii text   31EB2934 1926530   18   649603 Feb 18 2014 14:57:05 -05:00 upg_sp_rommon.srec
3   .D ascii text   31EB2934 19C4F34   18   649603 Feb 18 2014 14:59:08 -05:00 upg_sp_rommon.srec
4   .. crashinfo    7D4F7680 19FAEE4   25   220975 Dec 19 2014 21:05:41 -05:00 crashinfo_20141220-020541

Show Redundancy
JV-CORE#show redundancy
Redundant System Information :
------------------------------
       Available system uptime = 6 days, 2 hours, 14 minutes
Switchovers system experienced = 0
              Standby failures = 8
        Last switchover reason = none

                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up

Current Processor Information :
-------------------------------
               Active Location = slot 1
        Current Software state = ACTIVE
       Uptime in current state = 6 days, 2 hours, 13 minutes
                 Image Version = Cisco Internetwork Operating System Software
IOS (tm) s222_rp Software (s222_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF17b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by cisco Systems, Inc.
Compiled Tue 15-Mar-11 18:50 by ccai
                          BOOT = slot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102

Peer Processor Information :
----------------------------
              Standby Location = slot 2
        Current Software state = STANDBY HOT
       Uptime in current state = 16 hours, 21 minutes
                 Image Version = Cisco Internetwork Operating System Software
IOS (tm) s222_rp Software (s222_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF17b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by cisco Systems, Inc.
Compiled Tue 15-Mar-11 18:50 by ccai
                          BOOT = slot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin,12;
                       BOOTLDR =
        Configuration register = 0x2102

Question: How do I tell the switch to discover and happy with the image in the redundant SUP2 card?
As always, comments, suggestions, opinions and flames are welcome.

Thank you!

Bryan Smith

[InayathUlla Sharieff · Accepted solution]

Bryan,

Error Message    PFREDUN-4-BOOTSTRING_INVALID: The bootfile [chars]
is not present in standby

Explanation This message indicates that the bootfile that is configured is 
not present on the redundant supervisor engine. If the redundant 
supervisor engine resets, it will not come up because it will not find the 
image specified in the bootstring.

Action plan:

1. Take out the boot variable , write the memory and reconfigure it. 

2. If you notice that current boot variable is set to slot0: , where as we
are actually booting from disk0:. Though both these terms are used
synonymously.

I found this bug CSCee29647
<http://wwwin-metrics.cisco.com/cgi-bin/ddtsdisp.cgi?id=CSCee29647>  but it
can only be verified once we try booting up the standby supervisor. 

HTH

Regards

Inayath

**Plz rate all usefull posts.

[fariha zain]

Thanks for the info I too have the similar issue.

[BSmith2277]

Inayath,

Thank you for your reply.

Wow...I totally overlooked the slot0: versus the disk0:
I feel somewhat embarrassed now.
I couldn't see the forest because of all the trees.

Allow me to review what you've told me: 
I issued the no boot slot0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin
Executed a write command
Next, I issued the boot disk0:/s222-advipservicesk9_wan-mz.122-18.SXF17b.bin and finished with another wr command.

I think that's it!  MANY THANKS!

Should I be concerned about the really old image stored on bootflash:/ and sup-bootflash:/

Directory of bootflash:/

    1  -rw-     1861080   Dec 5 2005 14:18:03 -05:00  c6msfc2-boot-mz.121-26.E4.bin
    2  -rw-        1224  Mar 20 2014 07:48:00 -04:00  vlan.dat
  

31981568 bytes total (29815644 bytes free)

JV-CORE#dir sup-bootflash:
Directory of sup-bootflash:/

    1  -rw-    25197228   Dec 5 2005 15:22:49 -05:00  c6sup22-dsv-mz.121-26.E4.bin
 

Thank you!

Bryan Smith

[InayathUlla Sharieff · Accepted solution]

Should I be concerned about the really old image stored on bootflash:/ and sup-bootflash:/

Answer:- NO you can remove that to free up some space on the bootflash.

HTH

Regards

Inayath