Ciena 5170 Service Aggregation power supply failed: Diagnose & Fix

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

What this guide covers

Diagnose and recover from power supply failed on a Ciena 5170 Service Aggregation.

Full fix path

1. Confirm which PSU failed.
2. Verify the remaining PSU has enough capacity for the device + line cards + PoE budget.
3. Note the failed PSU's part number.
4. Replace during a maintenance window, most enterprise PSUs are hot-swappable.
5. After replacement, confirm both PSUs show OK.

CLI / commands

# Verify hardware state
software show
chassis show inventory
chassis show fans temperature

# Collect for Ciena TAC
show diagnostics

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 SAOS (Service-Aware OS) / Blue Planet version?

The procedure reflects current SAOS (Service-Aware OS) / Blue Planet behaviour. Older releases may need minor syntax adjustments: use the CLI help (? or tab-completion) to verify.

Should I open a Ciena 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 Ciena official documentation?

https://www.ciena.com/insights/knowledge-base, 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

• All Ciena fix guides → /ciena/
• All vendor guides → /vendors/

References

• Ciena support portal: https://www.ciena.com/services/support/
• Ciena knowledge base: https://www.ciena.com/insights/knowledge-base
• Ciena security advisories: https://www.ciena.com/services/support/security-advisories
• Open a case: https://www.ciena.com/services/support/contact-support

Reference material, not professional advice. Validate against your specific SAOS (Service-Aware OS) / Blue Planet version and test in a non-production environment before applying.

Why this matters for your day-to-day

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

Confirm it stuck

Before you walk away from a Ciena 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.

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

More frequently asked questions

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.

Will the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

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.

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.

Field notes from real incidents on Ciena

When I work on Ciena 5170 Service Aggregation 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. I never push a config change without a rollback timer; commit confirmed on Junos, archive on IOS, or a scripted timeout on EOS. Show tech-support is the artifact TAC will ask for first, capture it before you change anything so the pre-change state is preserved.

Half the BGP weirdness I have triaged was a route-map that someone copied from a template without reading what it actually filtered. Counters lie if you do not clear them; clear counters, reproduce, and read the deltas, not the cumulative numbers.

Tools I actually reach for

For Ciena 5170 Service Aggregation power supply failed: Diagnose & Fix on Ciena the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with show running-config | include <feature> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show logging last 200, show platform hardware capacity, ping vrf <vrf> <target>, and finally to show interfaces counters errors only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Ciena 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 Ciena 5170 Service Aggregation power supply failed: Diagnose & Fix resolved on a Ciena 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 logging | include %LINK|%LINEPROTO|%BGP|%OSPF

If 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 ip route <prefix>  # confirm best path post-change

If 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 changes

Only 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 Ciena detail, the disambiguation order I lean on is stable across products and across years. vendor TAC knowledge base is where I start for the ground-truth view. vendor release notes for the running software version is where I start for the ground-truth view. RFCs for the protocol in question (rfc-editor.org) is where I start for the ground-truth view. vendor official command reference (Cisco DocCD, Arista EOS Central, Juniper TechLibrary, etc.) 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 Ciena 5170 Service Aggregation 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 Ciena 5170 Service Aggregation power supply failed: Diagnose & Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Ciena unit, not things I read about. Counters lie if you do not clear them; clear counters, reproduce, and read the deltas, not the cumulative numbers. Show tech-support is the artifact TAC will ask for first. capture it before you change anything so the pre-change state is preserved. Most spanning-tree storms I have walked into started with a user-side switch that nobody documented; topology audits pay off the day the loop forms. 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 Ciena 5170 Service Aggregation 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 Ciena - 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 Ciena 5170 Service Aggregation power supply failed: Diagnose & Fix on a Ciena 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:

• Ciena 5171 Service Aggregation Service Edge power supply failed: Diagnose & Fix
• Ciena 5170 Service Aggregation fan tray failed: Diagnose & Fix
• Ciena 5170 Service Aggregation: How to rollback to the previous image after a failed upgrade
• Ciena 5170 Service Aggregation all ports dead: Diagnose & Fix
• Ciena 5170 Service Aggregation: How to back up configs nightly to a Git repo
• Ciena 5170 Service Aggregation: How to deploy with a Python script (paramiko / netmiko / native API)