Palo Alto Networks PA-220: Upgrade Path to latest hardening patch
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| 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. |
On Palo Alto Networks kit the upgrade ritual matters more than the speed. `show system info` first, `tftp export tech-support to 10.10.1.100` second, then the actual `request system software install version 11.1.2`: that order on PAN-OS saves the most support-case time when something goes wrong on the PA-220 unit.
Integrity verification is non-negotiable. Vendor mirrors get corrupted, internal staging servers serve stale files, and the checksum step on PAN-OS is the only thing standing between you and a chassis that boots to a recovery prompt.
What follows is the safe-rollback variant. If you need an in-place upgrade with zero rollback path, this guide is not it, and frankly that is not a thing you should be doing on production gear.
What this guide covers
Upgrade procedure for Palo Alto Networks PA-220 to latest hardening patch (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;
commitif 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.
Related guides
- All Palo Alto Networks fix guides → /paloalto/
- All vendor guides → /vendors/
Related fixes
Related guides worth a look while you sort this one out:
- Palo Alto Networks PA-440: Upgrade Path to latest hardening patch
- Palo Alto Networks PA-450: Upgrade Path to latest hardening patch
- Palo Alto Networks PA-460: Upgrade Path to latest hardening patch
- Palo Alto Networks PA-220: Upgrade Path to latest LTS / GA
- Palo Alto Networks PA-220: How to do an emergency image reload from the boot loader
- Palo Alto Networks PA-220: How to perform a controlled upgrade with rollback safety net
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.
Before you start
A few things to confirm so the Palo 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.
Quick verification
Before you walk away from a Palo device fix, run through:
1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.
Escalation guide
For a Palo device, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the Palo 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.
More frequently asked questions
Why is this happening on a brand-new unit?
Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.
What if the fix returns after a reboot?
Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).
Can I roll this back if something breaks?
Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.
Does this affect other devices on my network?
Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.