Upgrade Failure

Palo Alto Networks PA-220: How to perform a controlled upgrade with rollback safety net

Q: Where can I find the Palo Alto Networks official documentation?

https://knowledgebase.paloaltonetworks.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	Palo Alto Networks
Operating system	PAN-OS
Category	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Palo Alto TAC + RMA.

Upgrade work on a Palo Alto Networks fleet is mostly about discipline. PAN-OS gives you the commands; the failure mode is almost always operator error: wrong image for the platform, integrity not checked, no rollback plan. The PA-220 family is no exception.

I always do a one-box pilot before a fleet roll. request system software install version 11.1.2 on a single representative unit, then 24 hours of soak, then the rest of the fleet in waves. Skipping the soak has bitten me twice.

Palo Alto TAC will want the exact build string and the upgrade method (CLI vs controller-driven) on every case, so keep that recorded for the change ticket.

What this guide covers

Perform a controlled upgrade with rollback safety net on a Palo Alto Networks PA-220 (PAN-OS).

Step-by-step

Back up the current running config and image.
Download the new image and verify checksum.
Activate the new image; do NOT commit if the platform supports staged commit.
Verify production traffic on the new image.
Commit if healthy, or rollback within the safe window if not.

CLI / commands

# Boot recovery prompt: Maint mode

# Verify image
show system info

# Upgrade
request system software install version 11.1.2

# Save / commit
commit

# Rollback
load config from running-config-prev.xml

Recovery options

Boot loader recovery (Maint mode)
Rollback to the previous image with load config from running-config-prev.xml
Force failover to a known-good standby (HA platforms)

Frequently asked questions

Will this work on my specific PAN-OS version?

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

Should I open a Palo Alto 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 Palo Alto Networks official documentation?

https://knowledgebase.paloaltonetworks.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 Palo Alto Networks fix guides → /paloalto/
All vendor guides → /vendors/

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

References

Palo Alto Networks support portal: https://support.paloaltonetworks.com
Palo Alto Networks knowledge base: https://knowledgebase.paloaltonetworks.com
Palo Alto Networks security advisories: https://security.paloaltonetworks.com
Open a case: https://support.paloaltonetworks.com/Support/Index

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

Common patterns we see

When this symptom shows up on a Palo 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 Palo 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 Palo 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 Palo 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.