Upgrade Paths

Palo Alto Networks PA-220: Upgrade Path to latest LTS / GA

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

I have run more Palo Alto Networks upgrades than I can count and the only ones that hurt are the ones where I skipped image-integrity verification. PAN-OS either ships a `verify` step or expects you to checksum the file before request system software install version 11.1.2.

On the PA-220 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 PAN-OS is well-trodden, but only if you saved running-config before starting. Do that now, before anything else.

What this guide covers

Upgrade procedure for Palo Alto Networks PA-220 to latest LTS / GA (PAN-OS).

Notes specific to this combination

Verify the supported upgrade path in the Palo Alto Networks release notes before proceeding. Some PAN-OS releases require an intermediate hop; some support direct upgrade.

Step-by-step

Verify current version: show system info.
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 request system software install version 11.1.2.
Reboot: request restart system.
Verify; commit if healthy.

CLI / commands

show system info
show system state filter sys.s1.p*
request system software install version 11.1.2
commit

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.

Verification checklist

After applying the fix on your Palo device, confirm:

The original symptom is no longer reproducible.
Related features (status LEDs, app sync, paired accessories) still work.
The device responds to a soft reboot without the fault returning.
Any error codes that were on display have cleared.
Documentation (your service log, the brand companion app) reflects the change.

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.