Cisco Catalyst 3850: Supported Upgrade Paths to FTD 7.4

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

What this guide covers

Upgrade procedure for Catalyst 3850 to FTD 7.4.

Notes specific to this combination

Verify supported upgrade paths in the Cisco Release Notes for the target release.

Full fix path

1. Verify current version: show version.
2. Check target release's release notes for supported upgrade paths.
3. Confirm minimum RAM / disk space for the target release.
4. Download target image + verify MD5.
5. Schedule maintenance window.
6. Back up current configuration.
7. Copy image to bootflash:.
8. install add file bootflash:<image> activate.
9. Verify production traffic; install commit if healthy.

CLI commands

show version
show inventory
show bootvar
show license all
copy tftp:<image> bootflash:
verify /md5 bootflash:<image>
install add file bootflash:<image>
install activate
# verify production traffic
install commit

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.

Quick triage

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.

Confirm it stuck

On a Cisco device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every LED / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

Escalation guide

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

• Cosmetic / minor: log a ticket via the Cisco app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

Will the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

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.

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.

Field notes from real incidents on Upgrade Paths

When I work on Cisco Catalyst 3850: Supported Upgrade Paths to FTD 7.4 the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Most catalyst stack issues I have triaged were power-budget related, not software, the show power detail output answers it in 5 seconds. Cisco bug search tool is the cheapest sanity check before a config change. search the symptom, sort by affected releases, decide.

Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot.

Tools I actually reach for

For Cisco Catalyst 3850: Supported Upgrade Paths to FTD 7.4 on Upgrade Paths 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 platform hardware capacity, show tech-support (capture for TAC), show interfaces counters errors, ping vrf <vrf> <target>, and finally to traceroute vrf <vrf> <target> 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 Paths 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 Catalyst 3850: Supported Upgrade Paths to FTD 7.4 resolved on a Upgrade Paths 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 logging | include %LINK|%LINEPROTO|%BGP|%OSPF

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 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 interfaces <int> | include errors|drops|CRC

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 Paths detail, the disambiguation order I lean on is stable across products and across years. 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. 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. 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 Catalyst 3850: Supported Upgrade Paths to FTD 7.4 is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco Catalyst 3850: Supported Upgrade Paths to FTD 7.4 have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Upgrade Paths unit, not things I read about. 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. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. 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 Catalyst 3850: Supported Upgrade Paths to FTD 7.4 off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Upgrade Paths - 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 Catalyst 3850: Supported Upgrade Paths to FTD 7.4 on a Upgrade Paths 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 Catalyst 3850: How to do an emergency tftpdnld from ROMmon
• How to upgrade IOS-XE image on Cisco Catalyst 3850
• Cisco Catalyst 3850: How to perform in-service software upgrade (ISSU)
• Cisco Catalyst 3850: How to recover from a corrupted image during upgrade
• Cisco Catalyst 3850: How to rollback to the previous image after a failed upgrade
• Cisco Catalyst 3850: Supported Upgrade Paths to ASA 9.20