Hardware Failure

Zscaler ZDX (Digital Experience) fan tray failed: Diagnose & Fix

Q: Where can I find the Zscaler official documentation?

https://help.zscaler.com — 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	Zscaler
Operating system	Zscaler Cloud (ZIA / ZPA / ZDX)
Category	Hardware Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Zscaler Support + RMA.

Hardware-class faults on Zscaler kit fall into a tidy little matrix once you have seen a few. Zscaler Cloud (ZIA / ZPA / ZDX) gives you the building blocks via `Admin Portal → Activation` and `trust.zscaler.com cloud status`; the rest is pattern matching. The ZDX (Digital Experience) platform is one of the more common offenders only because the install base is large.

Do not skip the visible-and-audible inspection. Burnt-PCB smell and fan-tray rattle are diagnostic signals that no command will ever surface. I have caught more dying PSUs by ear than by `trust.zscaler.com cloud status`.

If the chassis is dark and the console is silent, jump straight to the PSU/cable substitution path before opening a Zscaler Support ticket, it eliminates the most common cause in under five minutes.

What this guide covers

Diagnose and recover from fan tray failed on a Zscaler ZDX (Digital Experience).

Step-by-step

Identify which fan failed via the environmental status command.
Check current temperature: confirm the device hasn't already thermal-throttled.
Note the fan part number.
Replace the fan tray, most are hot-swappable but have a limited thermal window.
After replacement, confirm all fans show OK.

CLI / commands

# Verify hardware state
Admin Portal → Activation
Admin Portal → Administration → Service Status
trust.zscaler.com cloud status

# Collect for Zscaler Support
Client Connector → Help → Export Logs

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 Zscaler Cloud (ZIA / ZPA / ZDX) version?

The procedure reflects current Zscaler Cloud (ZIA / ZPA / ZDX) behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.

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

https://help.zscaler.com, 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 Zscaler fix guides → /zscaler/
All vendor guides → /vendors/

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

References

Zscaler support portal: https://help.zscaler.com
Zscaler knowledge base: https://help.zscaler.com
Zscaler security advisories: https://trust.zscaler.com
Open a case: https://help.zscaler.com/submit-ticket

Reference material, not professional advice. Validate against your specific Zscaler Cloud (ZIA / ZPA / ZDX) version and test in a non-production environment before applying.

Common patterns we see

When this symptom shows up on a Zscaler device, three patterns repeat:

1. Recent firmware update changed behavior: the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger, temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear. components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Before you start

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

How to confirm it's actually fixed

On a Zscaler 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.

Escalation guide

For a Zscaler device, the right escalation depends on impact:

Cosmetic / minor: log a ticket via the Zscaler 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.