Upgrade Panorama with an Internet Connection

Verify that the updates you plan to install are appropriate for your Panorama deployment.
Palo Alto Networks highly recommends that Panorama, Log Collectors, and all managed firewalls run the same content release version.
Refer to the Release Notes for the minimum content release version required for a Panorama software release. If you intend to upgrade Log Collectors and firewalls to a particular release, you must first upgrade Panorama to that (or a later) release.
For a Panorama virtual appliance that runs on a hypervisor, ensure that the instance meets the Setup Prerequisites for the Panorama Virtual Appliance.
Determine the Upgrade Path to PAN-OS 10.1.
You cannot skip the installation of any feature release versions in the path from the currently running PAN-OS version to PAN-OS 10.1
Review PAN-OS Upgrade Checklist, the known issues and changes to default behavior in the Release Notes and Upgrade/Downgrade Considerations for each release through which you pass as part of your upgrade path.
Save a backup of the current Panorama configuration file that you can use to restore the configuration if you have problems with the upgrade.
Although Panorama automatically creates a backup of the configuration, best practice is to create and externally store a backup before you upgrade.
Log in to the Panorama web interface.
Save named Panorama configuration snapshot
(
Panorama
Setup
Operations
), enter a
Name
for the configuration, and click
OK
.
Export named Panorama configuration snapshot
, select the
Name
of the configuration you just saved, click
OK
, and save the exported file to a location that is external to Panorama.
(
Best Practices
) If you are leveraging Cortex Data Lake (CDL), install the Panorama device certificate.
Panorama automatically switches to using the device certificate for authentication with CDL ingestion and query endpoints on upgrade to PAN-OS 10.1.
If you do not install the device certificate prior to upgrade to PAN-OS 10.1, Panorama continues to use the existing logging service certificate for authentication.
Install the latest content updates.
If Panorama is not running the minimum content versions required for the Panorama release to which you intend to upgrade, you must update content versions to the minimum (or later) versions before you install the software updates. Refer to Release Notes for minimum content release version for a Panorama release.
Palo Alto Networks® highly recommends that Panorama, Log Collectors, and all managed firewalls run the same content release version. Additionally, we recommend that you schedule automatic, recurring updates so that you are always running the latest content versions (refer to 10).
Select
Panorama
Dynamic Updates
and
Check Now
for the latest updates. If the value in the Action column is
Download
, an update is available.
Ensure that Panorama is running the same but not a later content release version than is running on managed firewalls and Log Collectors.
(Before you update the content release version on Panorama, be sure to upgrade managed firewalls and then Log Collectors (see Upgrade Log Collectors When Panorama Is Internet-Connected) to the same (or a later) content release version.
If you do not need to install content updates at this time, then skip ahead to the next step.
Install remaining content updates, as needed. When installed, the Currently Installed column displays a check mark.
Download
and
Install
the Applications or Applications and Threats update. Regardless of your subscription, Panorama installs and needs only the Applications content update, not the Threats content. For details, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
Download
and
Install
other updates (Antivirus, WildFire®, or URL Filtering) as needed, one at a time, and in any sequence.
Upgrade Panorama to the PAN-OS releases along your upgrade path to PAN-OS 10.1.
Upgrade Panorama with an Internet Connection to PAN-OS 8.1.
Upgrade Panorama with an Internet Connection to PAN-OS 9.0.
PAN-OS 9.0 introduced a new log format. If a local Log Collector is configured, logs are automatically migrated to the new format after you successfully upgrade Panorama to PAN-OS 9.0.
Do not continue on your upgrade path until you verify the automatic log migration completed successfully.
Upgrade Panorama with an Internet Connection to PAN-OS 9.1.
Upgrade Panorama with an Internet Connection to PAN-OS 10.0.
(
Panorama in Legacy mode only
)
Download
PAN-OS 10.0.0 and then
Download
and
Install
PAN-OS 10.0.8 or later release before you continue on your upgrade path.
This is required to preserve all logs stored on the NFS storage partition. Some logs stored on the NFS storage partition of a Panorama in Legacy mode are deleted if you install PAN-OS 10.0.7 or earlier PAN-OS 10.0 release.
Upgrade Panorama to PAN-OS 10.1.
Check Now
(
Panorama
Software
) for the latest releases. If a software release is available, the Action column displays
Download
.
Locate and
Download
the PAN-OS 10.1.0 image. After a successful download, the Action column changes from
Download
to
Install
for the downloaded image.
(
Panorama in Legacy mode only
)
Download
the PAN-OS 10.1.0 image and then
Download
the PAN-OS 10.1.3 or later release image.
This is required to preserve all logs stored on the NFS storage partition. Some logs stored on the NFS storage partition of a Panorama in Legacy mode are deleted if you install PAN-OS 10.1.2 or earlier PAN-OS 10.1 release.
Install the downloaded image and then reboot.
Install
the image.
(
Panorama in Legacy mode only
)
Install
the PAN-OS 10.1.3 or later release image only.
After the installation completes successfully, reboot using one of the following methods:
If prompted to reboot, click
Yes
. If you see a CMS Login prompt, press Enter without typing a username or password. When the Panorama login prompt appears, enter the username and password you specified during initial configuration.
If you are not prompted to reboot,
Reboot Panorama
from the Device Operations section (
Panorama
Setup
Operations
).
(
Logs generated in PAN-OS 8.1 or earlier releases only
) If the Log Collector stores logs generated in PAN-OS 8.1 or earlier release, the upgrade to PAN-OS 10.1 an alert is displayed notifying you that logs generated in PAN-OS 8.1 or earlier release were detected and are no longer available after upgrade to PAN-OS 10.1.
This alert provides the exact CLI commands required to migrate and recover logs generated in PAN-OS 8.1 or earlier release after successful upgrade to PAN-OS 10.1. Save these CLI commands if you want to recover the logs generated while running PAN-OS 8.1 and earlier release.
Acknowledge the notification and
Install
PAN-OS 10.1 again.
(
Optional for Logs generated in PAN-OS 8.1 or earlier releases only
) After successful upgrade to PAN-OS 10.1, migrate and recover logs generated in PAN-OS 8.1 and earlier releases.
If you choose to not migrate and recover logs generated in PAN-OS 8.1 and earlier releases, they are deleted and are no longer available. Migrating the log format is required to recover logs generated in PAN-OS 8.1 and earlier releases after successful upgrade to PAN-OS 10.1.
Skip this step if you do not need to preserve logs generated in PAN-OS 8.1 or earlier release or if there are no logs that need to be migrated.
Log in to the Panorama CLI of the Log Collector.
Enter the CLI commands automatically displayed in the previous step to migrate logs.
The commands displayed to migrate logs are dynamic and unique to each Log Collector.
View the status of the log migration.
admin> 
debug logdb migrate-lc status
Do not reboot or otherwise power off the Log Collector until the log migration is complete. Disrupting the log migration may result in log loss.
(
If local Log Collector is in a Collector Group
) Upgrade the remaining Log Collectors in the Collector Group.
Upgrade Log Collectors When Panorama Is Internet-Connected
Upgrade Log Collectors When Panorama Is Not Internet-Connected
(
Best Practice
) Schedule recurring, automatic content updates.
Panorama does not synchronize content update schedules across HA peers. You must perform this task on both the active and passive Panorama.
In the header row for each update type (
Panorama
Dynamic Updates
), the
Schedule
is initially set to
None
. Perform the following steps for each update type.
Click
None
and select the update frequency (
Recurrence
). The frequency options depend on the update type.
Select the schedule action:
Download And Install
(
Best Practice
)—Panorama automatically installs updates after downloading them.
Download Only
—You must manually install updates after Panorama downloads them.
Based on the best practices for the security posture of your organization, configure a delay (
Threshold
) after an update becomes available before Panorama downloads the update.
Click
OK
to save your changes.
Select
Commit
Commit to Panorama
and
Commit
your changes.