Palo Alto Networks PA-220: How to verify image integrity before activating
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 Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Palo Alto TAC + RMA. |
An upgrade on Palo Alto Networks PA-220 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.
PAN-OS provides clear pre- and post-checks. `show system info` before and after is the bare minimum; ideally also `tftp export tech-support to 10.10.1.100` so Palo Alto TAC 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 PAN-OS release notes first.
What this guide covers
Verify image integrity before activating on a Palo Alto Networks PA-220 (PAN-OS).
Step-by-step
- Copy the image to local flash.
- Run the vendor checksum / md5 command.
- Compare against the checksum published on the vendor portal.
- If mismatched, the image is corrupt: re-download.
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.
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: How to verify image integrity before activating
- Palo Alto Networks PA-450: How to verify image integrity before activating
- Palo Alto Networks PA-460: How to verify image integrity before activating
- Palo Alto Networks PA-220: How to do an emergency image reload from the boot loader
- Palo Alto Networks PA-220: How to recover from a corrupted image during upgrade
- Palo Alto Networks PA-220: How to rollback to the previous image after a failed upgrade
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.
Why this matters for your day-to-day
A Palo 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 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.
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.
Should I update firmware first or last?
Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.
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.
Will this void my warranty?
Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.