Hardware Failure

ZTE ZXR10 9900X stack member missing: Diagnose & Fix

Q: Where can I find the ZTE official documentation?

https://support.zte.com.cn — search the product family + feature name.

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

⚡ At a glance

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.

Hardware-class faults on ZTE kit fall into a tidy little matrix once you have seen a few. ZXR10 / ZXROS gives you the building blocks via `show version` and `show environment`; the rest is pattern matching. The ZXR10 5950 platform is one of the more common offenders only because the install base is large.

Do not skip the visible-and-audible inspection. Burnt-PCB smell and fan-tray rattle are diagnostic signals that no command will ever surface. I have caught more dying PSUs by ear than by `show environment`.

If the chassis is dark and the console is silent, jump straight to the PSU/cable substitution path before opening a ZTE Customer Support ticket: it eliminates the most common cause in under five minutes.

What this guide covers

Diagnose and recover from stack member missing on a ZTE ZXR10 9900X.

Step-by-step

Run the stack / chassis status command to see member states.
Inspect the stack cables, re-seat both ends.
Try replacing one stack cable at a time to identify a bad cable.
Power-cycle the affected member if cables are good.
If the member still doesn't rejoin, RMA it.

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.

All ZTE fix guides → /zte/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

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.

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.