Palo Alto Networks PA-220: How to do an emergency image reload from the boot loader
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. |
Every Palo Alto Networks upgrade I have shipped to production was paired with a written rollback. PAN-OS on the PA-220 family makes rollback cheap if you saved the previous image and config: and expensive if you did not.
The request system software install version 11.1.2 command on PAN-OS is straightforward once you have the right artifact staged. The trap is mismatched hardware-to-image, always cross-reference platform IDs from `show system info` against the image name.
I file every upgrade run under a change number and attach the before/after `show system info` and tech-support bundle. Palo Alto TAC appreciates it; future me appreciates it even more.
What this guide covers
Do an emergency image reload from the boot loader on a Palo Alto Networks PA-220 (PAN-OS).
Step-by-step
- At the boot loader, configure IP, gateway, TFTP server.
- Download the image.
- Set the boot variable to the new image.
- Reset to boot.
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 do an emergency image reload from the boot loader
- Palo Alto Networks PA-450: How to do an emergency image reload from the boot loader
- Palo Alto Networks PA-460: How to do an emergency image reload from the boot loader
- Palo Alto Networks PA-220 partial boot then reload loop: Diagnose & Fix
- Palo Alto Networks PA-220 stuck at boot loader prompt: Diagnose & Fix
- Palo Alto Networks PA-220: How to recover from a corrupted image during 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.
What changed recently?
Fault diagnosis on a Palo device goes faster when you map the symptom to a recent change:
- Did firmware update in the last 7 days?
- Did the network (router, ISP, VPN) change?
- Was the device moved physically?
- Did paired devices (phone, hub, app) update?
- Were any accessories swapped in or out?
The answer narrows the root cause to a manageable subset.
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.
More frequently asked questions
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.
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.
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.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.