cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3362
Views
0
Helpful
1
Replies

ISSU loadversion initialized on RPR mode

avm_veera
Level 1
Level 1

Hi,

I have used ISSU for 6509 VSS to upgrade the IOS From s72033-adventerprise_wan-vz.122-33.SXI5.bin,12 to s72033-adventerprisek9_wan-vz.122-33.SXI5.bin,12; version

I have referred below link for ISSU

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/issu_efsu.html#wpxref41569

As per the document there will not be any network outage if we do ISSU for the IOS ver SXI.  The upgrade was success, but I got a network outage of 5 min...Please let me know why it took 5 min Network outage.

Below are the steps followed:-

1)      The command issu loadversion sup-bootdisk:s72033-adventerprisek9_wan-vz.122-33.SXI5.bin reload the standby Sup and booted with the new IOS but the Standby sup becomes STANDBY COLD and the redundancy mode becomes RPR mode.

O/P’s as below

CORE#sh issu state

Slot = 1/5

RP State = Active

ISSU State = Load Version

Boot Variable = bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,12

% Standby information is not available because it is in 'DISABLED' state

CORE#sh issu state

Slot = 1/5

RP State = Active

ISSU State = Load Version

Boot Variable = bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,12

% Standby information is not available because it is in 'DISABLED' state

CORE#sh issu state

Slot = 1/5

RP State = Active

ISSU State = Load Version

Boot Variable = bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,12

Slot = 2/5

RP State = Standby

ISSU State = Load Version

Boot Variable = bootdisk:s72033-adventerprisek9_wan-vz.122-33.SXI5.bin,12;bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,12

CORE#sh redundancy

Redundant System Information :

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

Available system uptime = 1 week, 6 days, 5 hours, 30 minutes

Switchovers system experienced = 4

Standby failures = 1

Last switchover reason = active unit removed

Hardware Mode = Duplex

Configured Redundancy Mode = sso

Operating Redundancy Mode = rpr Reason: Software mismat

Maintenance Mode = Disabled

Communications = Up

Current Processor Information :

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

Active Location = slot 1/5

Current Software state = ACTIVE

Uptime in current state = 1 week, 5 days, 18 hours, 23 minutes

Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISE_WAN-VM), Version 12.2(33)SXI5, RELEASE SOFTWARE (fc2)

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

Copyright (c) 1986-2010 by Cisco Systems, Inc.

Compiled Sat 23-Oct-10 03:26 by prod_rel_team

BOOT = sup-bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,1;

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Peer Processor Information :

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

Standby Location = slot 2/5

Current Software state = STANDBY COLD

Uptime in current state = 2 minutes

Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-VM), Version 12.2(33)SXI5, RELEASE SOFTWARE (fc2)

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

Copyright (c) 1986-2010 by Cisco Systems, Inc.

Compiled Sat 23-Oct-10 07:23 by prod_rel_team

BOOT = sup-bootdisk:s72033-adventerprise_wan-vz.122-33.SXI5.bin,1;

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

2)      The command issu runversion , initialized the standby sup to Active but it took 5 min to make the standby SUP to Active.

3)      Then completed the upgrade with the commands ISSU acceptversion and ISSU commitversion.

Please let me know why the Standby SUP initialized on RPR mode instead of SSO.

1 Reply 1

Yogesh Ramdoss
Cisco Employee
Cisco Employee

Hello,

ISSU from non-crypto to crypto image will fail eFSU/ISSU compatability check.

Reference document:

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/issu_efsu.html#wp1116940

Please note the limitation:

"Images from different features sets, regardless of release, fail the eFSU compatibility check"

eFSU/ISSU fails even when we migrate from modular to non-modular IOS (or vice versa)

Hope this helps.

- Yogesh