Solved: ISSU 7606 standby supervisor is in "cold standby" state

Eugene Khabarov · ‎06-09-2011

Hi,All! I was performing ISSU on 7606 following this document:

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6550/prod_white_paper0900aecd80456d57.pdf

After the first step (issu loadversion) i've spotted the problem, standby supervisor moved to "cold standby" state, although it was expected "hot standby":

My redundancy configururation:

core-7606-01#sh run | sec redundancy

redundancy

main-cpu

auto-sync running-config

mode sso

core-7606-01#show redundancy

Redundant System Information :

------------------------------

Available system uptime = 44 weeks, 2 days, 6 hours, 12 minutes

Switchovers system experienced = 0

Standby failures = 3

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 5

Current Software state = ACTIVE

Uptime in current state = 44 weeks, 2 days, 6 hours, 12 minutes

Image Version = Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVENTERPRISEK9-M), Version 12.2(33)SRD, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Thu 23-Oct-08 17:55 by prod_rel_team

BOOT = bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD.bin,12

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Peer Processor Information :

----------------------------

Standby Location = slot 6

Current Software state = STANDBY COLD

Uptime in current state = 23 minutes

Image Version = Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVENTERPRISEK9-M), Version 12.2(33)SRD4, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Mon 22-Feb-10 01:06 by prod_rel_team

BOOT = bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD4.bin,12;bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD.bin,12

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

core-7606-01#sh redundancy states

my state = 13 -ACTIVE

peer state = 4 -STANDBY COLD

Mode = Duplex

Unit = Primary

Unit ID = 5

Redundancy Mode (Operational) = rpr

Redundancy Mode (Configured) = sso

Redundancy State = rpr

Maintenance Mode = Disabled

Communications = Up

client count = 128

client_notification_TMR = 30000 milliseconds

keep_alive TMR = 9000 milliseconds

keep_alive count = 1

keep_alive threshold = 18

RF debug mask = 0x0

After issu loadversion bootvar looks as following:

core-7606-01#sh bootvar

BOOT variable = bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD.bin,12

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby BOOT variable = bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD4.bin,12;bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRD.bin,12

Standby CONFIG_FILE variable =

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

So my question is what to do next? I can't run "issu runversion" because downtime will follow I think.

rsimoni · ‎06-19-2011

Hi Eugene,

it seems that you don't have finished the ISSU upgrade completely.

Sup on slot 6 runs SRD4, I suppose the new image you want to run, while the one on slot 5 runs SRD (which I suppose is the original image).

Considering that the now active Sup in slot 5 "Uptime in current state = 44 weeks, 2 days, 6 hours, 12 minutes" while the one on slot 6 "Uptime in current state = 23 minutes" I think you forgot the final reload of one sup.

If you don't remember at which stage you are force switchover will let you failover to the sup on slot 6 while the one on slot 5 will reload on SRD4. You need to make sure that the bootvariable points to the correct image first, right now slot 5 still points to SRD.

Riccardo

View solution in original post

Adrian Lazar · ‎06-19-2011

Hi,

You could try setting the boot variable of the active supervisor to be the same as for the standby and then reboot the standby again. Currently you are in RPR mode which usually means that there is a difference in the configurations of the two supervisors.

Regards,

Adrian

rsimoni · ‎06-19-2011