Cisco ASA firewall partial boot then reload loop: Diagnose & Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

What this guide covers

Device gets partway through boot, then resets, usually corrupt image or hardware fault.

Resolve

1. Capture the boot console output to a file: this is the single most useful diagnostic.
2. Verify image integrity: verify /md5 bootflash:<image-name> matches Cisco's published MD5.
3. If image MD5 is wrong, re-download from cisco.com and copy back.
4. If the boot output references a hardware error (memory test fail, FPGA fail), the device is dying, open RMA.
5. Try booting an older known-good image stored in flash as a fallback.
6. Run an extended POST: test memory full at ROMmon (varies per platform).

CLI commands you may need

verify /md5 bootflash:cat9k_iosxe.17.09.04a.SPA.bin
# Compare against the MD5 on the Cisco download page.

When to RMA

• Repeated failure after re-seat / power-cycle
• Visual evidence of burn, scorching, or physical damage
• POST or memory diagnostic failure
• Hardware-related crashinfo with no software workaround

What to capture before calling TAC

• Device serial number (show inventory)
• IOS-XE / ASA version (show version)
• Full show tech-support if reachable
• Photos of any physical damage
• Console log of boot or crash

Frequently asked questions

Will this work on my exact IOS-XE / ASA version?

The procedure reflects current IOS-XE 17.x and ASA 9.20 behaviour. Older trains (15.x, 9.16 ASA) may need minor syntax adjustments. use ? in the CLI.

Should I open a TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your SmartNet is active first.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides

• All Cisco fix guides → /cisco/
• Cisco IOS error messages → /cisco/section/ios_error_messages.html
• Cisco troubleshooting by symptom → /cisco/section/troubleshoot_symptoms.html

References

• Cisco System Message Guide for IOS-XE / IOS
• Cisco Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/
• Cisco Smart Software Manager: https://software.cisco.com
• Cisco TAC: https://mycase.cloudapps.cisco.com/case

Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a Cisco device goes faster when you map the symptom to a recent change:

• Did firmware update in the last 7 days?
• Did the network (router, ISP, VPN) change?
• Was the device moved physically?
• Did paired devices (phone, hub, app) update?
• Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Isolate

A few things to confirm so the Cisco device fix goes cleanly:

• Latest firmware downloaded if you're going to update.
• Warranty + support contract status checked: opening sealed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time, rushing causes regressions.

Validate

Before you walk away from a Cisco device fix, run through:

1. Reproduce the original trigger. does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

When to call Cisco support instead

Escalate if:

• The same symptom returns within 24 hours of a clean fix.
• You see physical damage (burn marks, swollen battery, cracked PCB).
• The device is in warranty and a hardware replacement is the cheaper outcome.
• Repair requires specialised tools you don't own (alignment jigs, calibration software).
• Following the official path keeps the warranty intact, which matters more than the time spent.

More frequently asked questions

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Will this void my warranty?

Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.

Should I update firmware first or last?

Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Field notes from real incidents on Hardware Failure

When I work on Cisco ASA firewall partial boot then reload loop: Diagnose & Fix the rhythm I lean on is the one I have built over years of these tickets. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide. Most catalyst stack issues I have triaged were power-budget related, not software: the show power detail output answers it in 5 seconds. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment.

Tools I actually reach for

For Cisco ASA firewall partial boot then reload loop: Diagnose & Fix on Hardware Failure the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with ping vrf <vrf> <target> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to traceroute vrf <vrf> <target>, show tech-support (capture for TAC), show running-config | include <feature>, and finally to show logging last 200 only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Hardware Failure units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark Cisco ASA firewall partial boot then reload loop: Diagnose & Fix resolved on a Hardware Failure unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

show interfaces <int> | include errors|drops|CRC

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show ip route <prefix>  # confirm best path post-change

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show bgp summary  # confirm session state after route changes

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a Hardware Failure detail, the disambiguation order I lean on is stable across products and across years. cisco.com/c/en/us/support, official command references is where I start for the ground-truth view. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on Cisco ASA firewall partial boot then reload loop: Diagnose & Fix is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco ASA firewall partial boot then reload loop: Diagnose & Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Hardware Failure unit, not things I read about. Most catalyst stack issues I have triaged were power-budget related, not software. the show power detail output answers it in 5 seconds. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand Cisco ASA firewall partial boot then reload loop: Diagnose & Fix off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Hardware Failure - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For Cisco ASA firewall partial boot then reload loop: Diagnose & Fix on a Hardware Failure unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related fixes

Related guides worth a look while you sort this one out:

• Cisco ASR router partial boot then reload loop: Diagnose & Fix
• Cisco Catalyst 8000 router partial boot then reload loop: Diagnose & Fix
• Cisco Catalyst 9100 AP partial boot then reload loop: Diagnose & Fix
• Cisco Catalyst switch partial boot then reload loop: Diagnose & Fix
• Cisco Firepower NGFW partial boot then reload loop: Diagnose & Fix
• Cisco ISR router partial boot then reload loop: Diagnose & Fix