Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Arista |
|---|---|
| Operating system | Arista EOS |
| Category | Hardware Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Arista TAC + RMA. |
If you have ever stared at a Arista 7500R3 that just refused to come up, you know the muscle memory: serial console at 9600 8N1, wait for the Aboot# line, hope it actually paints. On Arista EOS the first move is always `show version` and `show environment all`: 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 Arista part-numbers next to the rack because the LED legend differs between hardware generations. The Arista EOS 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 Arista TAC 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
Diagnose and recover from power supply failed on a Arista 7500R3 (DC routing).
The repair
- 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 inventory
show environment all
# Collect for Arista TAC
show tech-support | redirect file:show-tech.log
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 Arista EOS version?
The procedure reflects current Arista EOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.
Should I open a Arista TAC 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 Arista official documentation?
https://www.arista.com/en/support/toi: 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
References
- Arista support portal: https://www.arista.com/en/support
- Arista knowledge base: https://www.arista.com/en/support/toi
- Arista security advisories: https://www.arista.com/en/support/advisories-notices
- Open a case: https://www.arista.com/en/support/customer-support
Reference material, not professional advice. Validate against your specific Arista EOS version and test in a non-production environment before applying.
What changed recently?
Fault diagnosis on a Arista 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.
Why it happens
A few things to confirm so the Arista 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 checks
Before you walk away from a Arista 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.
Escalation guide
For a Arista device, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the Arista 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.
More frequently asked questions
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.
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.
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).
Can I roll this back if something breaks?
Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.
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.
Field notes from real incidents on Arista
When I work on Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. CloudVision Portal alerts are noisy unless you tune them; I disable the defaults and re-enable the ones that map to actual production events. Show tech-support detail is the artifact Arista TAC expects on call one; bundle it with the agent logs before you open the ticket.
EOS-API (eAPI) over HTTPS is the cleanest way to script Arista at scale; do not wrap CLI screen-scraping when eAPI returns JSON. Arista EOS lets you reload a module without reloading the chassis on most platforms, I use that capability more than people realise.
Tools I actually reach for
For Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix on Arista the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with packet capture on the ingress interface (TAC will ask for it) because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show interfaces counters errors, show running-config | include <feature>, show tech-support (capture for TAC), and finally to show logging last 200 only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Arista units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.
Verification I run before I close the ticket
Before I mark Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix resolved on a Arista unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.
show ip route <prefix> # confirm best path post-changeIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show spanning-tree summary # confirm topology stabilityIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show logging | include %LINK|%LINEPROTO|%BGP|%OSPFIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show interfaces <int> | include errors|drops|CRCIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show bgp summary # confirm session state after route changesOnly when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.
Where I check first when the docs disagree
When two sources contradict each other on a Arista detail, the disambiguation order I lean on is stable across products and across years. github.com/aristanetworks for open-source tooling like Ansible roles is where I start for the ground-truth view. eos.arista.com for the official software documentation is where I start for the ground-truth view. Arista TAC knowledge base is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix is rarely worth the time it saved.
Pitfalls I have walked into on this exact path
The shortcuts that look smart on Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Arista unit, not things I read about. Show tech-support detail is the artifact Arista TAC expects on call one; bundle it with the agent logs before you open the ticket. Arista EOS lets you reload a module without reloading the chassis on most platforms. I use that capability more than people realise. CloudVision Portal alerts are noisy unless you tune them; I disable the defaults and re-enable the ones that map to actual production events. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.
What I tell the next on-call
When I hand Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Arista - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.
I also add a one-line note on the cost of getting this wrong. For Arista 7500R3 (DC routing) power supply failed: Diagnose & Fix on a Arista unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.
Related fixes
Related guides worth a look while you sort this one out:
- Arista 7280R3 (routing role) power supply failed: Diagnose & Fix
- Arista 7500R3 (DC routing) fan tray failed: Diagnose & Fix
- Arista 7500R3 (DC routing): How to rollback to the previous image after a failed upgrade
- Arista 7010T power supply failed: Diagnose & Fix
- Arista 7050X3 power supply failed: Diagnose & Fix
- Arista 7060X4 power supply failed: Diagnose & Fix
People also ask
Will this work on my specific Arista EOS version?
The procedure reflects current Arista EOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (`?` or tab-completion) to verify.
Should I open a Arista TAC 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 Arista official documentation?
https://www.arista.com/en/support/toi: 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.