Cisco 7613 Router boots from sup-bootdisk instead of disk0 as per boot system command

edwardwaithaka · ‎02-10-2010

Hi,

I have a C7613 with two sup engines in redundant mode (SSO).

My issue is as follows;

I have IOS 12.2.18 in sup-bootdisk and IOS 12.2.33 in disk0 in both SUP720s. I have set the boot variable as "boot system flash disk0:"

The issue is that SUP1 loads with .33 IOS and SUP2 loads with .18 IOS. For some reason SUP2 does not follow the boot system command.

In some cases, SUP2 correctly loads from disk0 using .33 IOS in other cases it loads .18 IOS.

I have another 7613 at a different site with the same setup and IOS and it boots correctly all the time.

The main difference is that I got a replacement SUP for the SUP2 for the router with the above issue and since then I have had the issue. The replacement SUP is identical to the existing SUP (memory,flash,MSFC,etc).

Is there some setting maybe i need to configure for the replacement SUP?

Some output;

7613_01#sh bootvar
BOOT variable = disk0:,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102

Standby BOOT variable = disk0:,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
7613_01#

7613_01#sh redundancy
Redundant System Information :
------------------------------
        Available system uptime = 5 hours, 17 minutes
Switchovers system experienced = 0
               Standby failures = 4
         Last switchover reason = none

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

Current Processor Information :
-------------------------------
                Active Location = slot 7
         Current Software state = ACTIVE
        Uptime in current state = 5 hours, 16 minutes
                  Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ITPK9V-M), Version 12.2(33)IRC, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 01-Apr-09 14:22 by prod_rel_team
                           BOOT = disk0:,1;
                    CONFIG_FILE =
                        BOOTLDR =
         Configuration register = 0x2102

Peer Processor Information :
----------------------------
               Standby Location = slot 8
         Current Software state = STANDBY COLD
        Uptime in current state = 4 hours, 18 minutes
                  Image Version = Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ITPK9V-M), Version 12.2(18)IXF, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Tue 25-Mar-08 15:57 by alnguyen
                           BOOT = disk0:,1;
                        BOOTLDR =
         Configuration register = 0x2102

7613_01#

Reza Sharifi · ‎02-10-2010

Hi Edward,

I know you wrote that you have identical Sup replacement, but can you make sure that the PFC for both Sups are exactly the same?

We had an issue like this before. Cisco have sent us PFC-3CXL instead of 3C and it took us a while to figure it out and send back the 3CXL to get a replaced with a 3C. Also if they are both 3C check the version number and make sure the new one is the same as the old one you aready have.

HTH

Reza

edwardwaithaka · ‎02-10-2010

Hi,

The cards look identical, see below;

NAME: "module 7", DESCR: "WS-SUP720-3B 2 ports Supervisor Engine 720 Rev. 5.7"
PID: WS-SUP720-3B , VID: V06, SN:

NAME: "msfc sub-module of 7", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev. 3.2"
PID: WS-SUP720 , VID: , SN:

NAME: "switching engine sub-module of 7", DESCR: "WS-F6K-PFC3B Policy Feature Card 3 Rev. 2.4"
PID: WS-F6K-PFC3B , VID: V02, SN:

NAME: "module 8", DESCR: "WS-SUP720-3B 2 ports Supervisor Engine 720 Rev. 5.7"
PID: WS-SUP720-3B , VID: V06, SN:

NAME: "msfc sub-module of 8", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev. 3.2"
PID: WS-SUP720 , VID: , SN:

NAME: "switching engine sub-module of 8", DESCR: "WS-F6K-PFC3B Policy Feature Card 3 Rev. 2.4"
PID: WS-F6K-PFC3B , VID: V02, SN:

edwardwaithaka · ‎02-11-2010

Hi,

For some reason the SUP 2 ignores the set boot sting and complains that the variable is empty.

I get the error;

"Autoboot: failed, BOOT string is empty"