besseres Verständnis für erweitertes schnelles Software-Upgrade - Quad-SUP auf Catalyst 6500 VSS

Einleitung

In diesem Dokument wird ein schrittweises ISSU/eFSU-Verfahren für Cisco Catalyst Switches der Serie 6500 im VSS-Modus unter Verwendung des Supervisor 6T mit Dual-Homed in einer Quad-SUP-Konfiguration beschrieben.

Voraussetzungen

Anforderungen

Cisco empfiehlt, dass Sie über Kenntnisse in folgenden Bereichen verfügen:

• Grundkenntnisse der Einrichtung und Konfiguration des QUAD-SUP Virtual Switching System (VSS) des Catalyst 6500
• Kopieren von Bildern mithilfe der TFTP-/USB-/WebUI-Methode

Verwendete Komponenten

Die Informationen in diesem Dokument basieren auf dem Cisco Catalyst 6500 Virtual Switching System auf der Cisco IOS® Software-Version 15.5(1)SY12 oder höher.

Software- und Hardwareversionen.

Die Informationen in diesem Dokument beziehen sich auf Geräte in einer speziell eingerichteten Testumgebung. Alle Geräte, die in diesem Dokument benutzt wurden, begannen mit einer gelöschten (Nichterfüllungs) Konfiguration. Wenn Ihr Netzwerk in Betrieb ist, stellen Sie sicher, dass Sie die möglichen Auswirkungen aller Befehle kennen.

Topologie

Überprüfung der Kompatibilitätsmatrix

Schritt 1: Weitere Informationen finden Sie in diesem Cisco Dokument unter https://www.cisco.com/c/en/us/support/switches/catalyst-6500-series-switches/products-release-notes-list.html#anchor142.

Schritt 2: Überprüfen Sie mithilfe des Befehls in der Geräte-CLI,

WS-C6504-E-1#show issu comp-matrix stored

Number of Matrices in Table = 1

(1) Matrix for s2t54-ADVENTERPRISEK9-M(10) - s2t54-ADVENTERPRISEK9-M(10) 
==========================================
Start Flag (0xDEADBABE)

My Image ver: 15.5(1)SY13
Peer Version Compatibility
------------ -------------
15.1(2)SY Incomp(1)
15.1(2)SY1 Incomp(1)
15.1(2)SY2 Incomp(1)
15.5(1)SY Dynamic(0)
15.5(1)SY1 Dynamic(0)
15.1(2)SY12 Incomp(1)
15.2(1)SY6 Incomp(1)
15.4(1)SY4 Incomp(1)
15.5(1)SY2 Dynamic(0)
15.5(1)SY3 Dynamic(0)
15.5(1)SY4 Dynamic(0)
15.5(1)SY5 Dynamic(0)
15.5(1)SY6 Dynamic(0)
15.5(1)SY7 Dynamic(0)
15.5(1)SY8 Dynamic(0)
15.5(1)SY9 Dynamic(0)
15.5(1)SY10 Dynamic(0)
15.5(1)SY11 Dynamic(0)
15.5(1)SY12 Dynamic(0)
15.5(1)SY13 Comp(3)

Upgrade-Verfahren

Schritt 1: Stellen Sie sicher, dass das neue Cisco IOS-Image (Cisco IOS Software, Version 15.5(1)SY13) im vorhanden istbootdisk,slavebootdisk,ics-bootdisk,slave-ics-bootdisk.

WS-C6504-E-1#dir bootdisk: | i SY13 
8 -rw- 167430292 Apr 16 2024 22:55:58 +00:00 s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
WS-C6504-E-1#dir slavebootdisk: | i SY13 
19 -rw- 167430292 Apr 16 2024 00:37:58 +00:00 s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
WS-C6504-E-1#dir ics-bootdisk: | i SY13 
11 -rw- 167430292 Apr 16 2024 23:06:18 +00:00 s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
WS-C6504-E-1#dir slave-ics-bootdisk: | i SY13
5 -rw- 167430292 Apr 16 2024 23:20:18 +00:00 s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin

Schritt 2: Verwenden Sie diese Befehle, um sicherzustellen, dass das VSS zur Ausführung des Upgrade-Vorgangs bereit ist:

WS-C6504-E-1#show redundancy
Redundant System Information :
------------------------------
       Available system uptime = 1 day, 4 hours, 41 minutes
Switchovers system experienced = 0
              Standby failures = 1
        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/1
        Current Software state = ACTIVE                                                           >> Switch 1 Slot 1 is active
       Uptime in current state = 1 day, 4 hours, 41 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY12, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Tue 05-Sep-23 11:24 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102
Peer Processor Information :
----------------------------
              Standby Location = slot 2/1                         
        Current Software state = STANDBY HOT                                                      >> Switch 2 Slot 1 is standby
       Uptime in current state = 19 hours, 43 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY12, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Tue 05-Sep-23 11:24 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102

WS-C6504-E-1#show issu state detail
 The system is configured to be upgraded in staggered mode.
 4 supervisor nodes are found to be online.
 Summary: the system will be upgraded in staggered mode.

Slot = 1/1
RP State = Active
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 2/1
RP State = Standby
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 1/2
RP State = Active-ICS
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 2/2
RP State = Standby-ICS
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Schritt 3: Verwenden Sie den issu loadversionBefehl, um den Upgrade-Prozess zu starten.

In diesem Schritt wird das VSS-Standby-Chassis neu gestartet, mit dem neuen Image neu geladen und als VSS-Standby-Chassis im SSO-Redundanzmodus initialisiert, wobei das neue Image ausgeführt wird. Dieser Schritt ist abgeschlossen, wenn die Chassis-Konfiguration synchronisiert wird, wie in der Meldung Bulk sync successfully (Massensynchronisierung erfolgreich) angegeben. Das Laden des neuen Images und der Übergang des VSS-Standby-Chassis in den SSO-Modus können einige Sekunden bis zu einigen Minuten dauern.

WS-C6504-E-1#issu loadversion 1/1 bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin 2/1 slavebootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
*Apr 17 00:43:14.195: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion sequence will begin in 60 seconds. Enter 'issu abortversion' to cancel.
*Apr 17 00:43:44.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Resetting Standby shortly
*Apr 17 00:43:44.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Resetting Standby ICS shortly
*Apr 17 00:43:44.199: %ISSU_PROCESS-SW2_STBY-6-SELF_RELOAD: slot 33 countdown to self-reload started, 30 second delay
*Apr 17 00:43:44.199: %ISSU_PROCESS-SW2-2_STBY-6-SELF_RELOAD: slot 34 countdown to self-reload started, 30 second delay
*Apr 17 00:44:29.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby ICS has gone offline
*Apr 17 00:44:29.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby has gone offline
*Apr 17 00:46:59.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby has come online, wait for Standby ICS
*Apr 17 00:47:44.503: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby ICS has come online
*Apr 17 00:49:15.363: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby reached terminal state
*Apr 17 00:49:29.199: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Standby ICS reached terminal state, wait for system to settle
*Apr 17 00:49:59.195: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion has completed. Please issue the 'issu runversion' command after all modules come online.
*Apr 17 00:49:59.195: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion has completed. Please issue the 'issu runversion' command after all modules come online.

Schritt 4: Die Boot-Variable für Standby muss auf ein neues Image in der show issu state detail Ausgabe zeigen.

WS-C6504-E-1#show issu state detail
 The system is configured to be upgraded in in-tandem mode.
 4 supervisor nodes are found to be online.
         Summary: an in-tandem upgrade is in progress.

Slot = 1/1
RP State = Active
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12
      Operating Mode = sso
      ISSU Sub-State = Load Version Completed
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 2/1
RP State = Standby
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = Load Version Completed
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin                       >> Standby Chassis has been upgraded to latest code

Slot = 1/2
RP State = Active-ICS
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12
      Operating Mode = sso
      ISSU Sub-State = Load Version Completed
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 2/2
RP State = Standby-ICS
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = Load Version Completed
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin                       >> Standby Chassis has been upgraded to latest code             

Schritt 5: Wenn das VSS-Standby-Chassis das neue Image im SSO-Redundanzstatus erfolgreich ausführt und alle Linecards im VSS-Standby-Chassis online sind, geben Sie den Befehl issu runversion ein, um einen Switchover zu erzwingen. Das aufgerüstete VSS-Standby-Chassis übernimmt das neue aktive Chassis, auf dem das neue Image ausgeführt wird. Das zuvor aktive Chassis wird neu geladen und initialisiert, während das neue VSS-Standby-Chassis im SSO-Modus das alte Image ausführt (falls das Software-Upgrade abgebrochen und das alte Image wiederhergestellt werden muss). Dieser Schritt ist abgeschlossen, wenn die Chassis-Konfiguration synchronisiert wird, wie in der Meldung Bulk sync successfully (Massensynchronisierung erfolgreich) angegeben.

WS-C6504-E-1#issu runversion
This command will reload the Active unit.  Proceed ? [confirm]y
%issu runversion initiated successfully
*Apr 17 00:54:42.707: %ISSU_PROCESS-SW1-2_STBY-6-SELF_RELOAD: slot 18 countdown to self-reload started, 3 second delay
*Apr 17 00:54:44.715: %RF-SW1-5-RF_RELOAD: Self reload. Reason: Admin ISSU runversion CLI
*Apr 17 00:54:46.719: %SYS-SW1-5-SWITCHOVER: Switchover requested by Exec. Reason: Admin ISSU runversion CLI.
Initializing as Virtual Switch STANDBY processor
*Apr 17 00:57:14.023: %VSLP-5-VSL_UP:  Ready for control traffic
*Apr 17 00:57:24.919: %PFREDUN-SW1_STBY-6-STANDBY: Initializing for SSO mode in Default Domain

Schritt 6: Überprüfen Sie den Status, sobald der Switchover abgeschlossen ist.

WS-C6504-E-1#show issu state detail
 The system is configured to be upgraded in in-tandem mode.
 4 supervisor nodes are found to be online.
         Summary: an in-tandem upgrade is in progress.

Slot = 2/1
RP State = Active
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = Run Version after Switchover
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin                       >> Switch 2 became the active after switchover        

Slot = 1/1
RP State = Standby
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = Run Version in Progress
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

Slot = 2/2
RP State = Active-ICS
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = Run Version in Progress
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin

Slot = 1/2
RP State = Standby-ICS
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
      Operating Mode = sso
      ISSU Sub-State = Run Version in Progress
      Starting Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin
        Target Image = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin

WS-C6504-E-1#sh redundancy    
Redundant System Information :
------------------------------
       Available system uptime = 44 minutes
Switchovers system experienced = 1
              Standby failures = 0
        Last switchover reason = user forced
                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up
Current Processor Information :
-------------------------------
               Active Location = slot 2/1
        Current Software state = ACTIVE
       Uptime in current state = 7 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY13, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2024 by Cisco Systems, Inc.
Compiled Tue 19-Mar-24 06:59 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102
Peer Processor Information :
----------------------------
              Standby Location = slot 1/1
        Current Software state = STANDBY HOT
       Uptime in current state = 2 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY12, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Tue 05-Sep-23 11:24 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102

Schritt 7: Verwenden Sie den Befehl issu acceptVersion, um den Rollback Timer zu stoppen. Dies ist erforderlich, da das aktualisierte Chassis nach Ablauf des Zeitraums neu geladen und auf die vorherige Softwareversion zurückgesetzt wird.

WS-C6504-E-1# show issu rollback-timer
Rollback Process State = In progress
 Configured Rollback Time = 00:45:00
 Automatic Rollback Time = 00:37:28

WS-C6504-E-1# issu acceptversion
% Rollback timer stopped. Please issue the commitversion command.
View the rollback timer to see that the rollback process has been stopped:
WS-C6504-E-1# show issu rollback-timer
Rollback Process State = Not in progress                                                         >> Rollback Process is stopped after the acceptversion                                              

Schritt 8: Falls Fabric Extender (FEX) in der Konfiguration verwendet wird, verwenden Sie den Befehl issu runversion fex all, um das Image-Download- und Upgrade-Verfahren für den FEX (6800IA) zu starten. Der FEX löst den Image-Download aus dem neuen Softwarepaket von Supervisor6T aus (hier: Cisco IOS Software Release 15.5(1)SY13). Wenn Sie FEX-Stacks verwenden, ist der Master für das Extrahieren des Bilds aus seinen Mitgliedern verantwortlich.

Schritt 9: Geben Sie zum Fortfahren den Befehl issu commitVersion ein, um das VSS-Standby-Chassis zu aktualisieren, und führen Sie die In-Service Software Upgrade (ISSU)-Sequenz aus. Das VSS-Standby-Chassis wird neu gestartet, mit dem neuen Image neu geladen und initialisiert sich im SSO-Redundanzstatus als VSS-Standby-Chassis, wobei das neue Image ausgeführt wird. Dieser Schritt ist abgeschlossen, wenn die Chassis-Konfiguration synchronisiert wird (wie in der Meldung Bulk sync successfully (Massensynchronisierung erfolgreich) angezeigt wird) und alle Linecards auf dem neuen VSS-Standby online sind.

WS-C6504-E-1# issu commitversion
%issu commitversion initiated successfully, upgrade sequence will continue shortly

WS-C6504-E-1#
*Apr 17 01:02:57.607: %ISSU_PROCESS-SW2-3-COMMITVERSION: issu commitversion; Commitversion sequence will begin in 60 seconds. Enter 'issu abortversion' to cancel.
*Apr 17 01:03:27.607: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Resetting Standby shortly
*Apr 17 01:03:27.607: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Resetting Standby ICS shortly
*Apr 17 01:03:27.611: %ISSU_PROCESS-SW1-2_STBY-6-SELF_RELOAD: slot 18 countdown to self-reload started, 30 second delay
*Apr 17 01:03:27.611: %ISSU_PROCESS-SW1_STBY-6-SELF_RELOAD: slot 17 countdown to self-reload started, 30 second delay
*Apr 17 01:04:12.607: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby ICS has gone offline
*Apr 17 01:04:12.607: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has gone offline
*Apr 17 01:06:42.607: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has come online, wait for Standby ICS
*Apr 17 01:07:28.315: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby ICS has come online
*Apr 17 01:08:59.623: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has reached terminal state
*Apr 17 01:09:12.699: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby ICS reached terminal state
*Apr 17 01:09:12.751: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Upgrade has completed, updating boot configuration
Building configuration...
[OK]

Schritt 10: Überprüfen Sie, ob das Upgrade abgeschlossen wurde.

WS-C6504-E-1#sh redundancy
Redundant System Information :
------------------------------
       Available system uptime = 55 minutes
Switchovers system experienced = 1
              Standby failures = 1
        Last switchover reason = user forced
                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up
Current Processor Information :
-------------------------------
               Active Location = slot 2/1
        Current Software state = ACTIVE
       Uptime in current state = 17 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY13, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2024 by Cisco Systems, Inc.
Compiled Tue 19-Mar-24 06:59 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102
Peer Processor Information :
----------------------------
              Standby Location = slot 1/1
        Current Software state = STANDBY HOT
       Uptime in current state = 3 minutes
                 Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.5(1)SY13, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2024 by Cisco Systems, Inc.
Compiled Tue 19-Mar-24 06:59 by mcpre
                          BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12                             >> Standby has been upgraded
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102

WS-C6504-E-1# show module switch all
 Switch Number:     1   Role:  Virtual Switch Standby
----------------------  -----------------------------
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1    5  Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G       xxxx
  2    5  Supervisor Engine 2T 10GE w/ CTS (CSSO VS-SUP2T-10G       xxxx
  3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     xxxx
Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 1.5   12.2(50r)SYS 15.5(1)SY13  Ok
  2  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 1.3   12.2(50r)SYS 15.5(1)SY13  Ok
  3  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 3.2   12.2(18r)S1  15.5(1)SY13  Ok
Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  1  Policy Feature Card 4       VS-F6K-PFC4         xxxx        1.2    Ok
  1  CPU Daughterboard           VS-F6K-MSFC5        xxxx        2.0    Ok
  2  Policy Feature Card 4       VS-F6K-PFC4         xxxx        1.2    Ok
  2  CPU Daughterboard           VS-F6K-MSFC5        xxxx        1.4    Ok
  3  Centralized Forwarding Card WS-F6700-CFC        xxxx        4.1    Ok
Mod  Online Diag Status
---- -------------------
  1  Pass
  2  Pass
  3  Pass
 Switch Number:     2   Role:   Virtual Switch Active
----------------------  -----------------------------
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1    5  Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G       xxxx
  2    5  Supervisor Engine 2T 10GE w/ CTS (CSSO VS-SUP2T-10G       xxxx
  3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     xxxx
Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 1.5   12.2(50r)SYS 15.5(1)SY13  Ok
  2  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 2.1   12.2(50r)SYS 15.5(1)SY13  Ok
  3  xxxx. xxxx. xxxx to xxxx. xxxx. xxxx 3.6   12.2(18r)S1  15.5(1)SY13  Ok
Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  1  Policy Feature Card 4       VS-F6K-PFC4        xxxx         1.2    Ok
  1  CPU Daughterboard           VS-F6K-MSFC5       xxxx         2.0    Ok
  2  Policy Feature Card 4       VS-F6K-PFC4        xxxx         3.0    Ok
  2  CPU Daughterboard           VS-F6K-MSFC5       xxxx         3.1    Ok
  3  Centralized Forwarding Card WS-F6700-CFC       xxxx         4.1    Ok
Mod  Online Diag Status
---- -------------------
  1  Pass
  2  Pass
  3  Pass

WS-C6504-E-1# sh issu state detail
 The system is configured to be upgraded in in-tandem mode.
 4 supervisor nodes are found to be online.
 Summary: the system will be upgraded in in-tandem mode.
Slot = 2/1
RP State = Active
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
Slot = 1/1
RP State = Standby
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
Slot = 2/2
RP State = Active-ICS
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
Slot = 1/2
RP State = Standby-ICS
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY12.bin,12
      Operating Mode = sso
      ISSU Sub-State = No Upgrade Operation in Progress
      Starting Image = N/A
        Target Image = N/A
     Current Version = bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin

Fehlerbehebung - Anwenderberichte

1. Szenario: Upgrade im gestaffelten Modus, wenn keine VSL-übergreifende Verbindung vorhanden ist

WS-C6504-E-1#issu loadversion 1/1 bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin 2/1 slavebootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
WS-C6504-E-1#*Apr 16 23:31:12.528: SW1:  Quad-sup ISSU Staggered mode VSL requirement(Parallel/Cross VSL connectivity) is NOT met. Disable Staggered mode using config cli "no issu upgrade staggered" to perform ISSU in default mode which is In-tandem.

In einer Fehlermeldung wird darauf hingewiesen, dass die Anforderung nicht erfüllt ist, da keine VSL-übergreifende Verbindung zur Verfügung steht.

Sie können das Upgrade durchführen, indem Sie die gestaffelte Option deaktivieren.

WS-C6504-E-1(conf t)# no issu upgrade staggered

WS-C6504-E-1#issu loadversion 1/1 bootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin 2/1 slavebootdisk:s2t54-adventerprisek9-mz.SPA.155-1.SY13.bin
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
*Apr 17 00:43:14.195: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion sequence will begin in 60 seconds. Enter 'issu abortversion' to cancel.
*Apr 17 00:43:44.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Resetting Standby shortly
*Apr 17 00:43:44.195: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Resetting Standby ICS shortly

Tandem gegen Staggered

Ein VSS-Upgrade für Tandem- oder Dual-Supervisor (SUP) ist ebenfalls möglich. Während des Bootens des Supervisors ist jedoch ein Gehäuse offline.

Ein Supervisor nach dem anderen wird im Standardmodus des Sup2T, gestaffelt, neu geladen. Dies impliziert, dass ein Supervisor vorhanden ist, der diese Version verwendet, wenn die Linecards für das Neuladen vorbereitet werden. Da die Linecards viel schneller neu geladen werden als die Supervisoren, kommt es zu deutlich weniger Ausfallzeiten im Chassis.

Darüber hinaus zeigt es an, dass ein Supervisor mit dem veralteten Programm verfügbar ist, wodurch die Rollback-Zeit bei Bedarf deutlich verkürzt wird. Für Sup2T ist der Standardmodus gestaffelt.

Die gestaffelte Aktualisierungsmethode kann mit diesem Befehl deaktiviert werden.

Szenario 2. Aktiver Schlag mit älterem Bild

Hier können Sie im Grunde genommen bei der ISSU Run Version getroffen werden.

Für die ISSU-Ausführungsversion ist bereits ein Rollback-Timer aktiviert. Falls Sie nicht fortfahren können, wird der Timer automatisch auf das ältere Bild zurückgesetzt.

In Bezug auf die ISSU-Commit-Version ist der Rollback-Timer deaktiviert, da Sie eine akzeptierte Version angegeben haben. Daher müssen Sie diesen Befehl ausführen, um zu dem älteren Bild zurückzukehren.

WS-C6504-E-1# issu abortversion

Szenario 3. Nach dem Switchover wird der Standby-Modus nicht aktiviert.

Trennen Sie die physische Verbindung zum Virtual Switch Link (VSL), und aktualisieren Sie das Gerät mithilfe der USB-/TFTP-Methode auf das neue Image.

Schalten Sie das Gerät nach der Aktualisierung aus. Schließen Sie den VSL-Link an, und bringen Sie das Gerät in das VSS ein, sodass es ein Standby-Gerät bilden kann.

Szenario 4. Nach dem Upgrade ICS SUP bleibt in älterer Version

Verbinden Sie die SUP alleine in einem Ersatzgehäuse oder Standby-Gehäuse, wo die Auswirkungen nicht sichtbar sind, da die aktive Komponente einwandfrei funktioniert.

Aktualisieren Sie das Gerät mithilfe der USB-/TFTP-Methode auf ein neues Image.

Schalten Sie es anschließend aus, und bringen Sie es in denselben Steckplatz, sodass das Image aktualisiert wird und wieder als In-Chassis Standby (ICS) mit einem neueren Image angezeigt wird.