Informazioni sull'upgrade del software Fast Enhanced - Quad-SUP su Catalyst 6500 VSS

Introduzione

Questo documento descrive una procedura ISSU/eFSU passo per gli switch Cisco Catalyst serie 6500 in modalità VSS con l'uso del Supervisor 6T con dual-homed in una configurazione Quad-SUP.

Prerequisiti

Requisiti

Cisco raccomanda la conoscenza dei seguenti argomenti:

• Conoscenze base di configurazione e configurazione del sistema VSS (Virtual Switching System) QUAD-SUP di Catalyst 6500
• Copia di immagini mediante il metodo TFTP/USB/WebUI

Componenti usati

Per questo documento, è stato usato un sistema di switching virtuale Cisco Catalyst 6500 con software Cisco IOS® versione 15.5(1)SY12 o successive

versioni software e hardware.

Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.

Topologia

Verifica matrice di compatibilità

Passaggio 1. Fare riferimento a questo documento di Cisco; https://www.cisco.com/c/en/us/support/switches/catalyst-6500-series-switches/products-release-notes-list.html#anchor142.

Passaggio 2. Verificare di aver utilizzato il comando nella CLI del dispositivo:

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)

Procedura di aggiornamento

Passaggio 1. Verificare che la nuova immagine Cisco IOS (software Cisco IOS versione 15.5(1)SY13) sia presente nell'bootdisk,slavebootdisk,ics-bootdisk,slave-ics-bootdiskhost.

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

Passaggio 2. Utilizzare questi comandi per verificare che il servizio Copia Shadow del volume sia pronto per eseguire la procedura di aggiornamento:

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

Passaggio 3. Utilizzare il comando issu loadversionper avviare il processo di aggiornamento.

In questo passaggio, lo chassis in standby VSS viene riavviato, ricaricato con la nuova immagine e inizializzato come chassis in standby VSS in modalità di ridondanza SSO (Stateful Switchover), eseguendo la nuova immagine. Questo passaggio è completo quando la configurazione dello chassis viene sincronizzata, come indicato dal messaggio Sincronizzazione in blocco riuscita. Il caricamento della nuova immagine e il passaggio dello chassis in standby VSS alla modalità SSO possono richiedere da alcuni secondi a pochi minuti.

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.

Passaggio 4. La variabile di avvio per la modalità standby deve puntare a una nuova immagine nell'output del show issu state detail comando.

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             

Passaggio 5. Quando lo chassis in standby VSS esegue correttamente la nuova immagine nello stato di ridondanza SSO e tutte le schede di linea sullo chassis in standby VSS sono attive e in linea, immettere il comando Issu runversion per forzare il passaggio. Lo chassis in standby VSS aggiornato diventa il nuovo chassis attivo, eseguendo la nuova immagine. Lo chassis precedentemente attivo viene ricaricato e inizializzato come nuovo chassis in standby VSS in modalità SSO, eseguendo l'immagine precedente (nel caso in cui l'aggiornamento del software debba essere interrotto e l'immagine precedente ripristinata). Questo passaggio è completo quando la configurazione dello chassis viene sincronizzata, come indicato dal messaggio Sincronizzazione in blocco riuscita.

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

Passaggio 6. Verificare lo stato al termine del passaggio.

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

Passaggio 7. Per interrompere il timer di rollback, usare il comando issu ACCEPTversion. Ciò è necessario perché se il timer scade, lo chassis aggiornato viene ricaricato e viene ripristinata la versione software precedente.

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                                              

Passaggio 8. Se nell'installazione viene utilizzato Fabric Extender (FEX), utilizzare il comando debug runversion fex all per avviare la procedura di download e aggiornamento dell'immagine sul server FEX (6800IA). Il FEX attiva il download dell'immagine dal nuovo pacchetto software del Supervisor6T (qui, il software Cisco IOS versione 15.5(1)SY13). Se si utilizzano stack FEX, il dispositivo master è responsabile dell'estrazione dell'immagine dai relativi membri.

Passaggio 9. Per continuare, immettere il comando commit version per aggiornare lo chassis in standby VSS e completare la sequenza ISSU (In-Service Software Upgrade). Lo chassis in standby VSS si riavvia, viene ricaricato con la nuova immagine e viene inizializzato come chassis in standby VSS in stato di ridondanza SSO, eseguendo la nuova immagine. Questo passaggio è completo quando la configurazione dello chassis è sincronizzata, come indicato dal messaggio Bulk sync successfully (Sincronizzazione di massa riuscita), e tutte le schede di linea sul nuovo VSS-Standby sono attive e online.

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]

Passaggio 10. Verificare se l'aggiornamento è stato completato.

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

Risoluzione dei problemi

Scenario 1. Aggiornamento in modalità sfalsata in assenza di connettività VSL incrociata

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.

Viene visualizzato un messaggio di errore che indica che il requisito non è soddisfatto perché non si dispone di una connessione VSL incrociata per procedere.

È possibile eseguire l'aggiornamento disabilitando lo sfalsamento.

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 e sfalsato

Anche l'aggiornamento del VSS per il tandem o il Supervisor doppio (SUP) è possibile. Tuttavia, viene messo offline uno chassis durante l'intero periodo di avvio dei supervisori.

Un supervisore alla volta viene ricaricato nella modalità predefinita di Sup2T, in modalità sfalsata. Ciò implica che un supervisore che utilizza tale versione è presente quando le schede di linea sono preparate per il ricaricamento. Dal momento che le schede di linea si ricaricano molto più velocemente dei supervisori, lo chassis presenta tempi di inattività notevolmente inferiori.

Inoltre, indica che è disponibile un supervisore che utilizza il programma obsoleto, fornendo un tempo di rollback molto più veloce, se necessario. Per Sup2T, la modalità predefinita è sfalsata.

Con questo comando è possibile disattivare il metodo di aggiornamento sfalsato.

Scenario 2. Attivo con immagine precedente

In pratica, qui si può essere colpiti dalla versione di esecuzione IOS.

Per la versione di esecuzione IOS è già abilitato un timer di rollback. Se non è possibile procedere oltre, il timer torna automaticamente all'immagine precedente.

Per quanto riguarda la versione di commit ISSU, il timer di rollback è disabilitato perché è stata fornita una versione accettata. È quindi necessario eseguire questo comando per ripristinare l'immagine precedente.

WS-C6504-E-1# issu abortversion

Scenario 3. Dopo il passaggio alla modalità standby non è più disponibile

Scollegare fisicamente il collegamento Virtual Switch Link (VSL) e aggiornare il dispositivo alla nuova immagine utilizzando il metodo USB/TFTP.

Dopo l'aggiornamento, spegnere il dispositivo. Collegare il collegamento VSL e portare il dispositivo nel VSS in modo che possa formare uno standby.

Scenario 4. La versione di SUP ICS successiva all'aggiornamento rimane precedente

Collegare la SUP da sola in uno chassis di riserva o in uno chassis di standby in cui l'impatto non è visibile poiché il dispositivo attivo funziona correttamente.

Aggiornare il dispositivo a una nuova immagine utilizzando il metodo USB/TFTP.

Spegnerlo e portarlo nello stesso slot in modo che l'immagine venga aggiornata e ritorni come in-Chassis Standby (ICS) con un'immagine più recente.