Upgrade Failure

Zscaler ZIA (SWG/CASB/FWaaS): How to do an emergency image reload from the boot loader

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	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Zscaler Support + RMA.

I have run more Zscaler upgrades than I can count and the only ones that hurt are the ones where I skipped image-integrity verification. Zscaler Cloud (ZIA / ZPA / ZDX) either ships a `verify` step or expects you to checksum the file before Cloud-managed; clients (Client Connector / App Connector) update via the cloud.

On the ZIA (SWG/CASB/FWaaS) platform the activation phase is where you lose data-plane connectivity. Plan the change window around that window, not the full upgrade duration.

If something goes wrong, the rollback path on Zscaler Cloud (ZIA / ZPA / ZDX) is well-trodden: but only if you saved running-config before starting. Do that now, before anything else.

What this guide covers

Do an emergency image reload from the boot loader on a Zscaler ZIA (SWG/CASB/FWaaS) (Zscaler Cloud (ZIA / ZPA / ZDX)).

Step-by-step

At the boot loader, configure IP, gateway, TFTP server.
Download the image.
Set the boot variable to the new image.
Reset to boot.

CLI / commands

# Boot recovery prompt: Client Connector logs / App Connector service

# Verify image
Admin Portal → Activation

# Upgrade
Cloud-managed; clients (Client Connector / App Connector) update via the cloud

# Save / commit
Activate (Admin Portal upper-right)

# Rollback
Admin Portal → Activation → Revert

Recovery options

Boot loader recovery (Client Connector logs / App Connector service)
Rollback to the previous image with Admin Portal → Activation → Revert
Force failover to a known-good standby (HA platforms)

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.

Why this matters for your day-to-day

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

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.

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