Guides you through upgrading Catalyst 9000 switch using one-step ISSU workflow, and confirming the post-upgrade redundancy and software state on the device.
Use this procedure to upgrade a Cisco Catalyst 9000 switch using one-step In-Service Software Upgrade (ISSU) workflow—add, activate, and commit in a single step.
When executing the commands and verifying the outputs, replace <CURRENT_RELEASE> , <TARGET_RELEASE> , <IMAGE.bin> , and SHA-512-VALUE values in the sample outputs with the actual values of your deployment.
To perform device upgrade in ISSU mode using three-step workflow, refer Upgrade the device in ISSU mode: three-step procedure
Before you begin
Note
ISSU is not supported on Cisco Catalyst 9300 series switches.
Proceed only when the ISSU Compatibility Matrix explicitly supports the exact platform, topology, source release, and target release.
Procedure
-
Verify that SSO redundancy is operating and that the standby control plane is ready.
Example:
switch# show redundancy
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso >>> Stateful Switchover is operating
Communications = Up >>> The active and standby control planes can communicate
Current Software state = ACTIVE
Current Software state = STANDBY HOT >>> The standby is synchronized and ready to assume the active role
BOOT = flash:packages.conf; >>> ISSU requires INSTALL mode
-
The Configured Redundancy Mode and Operating Redundancy Mode values must show sso.
-
The Communications = Up output confirms that the active and standby control planes can communicate.
-
The Current Software state = ACTIVE and Current Software state = STANDBY HOT values confirm that the standby is synchronized and ready to assume the active role.
-
The BOOT = flash:packages.conf; value confirms that the switch is running in INSTALL mode, which is required for ISSU.
-
Confirm that no ISSU operation is already in progress.
Example:
switch# show issu state detail
No ISSU operation is in progress
The output confirms that no previous ISSU operation needs to be completed or cleared before the new upgrade starts.
-
Confirm that the current source image is activated and committed.
Example:
switch# show install summary
Type St Filename/Version
------------------------------------------
IMG C <CURRENT_RELEASE> >>> The source image is activated and committed
Auto abort timer: inactive >>> No earlier uncommitted installation is active
The IMG entry must show state C for <CURRENT_RELEASE>, which means that the source image is activated and committed. The Auto abort timer: inactive output confirms that no earlier uncommitted installation is active.
-
Start the one-step ISSU workflow and commit the target image automatically.
Example:
switch# install add file flash:<MATRIX-APPROVED-IMAGE.bin> activate issu commit
install_add_activate_commit: START
%INSTALL-5-INSTALL_START_INFO:
install_engine: Started install one-shot ISSU >>> The one-step ISSU workflow has started and will commit automatically
--- Starting initial file syncing ---
[1]: Copying flash:<IMAGE.bin> from switch 1 to switch 2
[2]: Finished copying to switch 2 >>> The target image is available on both ISSU participants
--- Starting Add ---
Add: Passed on [1 2] >>> The target image was validated and expanded successfully
STAGE 0: Initial System Level Sanity Check
========================================================
--- Verifying install_issu supported ---
--- Verifying standby is in Standby Hot state ---
--- Verifying booted from valid media ---
--- Verifying AutoBoot mode is enabled ---
Finished Initial System Level Sanity Check >>> The initial ISSU prerequisites passed
STAGE 1: Installing software on Standby
========================================================
install_remote: Passed on [2] >>> The target software was installed on the standby
STAGE 2: Restarting Standby
========================================================
--- Starting standby reload ---
>>> [Standby reload messages omitted]
%HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded >>> Configuration synchronization with the restarted standby succeeded
%RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO) >>> The standby returned to a stable SSO state
STAGE 3: Installing software on Active
========================================================
install_active: Passed on [1] >>> The target software was installed on the active system
STAGE 4: Restarting Active
========================================================
--- Starting active reload --- >>> A switchover occurs. The management session can temporarily disconnect
%IOSXEBOOT-4-ISSU_ONE_SHOT: ISSU finished successfully >>> IOS XE reports successful completion of the ISSU sequence
%INSTALL-5-INSTALL_COMPLETED_INFO:
install_engine: Completed install commit ISSU >>> The target image was committed automatically
SUCCESS: install_add_activate_commit >>> The complete one-step ISSU operation succeeded
-
Verify that redundancy returned to a healthy SSO state after the ISSU operation.
Example:
switch# show redundancy | include Operating|Communications|STANDBY
Operating Redundancy Mode = sso
Communications = Up
Current Software state = STANDBY HOT >>> Redundancy returned to its normal healthy state
-
Confirm that the ISSU operation has fully completed.
Example:
switch# show issu state detail
No ISSU operation is in progress
The output must show No ISSU operation is in progress, confirming that the ISSU operation has fully completed.
-
Confirm that the target image is activated and committed after ISSU.
Example:
switch# show install summary
Type St Filename/Version
-----------------------------------------
IMG C <TARGET_RELEASE> >>> The target image is activated and committed
Auto abort timer: inactive >>> No rollback timer remains active
The IMG entry must show state C for <TARGET_RELEASE>. The Auto abort timer: inactive output confirms that no rollback timer remains active.
The Catalyst 9000 switch runs the target Cisco IOS XE release after a successful ISSU operation. Redundancy is operating in SSO mode, no ISSU operation remains in progress, the target image is activated and committed, and no rollback timer remains active.