Upgrade Paths

Zscaler Cloud Firewall: Upgrade Path to the next major release

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

An upgrade on Zscaler Cloud Firewall is really three jobs: stage the image, verify integrity, activate. Skipping verify is how you end up with a half-bricked unit at 2am, I have done it exactly once and learned for life.

Zscaler Cloud (ZIA / ZPA / ZDX) provides clear pre- and post-checks. `Admin Portal → Activation` before and after is the bare minimum; ideally also `Client Connector → Help → Export Logs` so Zscaler Support has a clean before/after diff.

The procedure below assumes you can take a maintenance window. If you cannot, ISSU / hitless options exist on some platforms but vary by code train. check Zscaler Cloud (ZIA / ZPA / ZDX) release notes first.

What this guide covers

Upgrade procedure for Zscaler Cloud Firewall to the next major release (Zscaler Cloud (ZIA / ZPA / ZDX)).

Notes specific to this combination

Verify the supported upgrade path in the Zscaler release notes before proceeding. Some Zscaler Cloud (ZIA / ZPA / ZDX) releases require an intermediate hop; some support direct upgrade.

Step-by-step

Verify current version: Admin Portal → Activation.
Read the release notes for supported upgrade paths.
Confirm minimum RAM / disk for the target release.
Download target image; verify checksum.
Schedule maintenance window.
Back up running configuration.
Copy image to local flash.
Run Cloud-managed; clients (Client Connector / App Connector) update via the cloud.
Reboot: Not applicable, Zscaler is cloud-managed.
Verify; Activate (Admin Portal upper-right) if healthy.

CLI / commands

Admin Portal → Activation
Admin Portal → Administration → Service Status
Cloud-managed; clients (Client Connector / App Connector) update via the cloud
Activate (Admin Portal upper-right)

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.

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.