Hardware Failure

SonicWall TZ470 power supply failed: Diagnose & Fix

Q: Where can I find the SonicWall official documentation?

https://www.sonicwall.com/support/knowledge-base/ — 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	SonicWall
Operating system	SonicOS
Category	Hardware Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need SonicWall Support + RMA.

A SonicWall platform behaving badly is usually one of three things: a thermal/PSU issue caught by `show diagnostic`, a transceiver problem caught by `show interface X0`, or a boot-loader hang you only see on the console. SonicOS surfaces all three differently from competitors, so the diagnostic order matters.

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

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

What this guide covers

Diagnose and recover from power supply failed on a SonicWall TZ470.

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 (CLI)
show status
show diagnostic

# Collect for SonicWall Support
show tech-support-report

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 SonicOS version?

The procedure reflects current SonicOS behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.

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

https://www.sonicwall.com/support/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.

All SonicWall fix guides → /sonicwall/
All vendor guides → /vendors/

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

References

SonicWall support portal: https://www.sonicwall.com/support
SonicWall knowledge base: https://www.sonicwall.com/support/knowledge-base/
SonicWall security advisories: https://psirt.global.sonicwall.com
Open a case: https://www.mysonicwall.com

Reference material, not professional advice. Validate against your specific SonicOS version and test in a non-production environment before applying.

Why this matters for your day-to-day

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

Before you start

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

Quick verification

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