03-03-2011 02:09 AM - edited 03-06-2019 03:52 PM
Hi team,
I have an outstanding SUP redundancy issue forone of my customer data center 6509 switch.
1. 6509 configured for sso as bellow
redundancy
mode sso
main-cpu
auto-sync running-config
boot system flash sup-bootdisk:
sw01#show sup-bootdisk:
-#- --length-- -----date/time------ path
1 33554432 Jan 06 2008 17:44:00 sea_log.dat
2 81764868 Mar 07 2008 17:04:18 s72033-ipservicesk9_wan-mz.122-18.SXF7.bin <-------------
396779520 bytes available (115326976 bytes used)
sw01#show slavebootflash:
-#- ED ----type---- --crc--- -seek-- nlen -length- ---------date/time--------- name
1 .. unknown 154D5D43 850C0 25 20544 --- -- ---- --:--:-- ----- crashinfo-20080224-161537
2 .. unknown B2ACB36B 852C4 38 388 --- -- ---- --:--:-- ----- crashinfo_kernel_trace-20080224-161537
2. Two SUPs have different IOS on it so obviously the operational mode RPR mode but we need SSO mode.
(Versioning problem)
3. Could you please advice an action plan to upgrade these two SUPS to same IOS in-order to run intended SSO high availability mode.
4. Also please advice which of these two IOS is latest and better one?
Thank you very much in advance
Sanjeev
sw01#show module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1201BUP1
2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1202CB0Q
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1201C70C
4 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1201BZQU
5 2 Supervisor Engine 720 (Cold) WS-SUP720-3B SAL1201C1FK <--------
6 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1201C1M4
7 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1202CB0L
8 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1202CB1V
9 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL11456HT2
sw01#show redundancy
Redundant System Information :
------------------------------
Available system uptime = 2 years, 50 weeks, 3 days, 17 hours, 27 minutes
Switchovers system experienced = 0
Standby failures = 2
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 6
Current Software state = ACTIVE
Uptime in current state = 2 years, 50 weeks, 3 days, 17 hours, 26 minutes
Image Version = Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Thu 23-Nov-06 06:42 by kellythw
BOOT = sup-bootdisk:,1;
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Peer Processor Information :
----------------------------
Standby Location = slot 5
Current Software state = STANDBY COLD
Uptime in current state = 2 years, 7 weeks, 13 hours, 30 minutes
Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-VM), Version 12.2(33)SXH, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Sun 19-Aug-07 13:29 by prod_rel_team
BOOT = sup-bootdisk:,1;
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
03-08-2011 01:06 PM
Hi Sanjeev,
If your aim is to just get SSO, then you are correct. You need to get the same image to both SUPs. Either copy from one SUP to another or download a newer version.
Take a look at the release notes and compare them to the features you need.
SXH/SHI:
SXF is getting older. The last release looks like it is from March 2010 (12.2(18)SXF17a):
You can also look on CCO for the software tool:
http://tools.cisco.com/Support/Fusion/FusionHome.do
Lastly, you can contact your SE or NCE for assistance.
Once you get the image on the SUPs (in the same location), disk0, sup-bootdisk...your choice. Schedule a short downtime or wait for a low traffic period. Change the boot statement, save the config, reload the secondary, once it is up, fail over (the active reloads), and you should come up in SSO.
Take a look at the fast upgrade section for more detail:
HTH,
Nelson
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