Hardware Failure

Extreme Networks AP3000 power supply failed: 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.

If you have ever stared at a Extreme Networks AP3000 that just refused to come up, you know the muscle memory: serial console at 9600 8N1, wait for the BootROM> line, hope it actually paints. On EXOS / Switch Engine / VOSS the first move is always `show version` and `show power`, if those return cleanly the box is alive enough to talk to you, which is the difference between a ten-minute fix and an RMA paperwork morning.

I keep a small notebook of Extreme Networks part-numbers next to the rack because the LED legend differs between hardware generations. The EXOS / Switch Engine / VOSS platform tends to tell the truth in `show` output before the front-panel LED catches up, so trust the CLI first.

This guide assumes you have console access and an active Extreme GTAC entitlement. If the device is out of warranty, skip straight to the recovery section. most of the steps still apply, you just lose the RMA option at the end.

What this guide covers

Real-world context. Cost envelope: ~Rs 0 INR under Extreme support, otherwise ~Rs 5,000 to Rs 80,000 INR for parts (around $60 to $960 USD). Time at the keyboard: ~20 to 60 minutes triage. Time end-to-end including verification: ~1 to 4 hours including failback. Have the switch serial, an EXOS config backup, and console access staged before the first command so you do not stall on missing inputs.

Diagnose and recover from power supply failed on a Extreme Networks AP3000.

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

What changed recently?

Fault diagnosis on a Extreme 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.

Before you start

A few things to confirm so the Extreme 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.

Verification checklist

After applying the fix on your Extreme device, confirm:

The original symptom is no longer reproducible.
Related features (status LEDs, app sync, paired accessories) still work.
The device responds to a soft reboot without the fault returning.
Any error codes that were on display have cleared.
Documentation (your service log, the brand companion app) reflects the change.

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.