Downgrade from Panorama 9.1
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)
Downgrade from Panorama 9.1
Procedure on how to downgrade from Panorama 9.1 to Panorama
9.0.
PAN-OS® 9.1 introduces the ability for the
firewall to automatically revert its configuration to the last running
configuration if the connection between the Panorama management
server and the firewall is broken and support for SD-WAN. However, these
features are not compatible with Panorama™ running PAN-OS 9.0 or
earlier release. Use the following workflow to downgrade firewalls
before you downgrade Log Collectors and Panorama running a Panorama
9.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.
Review the Palo Alto Networks Compatibility Matrix to
confirm that the firewalls and appliances you intend to downgrade
are compatible with the PAN-OS release to which you intend to downgrade.
For example, PA-220, PA-800 Series, PA-5200 Series and some VM-Series
firewalls are not supported on any release earlier than PAN-OS 8.0
and you cannot manage these firewalls from Panorama after you downgrade
Panorama to Panorama 7.1. 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.
- Downgrade each firewall running a PAN-OS 9.1 release.If downgrading more than one firewall, streamline the process by having each firewall-specific PAN-OS 9.0 image downloaded to Panorama before you start downgrading. For example, to downgrade your PA-220 firewall to PAN-OS 9.0.0, download the PanOS_220-9.0.0 or PanOS_3000-9.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 9.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 FirewallsInstall (Action column) the appropriate PAN-OS 9.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
Panorama 9.1.
- Check Now for available images (PanoramaDevice DeploymentSoftware).
- Locate the Panorama 9.0 image. If the image is not already downloaded, then Download it (Action column).
- After the download is complete, Install the image on each Log Collector running Panorama 9.1. Select Reboot device after install to automatically reboot the device when the upgrade is complete.
- Downgrade Panorama.
- Check Now for available images (PanoramaDevice DeploymentSoftware).
- Locate the Panorama 9.0 image. If the image is not already downloaded, then Download it.
- After the download is complete, Install the image on Panorama.
- 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).
- Migrate Panorama logs to the PAN-OS 9.0 log format.During the migration, log data is not visible in the ACC or Monitor tabs. Additionally, new log data is not forwarded to Log Collectors until the migration is complete.
- View the incoming logging rate.For best results, start log migration when the incoming log rate is low. To check the rate, run the following command from the Log Collector CLI:
admin@FC-M500-1> debug log-collector log-collection-stats show incoming-logs
High CPU utilization (close to 100%) during log migration is expected and operations will continue to function normally. Log migration is throttled in favor of incoming logs and other processes in the event of resource contention. - Start migrating the logs on each Log Collector to
the previous format.To begin the migration, enter the following command from the CLI of each Log Collector:
admin@FC-M500-1> request logdb migrate lc serial-number <ser_num> start
- View the log migration status to estimate the amount
of time it will take to finish migrating all existing logs to the
previous format.
admin@FC-M500-1> request logdb migrate lc serial-number <ser_num> status Slot: all Migration State: In Progress Percent Complete: 0.04 Estimated Time Remaining: 451 hour(s) 47 min(s)
- View the incoming logging rate.