ZTE ZXR10 9900X smoke smell or burned PCB: Diagnose & Fix
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | ZTE |
|---|---|
| Operating system | ZXR10 / ZXROS |
| Category | Hardware Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need ZTE Customer Support + RMA. |
A ZTE platform behaving badly is usually one of three things: a thermal/PSU issue caught by `show environment`, a transceiver problem caught by `show interface gei_1/1/1`, or a boot-loader hang you only see on the console. ZXR10 / ZXROS surfaces all three differently from competitors, so the diagnostic order matters.
I will be honest, on the ZXR10 5950 family I have seen at least one false-positive from the on-box monitoring per quarter. Always cross-check what `show version` and `show environment` reports against the physical front-panel and a smell test of the chassis.
If this is your first ZTE hardware issue, the good news is that ZTE Customer Support is competent and the part-replacement RMA cycle is usually under a week for a covered unit.
What this guide covers
Diagnose and recover from smoke smell or burned PCB on a ZTE ZXR10 9900X.
Step-by-step
- STOP. Power off the device at the wall before touching it.
- Open the chassis and identify which board / module is the source of the smell.
- Photograph the visible damage (scorched capacitors, blackened ICs).
- Note the device serial number and exact model for the support case.
- Do not power back on: burned components fail closed and can damage adjacent boards.
- Open a ZTE Customer Support case with the photos and serial.
- RMA the affected component (line card, supervisor, PSU) or the full chassis if the backplane is damaged.
CLI / commands
# Verify hardware state
show version
show device
show environment
# Collect for ZTE Customer Support
show tech-support
When to RMA
- Repeated failure after re-seat and power-cycle
- Visible burn, scorching, or physical damage
- POST or memory diagnostic failure
- Hardware crashinfo without a software workaround
Frequently asked questions
Will this work on my specific ZXR10 / ZXROS version?
The procedure reflects current ZXR10 / ZXROS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.
Should I open a ZTE Customer Support case immediately?
Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.
Where can I find the ZTE official documentation?
https://support.zte.com.cn. 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
Related fixes
Related guides worth a look while you sort this one out:
- ZTE ZXR10 5950 smoke smell or burned PCB: Diagnose & Fix
- ZTE ZXR10 5960 smoke smell or burned PCB: Diagnose & Fix
- ZTE ZXR10 8900E smoke smell or burned PCB: Diagnose & Fix
- ZTE ZXR10 M6000 smoke smell or burned PCB: Diagnose & Fix
- ZTE ZXR10 T8000 smoke smell or burned PCB: Diagnose & Fix
- ZTE ZXR10 W821 smoke smell or burned PCB: Diagnose & Fix
References
- ZTE support portal: https://support.zte.com.cn
- ZTE knowledge base: https://support.zte.com.cn
- ZTE security advisories: https://support.zte.com.cn/support/news/AnnoucementOverviewLatest.aspx
- Open a case: https://support.zte.com.cn
Reference material, not professional advice. Validate against your specific ZXR10 / ZXROS version and test in a non-production environment before applying.
What changed recently?
Fault diagnosis on a ZTE 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.
Safety + preconditions
Before any work on a ZTE device:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
How to confirm it's actually fixed
On a ZTE 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 ZTE device, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the ZTE 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
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.
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.
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.