Outlines the criteria for stopping self-recovery and opening a Cisco Support case for repeated ROMMON recovery, boot failures, synchronization issues, install inconsistencies, failed updates, unexpected reloads, or persistent recovery and rollback problems.
Stop self-recovery and open a Cisco Support case when any of these conditions applies:
-
The device repeatedly returns to ROMMON or no validated boot image or provisioning file is available.
-
A stack member or supervisor remains missing, version mismatch, or unable to synchronize after storage and image checks.
-
ISSU or xFSU remains active or stalled even after performing the abort procedure.
-
Install state remains inconsistent after the supported commit, abort, rollback, or inactive cleanup proedure.
-
A bootloader, ROMMON, CPLD, or FPGA update fails or is interrupted.
-
An unexpected reload, process crash, watchdog, low-memory event, or forwarding failure occurs.
-
The suggested recovery process requires clearing install state, flash formatting, emergency-install, service internal, or manual changes to package file.
-
The correct rollback point or required package files are absent.
-
The same validated operation fails again after the underlying cause was corrected.