ZTE ZXR10 5960 power supply failed: 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 power supply failed on a ZTE ZXR10 5960.
Step-by-step
- Confirm which PSU failed.
- Verify the remaining PSU has enough capacity for the device + line cards + PoE budget.
- Note the failed PSU's part number.
- Replace during a maintenance window: most enterprise PSUs are hot-swappable.
- After replacement, confirm both PSUs show OK.
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 power supply failed: Diagnose & Fix
- ZTE ZXR10 8900E power supply failed: Diagnose & Fix
- ZTE ZXR10 9900X power supply failed: Diagnose & Fix
- ZTE ZXR10 M6000 power supply failed: Diagnose & Fix
- ZTE ZXR10 T8000 power supply failed: Diagnose & Fix
- ZTE ZXR10 W821 power supply failed: 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.
Why this matters for your day-to-day
A ZTE device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.
Before you start
A few things to confirm so the ZTE 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.
Quick verification
Before you walk away from a ZTE 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 ZTE 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.
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.
Are there safer alternatives for non-technical users?
Yes. the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
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).