Hardware Failure

Extreme Networks X590 stack member missing: Diagnose & Fix

Q: Where can I find the Extreme Networks official documentation?

https://extremeportal.force.com/ExtrArticleLanding — 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	Extreme Networks
Operating system	EXOS / Switch Engine / VOSS
Category	Hardware Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Extreme GTAC + RMA.

A Extreme Networks platform behaving badly is usually one of three things: a thermal/PSU issue caught by `show power`, a transceiver problem caught by `show ports 1 description`, or a boot-loader hang you only see on the console. EXOS / Switch Engine / VOSS surfaces all three differently from competitors, so the diagnostic order matters.

I will be honest. on the X590 family I have seen at least one false-positive from the on-box monitoring per quarter. Always cross-check what `show version` and `show power` reports against the physical front-panel and a smell test of the chassis.

If this is your first Extreme Networks hardware issue, the good news is that Extreme GTAC is competent and the part-replacement RMA cycle is usually under a week for a covered unit.

What this guide covers

Real-world context. Last time I walked through this on a real machine, the budget shook out to ~Rs 0 INR under Extreme support, otherwise ~Rs 5,000 to Rs 80,000 INR for parts (around $60 to $960 USD). Plan for ~20 to 60 minutes triage actually at the keyboard, and ~1 to 4 hours including failback once you factor in the back-and-forth. Keep the switch serial, an EXOS config backup, and console access within arm’s reach before you start, stopping mid-step to hunt for them is how a 30-minute job turns into an afternoon.

Diagnose and recover from stack member missing on a Extreme Networks X590.

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 slot
show power

# Collect for Extreme GTAC
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 EXOS / Switch Engine / VOSS version?

The procedure reflects current EXOS / Switch Engine / VOSS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Extreme GTAC 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 Extreme Networks official documentation?

https://extremeportal.force.com/ExtrArticleLanding. 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 Extreme Networks fix guides → /extreme/
All vendor guides → /vendors/

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

References

Extreme Networks support portal: https://www.extremenetworks.com/support/
Extreme Networks knowledge base: https://extremeportal.force.com/ExtrArticleLanding
Extreme Networks security advisories: https://www.extremenetworks.com/support/policies/product-security
Open a case: https://extr.co/3ZxQDt9

Reference material, not professional advice. Validate against your specific EXOS / Switch Engine / VOSS version and test in a non-production environment before applying.

Why this matters for your day-to-day

A Extreme 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 Extreme 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 Extreme 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.

When to call Extreme 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.