Upgrade the VM-Series PAN-OS Software Using Panorama
Table of Contents
10.1
Expand all | Collapse all
-
-
- Upgrade Panorama with an Internet Connection
- Upgrade Panorama Without an Internet Connection
- Install Content Updates Automatically for Panorama without an Internet Connection
- Upgrade Panorama in an HA Configuration
- Migrate Panorama Logs to the New Log Format
- Upgrade Panorama for Increased Device Management Capacity
- Downgrade from Panorama 10.1
- Troubleshoot Your Panorama Upgrade
-
- What Updates Can Panorama Push to Other Devices?
- Schedule a Content Update Using Panorama
- Panorama, Log Collector, Firewall, and WildFire Version Compatibility
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade a WildFire Cluster from Panorama with an Internet Connection
- Upgrade a WildFire Cluster from Panorama without an Internet Connection
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
Upgrade the VM-Series PAN-OS Software Using Panorama
How do I upgrade my VM-Series Panorama-managed firewalls.
Use
the following procedure to upgrade firewalls that you manage with
Panorama. This procedure applies to standalone firewalls and firewalls
deployed in a high availability (HA) configuration.
If Panorama is unable to connect directly
to the update server, follow the procedure for deploying updates to firewalls
when Panorama is not internet-connected so that you can manually
download images to Panorama and then distribute the images to firewalls.
Before
you can upgrade firewalls from Panorama, you must:
- Make sure Panorama is running the same or a later PAN-OS version than you are upgrading to. You must upgrade Panorama and its Log Collectors to 9.1 before upgrading the managed firewalls to this version. In addition, when upgrading Log Collectors to 9.1, you must upgrade all Log Collectors at the same time due to changes in the logging infrastructure.
- Plan for an extended maintenance window of up to six hours when upgrading Panorama to 9.1. This release includes significant infrastructure changes, which means that the Panorama upgrade will take longer than in previous releases.
- Ensure that firewalls are connected to a reliable power source. A loss of power during an upgrade can make a firewall unusable.
- After upgrading Panorama, commit and push the configuration to the firewalls you are planning to upgrade.
- Verify that enough hardware resources are available to the VM-Series firewall.Refer to the VM-Series System Requirements to see the resource requirements for each VM-Series model. Allocate additional hardware resources before continuing the upgrade process; the process for assigning additional hardware resources differs on each hypervisor.If the VM-Series firewall does not have the required resources for the model, it defaults to the capacity associated with the VM-50.
- From the web interface, navigate toand make sure you have the correct VM-Series firewall license and that the license is activated.DeviceLicensesOn the VM-Series firewall standalone version, navigate toand make sure that you have activated the support license.DeviceSupport
- Save a backup of the current configuration file on each managed firewall you plan to upgrade.Although the firewall automatically creates a configuration backup, it is a best practice to create and externally store a backup before you upgrade.
- From the Panorama web interface, selectand clickPanoramaSetupOperationsExport Panorama and devices config bundleto generate and export the latest configuration backup of Panorama and of each managed appliance.
- Save the exported file to a location external to the firewall. You can use this backup to restore the configuration if you have problems with the upgrade.
- Update the content release version on the firewalls you plan to upgrade.Refer to the Release Notes for the minimum content release version required for PAN-OS 9.1. Make sure to follow the Best Practices for Application and Threat Updates when deploying content updates to Panorama and managed firewalls.
- SelectandPanoramaDevice DeploymentDynamic UpdatesCheck Nowfor the latest updates. If an update is available, the Action column displays aDownloadlink.
- If not already installed,Downloadthe latest content release version.
- ClickInstall, select the firewalls on which you want to install the update, and clickOK. If you are upgrading HA firewalls, you must update content on both peers.
- (HA firewall upgrades only) If you will be upgrading firewalls that are part of an HA pair, disable preemption. You need only disable this setting on one firewall in each HA pair.
- Selectand edit theDeviceHigh AvailabilityElection Settings.
- If enabled, disable (clear) thePreemptivesetting and clickOK.
- Commityour change. Make sure the commit is successful before you proceed with the upgrade.
- Download the target PAN-OS release image.
- SelectandPanoramaDevice DeploymentSoftwareCheck Nowfor the latest release versions.
- Downloadthe firewall-specific file (or files) for the release version to which you are upgrading. You must download a separate installation file for each firewall model (or firewall series) that you intend to upgrade.
- Install the PAN-OS software update on the firewalls.
- ClickInstallin the Action column that corresponds to the firewall models you want to upgrade.
- In the Deploy Software file dialog, select all firewalls that you want to upgrade. To reduce downtime, select only one peer in each HA pair. For active/passive pairs, select the passive peer; for active/active pairs, select the active-secondary peer.
- (HA firewall upgrades only) Make sureGroup HA Peersis not selected.
- SelectReboot device after install.
- To begin the upgrade, clickOK.
- After the installation completes successfully, reboot using one of the following methods:
- If you are prompted to reboot, clickYes.
- If you are not prompted to reboot, selectandDeviceSetupOperationsReboot Device.
- After the firewalls finish rebooting, selectand verify the Software Version is 9.1.0 for the firewalls you upgraded. Also verify that the HA status of any passive firewalls you upgraded is still passive.PanoramaManaged Devices
- (HA firewall upgrades only) Upgrade the second HA peer in each HA pair.
- (Active/passive upgrades only) Suspend the active device in each active/passive pair you are upgrading.
- Switch context to the active firewall.
- In the High Availability widget on theDashboard, verify thatLocalfirewall state isActiveand thePeerisPassive).
- Select.DeviceHigh AvailabilityOperational CommandsSuspend local device
- Go back to the High Availability widget on theDashboardand verify thatLocalchanged toPassiveandPeerchanged toActive.
- Go back to the Panorama context and select.PanoramaDevice DeploymentSoftware
- ClickInstallin the Action column that corresponds to the firewall models of the HA pairs you are upgrading.
- In the Deploy Software file dialog, select all firewalls that you want to upgrade. This time, select only the peers of the HA firewalls you just upgraded.
- Make sureGroup HA Peersis not selected.
- SelectReboot device after install.
- To begin the upgrade, clickOK.
- After the installation completes successfully, reboot using one of the following methods:
- If you are prompted to reboot, clickYes.
- If you are not prompted to reboot, selectandDeviceSetupOperationsReboot Device.
- (Active/passive upgrades only) From the CLI of the peer you just upgraded, run the following command to make the firewall functional again:request high-availability state functional
- Verify the software and content release version running on each managed firewall.
- On Panorama, select.PanoramaManaged Devices
- Locate the firewalls and review the content and software versions in the table.For HA firewalls, you can also verify that the HA Status of each peer is as expected.
- (HA firewall upgrades only)If you disabled preemption on one of your HA firewalls before you upgraded, then edit theElection Settings() and re-enable theDeviceHigh AvailabilityPreemptivesetting for that firewall and thenCommitthe change.