HowToFixMe
Upgrade Failure

Cisco ASR 1000: How to verify image integrity with md5sum

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

⚡ At a glance
CategoryUpgrade Failure
SubjectCisco ASR 1000
Skill levelIntermediate to advanced (CCNA / CCNP background recommended)
DIY-able?Mostly yes with CLI access; some scenarios need TAC + RMA.

What this guide covers

Real-world context. Cost envelope: ~Rs 0 INR under SmartNet, otherwise ~Rs 5,000 to Rs 1,50,000 INR for parts (around $60 to $1,800 USD). Time at the keyboard: ~20 to 60 minutes triage. Time end-to-end including verification: ~1 to 4 hours including failback. Have the device serial, the IOS or NX-OS image, and console access staged before the first command so you do not stall on missing inputs.

Confirm the image isn't corrupt before activating.

The repair

  1. Copy the image to bootflash:.
  2. Run verify /md5 bootflash:<image> on the device.
  3. Compare against the published MD5 on cisco.com for that exact release.
  4. If mismatched: image is corrupt: re-download.
  5. Repeat verify until the MD5 matches.

CLI commands

copy tftp:cat9k_iosxe.17.09.04a.SPA.bin bootflash:
verify /md5 bootflash:cat9k_iosxe.17.09.04a.SPA.bin
# Expected: matches Cisco's published MD5 hash

Recovery options

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.

References

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

What you'll see

When this symptom shows up on a Cisco device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Why it happens

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

Verification checks

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.

Escalation guide

For a Cisco device, the right escalation depends on impact:

More frequently asked questions

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

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.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

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.

Field notes from real incidents on Upgrade Failure

When I work on Cisco ASR 1000: How to verify image integrity with md5sum the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. 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. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide.

Tools I actually reach for

For Cisco ASR 1000: How to verify image integrity with md5sum on Upgrade Failure the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with packet capture on the ingress interface (TAC will ask for it) because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show interfaces counters errors, show logging last 200, and finally to show platform hardware capacity only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Upgrade 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 ASR 1000: How to verify image integrity with md5sum resolved on a Upgrade 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 spanning-tree summary  # confirm topology stability

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

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

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 Upgrade Failure detail, the disambiguation order I lean on is stable across products and across years. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. developer.cisco.com for NSO / model-driven APIs is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. cisco.com/c/en/us/support: official command references 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 ASR 1000: How to verify image integrity with md5sum is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco ASR 1000: How to verify image integrity with md5sum have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Upgrade Failure unit, not things I read about. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. Most catalyst stack issues I have triaged were power-budget related, not software. the show power detail output answers it in 5 seconds. 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 ASR 1000: How to verify image integrity with md5sum off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Upgrade 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 ASR 1000: How to verify image integrity with md5sum on a Upgrade 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 guides worth a look while you sort this one out:

People also ask

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.