Downgrade from Panorama 10.1
Table of Contents
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
-
Downgrade from Panorama 10.1
Procedure on how to downgrade from Panorama 10.1 to Panorama
10.0.
PAN-OS® 10.1 introduces enhanced features
such as enhanced authentication that enables you to add new firewalls
to Panorama management, as well as the ability to schedule configuration
pushes to managed firewalls, to configure a unique master key for
Panorama and managed firewalls, to perform audit tracking for administrator activity
on Panorama and managed firewalls, and the ability for Panorama
to preserve uncommitted configuration changes when an unexpected
restart occurs. However, these features are not compatible with
Panorama appliances running PAN-OS 10.0 or earlier releases. Use
the following workflow to downgrade firewalls before you downgrade
Log Collectors and Panorama running a PAN-OS 10.1 release to an
earlier feature release. This procedure works both for Panorama
when managing a local Log Collector and for Panorama when managing
one or more Dedicated Log Collectors.
All
existing logs are lost after downgrade to PAN-OS 10.0. This means
that all logs ingested while running PAN-OS 10.1 are not visible
after downgrade to PAN-OS 10.0. Additionally, logs ingested while
running PAN-OS 10.1 cannot be retrieved by migrating the raw logs
forwarded from the managed firewall to the Log Collector before
they are ingested by the Log Collector.
However, you can
recover logs ingested while running PAN-OS 10.0, 9.1, or 9.0 by from
the Log Collector CLI after successful downgrade. Logs must be recovered
on each Log Collector downgraded to PAN-OS 10.0.
Review the Palo Alto Networks Compatibility Matrix to
confirm that the firewalls and appliances you intend to downgrade
are compatible with the PAN-OS version to which you intend to downgrade.
For the firewalls and appliances that you can downgrade, you should
also review the Upgrade/Downgrade Considerations to ensure
that you account for all features and configuration settings that
will be different or unavailable after you downgrade.
- Save a backup of the configuration files for Panorama and managed devices.
- Export Panorama and device configuration snapshot (PanoramaSetupOperations).Save the exported .tgz file to a location external to Panorama, Log Collectors, and firewalls. You can use this backup to restore the configuration if you experience problems that cause you to start over.If you have configured authentication for a Dedicated Log Collector and removed the admin administrator, configure and push a new admin user to your Dedicated Log Collectors.Dedicated Log Collectors must have the admin user configured in order to downgrade to PAN-OS 9.1 and earlier releases.Downgrade each firewall running a PAN-OS 10.1 version.If downgrading more than one firewall, streamline the process by having each firewall-specific PAN-OS 10.0 image downloaded to Panorama before you start downgrading. For example, to downgrade your PA-220 firewall to PAN-OS 10.0.0, download the PanOS_220-10.0.0 or PanOS_3000-10.0.0 images.Panorama requires that all firewalls are running the same or an earlier PAN-OS release. So before you downgrade Panorama, use and repeat the appropriate tasks below according to your environment to downgrade all managed firewalls as needed:
- Check Now for available images (PanoramaDevice DeploymentSoftware).Locate the PAN-OS 10.0 image for each model or series of firewalls you intend to downgrade. If the image is not already downloaded, then Download it.Non-HA FirewallInstall (Action column) the appropriate PAN-OS 10.0 version, select all the firewalls you intend to downgrade, select Reboot device after install, and click OK.Active/Active HA Firewalls
- Click Install, disable (clear) Group HA Peers, select either of the HA peers, select Reboot device after install, and click OK. Wait for the firewall to finish rebooting before you proceed.Click Install, disable (clear) Group HA Peers, select the HA peer that you didn’t update in the previous step, select Reboot device after install, and click OK.Active/Passive HA FirewallsIn this example, the active firewall is named fw1 and the passive firewall is named fw2:
- Install (Action column) the appropriate update, disable (clear) Group HA Peers, select fw2, select Reboot device after install, and click OK.After fw2 finishes rebooting, verify fw1 (DashboardHigh Availability widget) is still the active peer and that fw2 is still the passive peer (the Local firewall state is active and the Peer—fw2—is passive).Access fw1 and Suspend local device (DeviceHigh AvailabilityOperational Commands).Access fw2 (DashboardHigh Availability) and verify that the Local firewall state is active and the Peer firewall—fw1—is suspended.Access Panorama, select PanoramaDevice DeploymentSoftware, Install (Action column) the appropriate update, disable (clear) Group HA Peers, select fw1, select Reboot device after install, and click OK. Wait for fw1 to finish rebooting before you proceed.Access fw1 (DashboardHigh Availability widget) and verify that the Local firewall state is passive and the Peer—fw2—is active.If you enabled preemption in the Election settings (DeviceHigh AvailabilityGeneral), then fw1 will be reinstated as the active peer after reboot.Downgrade each Log Collector running PAN-OS 10.1.
- Check Now for available images (PanoramaDevice DeploymentSoftware).Locate the appropriate PAN-OS 10.0 image for your Panorama appliance. If the image is not already downloaded, then Download it (Action column).Palo Alto Networks requires downgrading your Log Collectors to PAN-OS 10.0.8 or later PAN-OS 10.0 release.After the download is complete, Install the image on each Log Collector running PAN-OS 10.1. Select Reboot device after install to automatically reboot the appliance when the upgrade is complete.Downgrade Panorama.
- Select PanoramaSoftware and Check Now for available images.Locate the appropriate PAN-OS 10.0 image for your Panorama appliance. If the image is not already downloaded, then Download it.After the download is complete, Install the image on your Panorama appliance.Reboot Panorama as follows:
- If you are prompted to reboot, click Yes. If you see a CMS Login prompt, press Enter without typing the username or password. When the Panorama login prompt appears, enter the username and password you set during initial configuration.
- If you are not prompted to reboot, select PanoramaSetupOperations and click Reboot Panorama (Device Operations).
Recover logs ingested while running PAN-OS 10.0, 9.1, and 9.0.All existing logs are lost after successful downgrade to PAN-OS 10.0. However, you can recover logs ingested by the Log Collector while it was running PAN-OS 10.0, 9.1, or 9.0. Logs ingested while running PAN-OS 10.1 are not recoverable.Repeat this step for all Log Collectors downgraded to PAN-OS 10.0.- Log in to the Log Collector CLI.Recover your logs.admin> debug logdb migrate-lc start log-type all time period start-date <date> end-date <date>The start-date and end-date specify the set of logs that are recovered. The command recovers logs ingested within the specified date range and while the Log Collector was running PAN-OS 10.0, 9.1, or 9.0.