Guides you through troubleshooting xFSU issues on Catalyst 9300 series switches, including resolving eligibility failures, analyzing incomplete status, verifying reload-fast events, investigating failed or stalled operations, and understanding the rollback boundary and commit behavior for supported upgrade workflows.
Use this procedure to troubleshoot xFSU issues on Catalyst 9300 series switches, including resolving eligibility failures, analyzing incomplete status, verifying reload-fast events, investigating failed or stalled operations, and understanding the rollback boundary and commit behavior for supported upgrade workflows.
Before you begin
-
Refer the xFSU guidelines mentioned in the Upgrade chapter.
-
Understand the xFSU rollback boundary: The xFSU command includes commit operation. After a successful committed xFSU, returning to an older image is a separate normal install or downgrade operation. Perform the downgrade operation only when the path is supported with normal maintenance impact. The clear xfsu state command clears the recorded last-reload state; it does not restore the previous image. Do not use it while an operation is active or before collecting the diagnostics data.
Procedure
-
Resolve xFSU eligibility failures.
- Review xFSU eligibility failure details.
Example:
switch# show xfsu eligibility
Eligibility Check Status
================== ======
Autoboot Enabled Yes
Install Mode Yes
Spanning Tree Eligible
MacSec Eligible
FAILED: FPGA on switch 1 does not support xFSU.
Please upgrade the FPGA via a normal install.
XFSU Eligibility Summary
==============================
XFSU Eligibility: NOT ELIGIBLE
==============================
Do not start xFSU in this case. This device requires a normal INSTALL-mode upgrade to update the unsupported FPGA.
- Verify graceful-reload client readiness.
Example:
switch# show graceful-reload
Graceful Reload Infra Status: Not running
Client OSPF Status: Up
Client GR_CLIENT_BGP Status: Up
Client LACP_xFSU Status: Up
Client GR_CLIENT_RIB Status: Up
Client GR_CLIENT_FIB Status: Up
Configured graceful-reload clients relevant to the deployment must be Up before xFSU.
On a supported stack, also confirm that full-ring stack, required license, and SSO checks report status as eligible. If SSO is not ready, wait for the standby and stack to become healthy; do not force the operation.
Typical blockers for xFSU eligibility include unsupported FPGA, disabled autoboot, BUNDLE mode, partial stack ring, unsupported spanning-tree condition, MACsec or feature restrictions, or an unsupported topology-protocol combination. Use the exact reason in the output and refer the xFSU guide.
-
Analyse incomplete xFSU status.
- Check an intermediate xFSU status.
Example:
switch# show xfsu status
XFSU PLATFORM Status: Stack converged, waiting for standby reconnect
This can be a normal intermediate state. If it remains unchanged beyond the approved maintenance plan, collect diagnostics and do not start another xFSU.
A completed xFSU platform status looks like this:
switch# show xfsu status
XFSU PLATFORM Status: Data plane update done, Upgrade done in 1590 ms.
- Verify the device reload reason.
Example:
switch# show version | include reason
Last reload reason: Image Install with Reloadfast
switch# show logging | include FAST
%FED_IPC_MSG-5-FAST_RELOAD_COMPLETE: Fast reload operation completed
The reload reason and completion message confirm the reduced-downtime reload path.
- Collect diagnostics data for failed or stalled xFSU.
Example:
switch# show xfsu eligibility
switch# show xfsu status
switch# show graceful-reload
switch# show switch
switch# show install summary
switch# show install log
switch# show version running
switch# show logging
switch# show platform hardware fpga switch 1 | include Version
switch# show inventory
switch# show etherchannel summary
switch# show spanning-tree
switch# dir crashinfo-1:
switch# show tech-support xfsu
Older releases can use reloadfast variants of the status and technical-support commands.