HowToFixMe
Hardware Failure

Cisco Catalyst 9100 AP smoke smell or burned PCB: Diagnose & Fix

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

⚡ At a glance
CategoryHardware Failure
SubjectCisco Catalyst 9100 AP smoke smell or burned PCB
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.

Identify a burned component and recover safely without further damage.

Full fix path

  1. STOP. Power off the device at the wall (not the panel switch) before doing anything else.
  2. Smell test: open the chassis and identify which board / module has the burned smell.
  3. Look for visual evidence: scorched capacitors, blackened ICs, discoloured PCB.
  4. Photograph the damage for the TAC / RMA case.
  5. Do not power back on: burned components fail closed (short) and can damage adjacent boards.
  6. Open a TAC case with the photos and the device serial number.
  7. RMA the affected component (line card, supervisor, PSU), if the chassis itself is the casualty, RMA the full chassis.

CLI commands you may need

# Before power-down (only if device is still up and responsive):
show environment all
show inventory
show tech-support | redirect tftp://10.10.1.100/burned-device.txt

When to RMA

What to capture before calling TAC

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.

Spot the symptom

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.

Safety + preconditions

Before any work on a Cisco device:

Confirm it stuck

After applying the fix on your Cisco device, confirm:

Escalation guide

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

More frequently asked questions

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.

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.

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

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 Hardware Failure

When I work on Cisco Catalyst 9100 AP smoke smell or burned PCB: Diagnose & Fix the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. 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.

Tools I actually reach for

For Cisco Catalyst 9100 AP smoke smell or burned PCB: 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 show interfaces counters errors because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show logging last 200, ping vrf <vrf> <target>, packet capture on the ingress interface (TAC will ask for it), traceroute vrf <vrf> <target>, and finally to show tech-support (capture for TAC) 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 Catalyst 9100 AP smoke smell or burned PCB: 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 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

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/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. 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 9100 AP smoke smell or burned PCB: 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 Catalyst 9100 AP smoke smell or burned PCB: 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. 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. 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 9100 AP smoke smell or burned PCB: 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 Catalyst 9100 AP smoke smell or burned PCB: 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 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.