If ISSU fails, it is expected that auto-abort can recover the system back to initial state (older image). However, if this fails as well, manual recovery of the chassis is expected.
Can you check with "show redundancy config-sync failures historic mcl" what is the reason for failure.
for recovery,
clear install state
Have you followed Release Support Matrix,
===================STEP-1=================================
PP3Clrm-9500-S1#show boot system
BOOT variable = bootflash:packages.conf;
MANUAL_BOOT variable = no
BAUD variable = 9600
ENABLE_BREAK variable does not exist
BOOTMODE variable does not exist
IPXE_TIMEOUT variable does not exist
CONFIG_FILE variable =
Standby BOOT variable = bootflash:packages.conf;
Standby MANUAL_BOOT variable = no
Standby BAUD variable = 9600
Standby ENABLE_BREAK variable does not exist
Standby BOOTMODE variable does not exist
Standby IPXE_TIMEOUT variable does not exist
Standby CONFIG_FILE variable =
===================STEP-2=================================
PP3Clrm-9500-S1#show redundancy
Redundant System Information :
------------------------------
Available system uptime = 15 weeks, 1 day, 6 hours, 9 minutes
Switchovers system experienced = 0
Standby failures = 0
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 2
Current Software state = ACTIVE
Uptime in current state = 15 weeks, 1 day, 6 hours, 9 minutes
Image Version = Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.6.5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Wed 25-Jan-23 16:15 by mcpre
BOOT = bootflash:packages.conf;
CONFIG_FILE =
Peer Processor Information :
----------------------------
Standby Location = slot 1
Current Software state = STANDBY HOT
Uptime in current state = 15 weeks, 1 day, 6 hours, 5 minutes
Image Version = Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.6.5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Wed 25-Jan-23 16:15 by mcpre
BOOT = bootflash:packages.conf;
CONFIG_FILE =
===================STEP-3=================================
PP3Clrm-9500-S1#sh issu state detail
Current ISSU Status: Enabled
Previous ISSU Operation: N/A
=======================================================
System Check Status
-------------------------------------------------------
Platform ISSU Support Yes
Standby Online Yes
Autoboot Enabled Yes
SSO Mode Yes
Install Boot Yes
Valid Boot Media Yes
Operational Mode HA-REMOTE
=======================================================
No ISSU operation is in progress
===================STEP-4=================================
PP3Clrm-9500-S1#install add file flash:cat9k_iosxe.17.12.04.SPA.bin activate issu commit
install_add_activate_commit: START Fri Nov 1 23:35:45 KSA 2024
install_add_activate_commit: Adding ISSU
install_add_activate_commit: Checking whether new add is allowed ....
--- Starting initial file syncing ---
[2]: Copying bootflash:cat9k_iosxe.17.12.04.SPA.bin from chassis 2/R0 to chassis 1/R0
![1]: Finished copying to chassis 1/R0
Info: Finished copying bootflash:cat9k_iosxe.17.12.04.SPA.bin to the selected chassis
Finished initial file syncing
--- Starting Add ---
Performing Add on all members
[1] Add package(s) on chassis 1/R0
[1] Finished Add on chassis 1/R0
[2] Add package(s) on chassis 2/R0
[2] Finished Add on chassis 2/R0
Checking status of Add on [1/R0 2/R0]
Add: Passed on [1/R0 2/R0]
Finished Add
install_add_activate_commit: Activating ISSU
NOTE: Going to start Oneshot ISSU install process
STAGE 0: System Level Sanity Check
===================================================
--- Verifying install_issu supported ---
--- Verifying standby is in Standby Hot state ---
--- Verifying booted from the valid media ---
--- Verifying AutoBoot mode is enabled ---
--- Verifying Platform specific ISSU admission criteria ---
-- Verifying Image ISSU Compatibility ---
Finished Initial System Level Sanity Check
STAGE 1: Installing software on Standby
===================================================
--- Starting install_remote ---
![1] install_remote package(s) on chassis 1/R0
WARNING: Found 3175 disjoint TDL objects.
[1] Finished install_remote on chassis 1/R0
install_remote: Passed on [1/R0]
Finished install_remote
STAGE 2: Restarting Standby
===================================================
--- Starting standby reload ---
Finished standby reload
--- Starting wait for Standby to reach terminal redundancy state ---
!Finished wait for Standby to reach terminal redundancy state
STAGE 3: Installing software on Active
===================================================
--- Starting install_active ---
!gzip: initramfs.cpio.gz: decompression OK, trailing garbage ignored
WARNING: Found 3175 disjoint TDL objects.
[2] install_active package(s) on chassis 2/R0
[2] Finished install_active on chassis 2/R0
install_active: Passed on [2/R0]
Finished install_active
/usr/binos/conf/install_issu_activate.sh: line 307: Rtrace_notice: command not found
STAGE 4: Restarting Active (switchover to standby)
===================================================
--- Starting active reload ---
New software will load after reboot process is completed
SUCCESS: install_add_activate_commit Fri Nov 1 23:58:32 2024
********************************************************************
Regards
