Hardware Failure

ZTE ZXR10 8900E stack member missing: Diagnose & Fix

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

⚡ At a glance
VendorZTE
Operating systemZXR10 / ZXROS
CategoryHardware Failure
Skill levelIntermediate to advanced
DIY-able?Yes with CLI access; some scenarios need ZTE Customer Support + RMA.

Treat this like a flight checklist. `show version` and `show environment` on ZXR10 / ZXROS returns the data you need for a ZTE ZTE Customer Support case. if you have that saved before the box dies completely, your support call is 20 minutes shorter.

I have seen ZXR10 5950 units that looked dead at the LED panel but were actually fine, the front panel had failed, not the data plane. Always verify with CLI before declaring time of death.

What follows is the recovery playbook, not the marketing version. Some steps assume a spare unit or a console cable; if you do not have them, the diagnostic section is still useful for the ZTE Customer Support case.

What this guide covers

Diagnose and recover from stack member missing on a ZTE ZXR10 8900E.

Step-by-step

  1. Run the stack / chassis status command to see member states.
  2. Inspect the stack cables: re-seat both ends.
  3. Try replacing one stack cable at a time to identify a bad cable.
  4. Power-cycle the affected member if cables are good.
  5. 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

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 worth a look while you sort this one out:

References


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:

The answer narrows the root cause to a manageable subset.

Safety + preconditions

Before any work on a ZTE device:

How to confirm it's actually fixed

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

Escalation guide

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

More frequently asked questions

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.

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.

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).

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.