Upgrade Paths

Palo Alto Networks PA-440: 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.

An upgrade on Palo Alto Networks PA-440 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

Upgrade procedure for Palo Alto Networks PA-440 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.

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.

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.

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.

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.