Install Updates for Panorama with an Internet Connection
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute User-ID Information to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Configure Basic WildFire Appliance Settings on Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Restore an Expired Device Certificate
- Downgrade from Panorama 9.1
End-of-Life (EoL)
Install Updates for Panorama with an Internet Connection
If Panorama™ has a direct connection to the
internet, perform the following steps to install Panorama software
and content updates as needed. If Panorama is running in a high
availability (HA) configuration, upgrade the Panorama software on
each peer (see Install
Updates for Panorama in an HA Configuration).
Upgrading
the software on the Panorama virtual appliance does not change the system
mode; switching to Panorama mode or Management Only mode is a manual task
that requires additional settings as described when you Set
Up the Panorama Virtual Appliance with Local Log Collector.
If
you are upgrading from PAN-OS 8.1, PAN-OS® 9.0 introduced a new
log data format for local and Dedicated Log Collectors. On your
upgrade path to PAN-OS 10.0, existing log data is automatically
migrated to the new format when you upgrade to PAN-OS 9.0. During
reformatting, log data is not visible in the ACC or Monitor tabs. Additionally,
new log data is not forwarded to Log Collectors until reformatting
is complete. While the reformatting takes place, new logs are written
to the firewall system disk and after the procedure is successfully
completed, the new logs are forwarded to the appropriate Log Collector.
You
must upgrade all Log Collectors in a collector group at the same
time to avoid losing log data loss. No log forwarding or log collection
occurs if the Log Collectors in a collector group are not all running
the same PAN-OS version. Additionally, the log data for the Log
Collectors in the collector group is not visible in the ACC or Monitor tabs
until all Log Collectors are running the same PAN-OS version. For example,
if you have three Log Collectors in a collector group and you upgrade
two of the Log Collectors, then no logs are forwarded to any Log
Collectors in the collector group.
Before updating Panorama,
refer to the Release Notes for the
minimum content release version required for PAN-OS 9.1.
For M-100 appliances,
Palo Alto Networks requires upgrading the memory to 32GB or more
for management and log collection tasks. See the M-100 Memory Upgrade Guide before
upgrading your M-100 appliance to PAN-OS 9.1.0.
- 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 9.1.You cannot skip the installation of any feature release versions in the path from the currently running PAN-OS version to PAN-OS 9.1. Review the known issues and changes to default behavior in the Release Notes and upgrade/downgrade considerations in the New Features Guide for each release through which you pass as part of your upgrade path.
- (Panorama Interconnect plugin only) Synchronize the Panorama Node with the
Panorama Controller.Before you begin upgrading a Panorama Node, you must synchronize the Panorama Controller and Panorama Node configuration. This is required to successfully push the common Panorama Controller configuration to your Panorama Node after successful upgrade.
- 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 (PanoramaSetupOperations), 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.
- 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 9).
- Select PanoramaDynamic Updates and Check
Now for the latest updates. If an update is available,
the Action column displays a Download link.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.
- Select PanoramaDynamic Updates and Check
Now for the latest updates. If an update is available,
the Action column displays a Download link.
- Upgrade Panorama to the PAN-OS releases along your upgrade
path to PAN-OS 9.1.
- Install Updates for Panorama with an Internet Connection to PAN-OS 8.1.
- Install Updates for 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 to PAN-OS 9.1.
- Check Now (PanoramaSoftware) for the latest releases. If a software release is available, the Action column displays Download.
- Locate and Download the PAN-OS 9.1.0 image. After a successful download, the Action column changes from Download to Install for the downloaded image.
- Install the downloaded image
and then reboot.
- Install the image.
- 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 (PanoramaSetupOperations).
- (Required only if upgrading to PAN-OS 9.1.1 or a later release) After you complete the above steps for the PAN-OS 9.1 base image, repeat steps 1 through 3 to upgrade to the target maintenance release.
- (If local Log Collector is in a Collector Group) Upgrade the remaining Log Collectors in the Collector Group.
- (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 (PanoramaDynamic 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 CommitCommit to Panorama and Commit your changes.