Upgrade/Downgrade Considerations

The following table lists the new features that have upgrade or downgrade impact. Make sure you understand all upgrade/downgrade considerations before you upgrade to or downgrade from a PAN-OS 9.0 release. For additional information about PAN-OS 9.0 releases, refer to the PAN-OS 9.0 Release Notes.
Review the following when upgrading Panorama to PAN-OS 9.0:
PAN-OS 9.0 Upgrade/Downgrade Considerations
Feature
Upgrade Considerations
Downgrade Considerations
VM-Series Plugin
The VM-Series plugin manages integration with public and private clouds, allowing Palo Alto Networks to release bug fixes, new features, and new cloud integrations independent of a PAN-OS release.
Save your PAN-OS 8.1. configuration before upgrading to PAN-OS 9.0.
The plugin is installed automatically when you install or upgrade the VM-Series firewall to PAN-OS 9.0. The plugin can be upgraded or downgraded, but it cannot be removed from PAN-OS.
The plugin supports all clouds so upgrades might not apply to you. Before you upgrade the plugin, review the release notes.
(PAYG licenses only) You must upgrade to VM-Series plugin 1.0.2 (or later) after you upgrade to a PAN-OS 9.0 release and, then, reboot your firewall to recover your pay-as-you-go (PAYG) license after you upgrade from a PAN-OS 8.1 release.
Each plugin version provides PAN-OS compatibility information. You can upgrade the plugin version from the VM-Series firewall with DevicePluginsCheck Now or from a bootstrap file.
If you have upgraded the VM-Series plugin independent of PAN-OS, downgrading to a previous release works the same as for other plugins.
Downgrading from PAN-OS version 9.0 to 8.1 generates many error messages or disallows the downgrade. Instead of downgrading, restore your 8.1 configuration on a new firewall.
  1. Deactivate any licenses for the VM-Series firewall, and delete the VM.
  2. Deploy a new VM-Series firewall and load your previously saved configuration.
Use Panorama to manage VM-Series plugin integrations with your managed firewalls
If you have one or more cloud integrations configured in 8.1 when you upgrade to 9.0 (Google Stackdriver, Azure Application Insights, or AWS CloudWatch), the VM-Series plugin is automatically installed and any existing configuration is migrated to the VM-Series plugin.
If you have not configured cloud integrations in 8.1, the VM-Series plugin is supplied when you upgrade Panorama to 9.0, but it is not installed.
In 9.0, if you want to manage cloud integrations from Panorama, go to PanoramaPluginsand use Check Now to view the VM-Series plugin. Load the VM-Series plugin, and install. Once installed the plugin can be upgraded and downgraded.
If you have upgraded the VM-Series plugin independent of Panorama, downgrading to a previous release works the same as for other plugins.
User-ID Support for Large Numbers of Terminal Servers
None.
To downgrade, remove any Alternative IP Addresses that contain an FQDN. If you have configured more than 1000 Terminal Services agents across all virtual systems on the firewall, remove agents until there are no more than 1000 before downgrading.
Shared User-ID Mapping Across Virtual Systems
None.
If you have consolidated the User-ID sources on the hub, you need to reconfigure the User-ID sources on each virtual system.
WinRM Support for Server Monitoring
None.
During a downgrade, any server profiles using WinRM-HTTP or WinRM-HTTPS are migrated to WMI.
Universally Unique Identifiers for Policy Rules
When you upgrade, upgrade Panorama first, push the rulebases to the firewalls Panorama manages, and then upgrade the firewalls. If you do not push the policy configuration to the firewalls from Panorama before upgrading the managed firewalls, the upgrade will not be successful.
In addition, if you are upgrading an HA pair, upon upgrade to PAN-OS 9.0, each peer independently assigns UUIDs for each policy rule. Because of this, the peers will show as out of sync until you sync the configuration (DashboardWidgetsSystemHigh AvailabilitySync to peer).
In the ACC, the Rule field is now Rule Name to distinguish it from the new Rule UUID field.
If you push a log forwarding profile that uses UUIDs from an upgraded Panorama to a firewall that has not been upgraded, the commit on the firewall will not be successful.
All UUIDs are retained as attributes so they can be reapplied to the rulebase in case you re-upgrade.
If you are using UUIDs in log forwarding profiles or custom reports, the downgrade and any autocommits will be successful, but any subsequent commits will not be successful.
If you downgrade Panorama, the Shared Policy column (PanoramaManaged DevicesSummary) for all devices displays as Out of sync, due to the missing UUIDs. After you commit and push the configuration to the devices, they will display as In sync.
Upgrading Panorama with Local Log Collectors or Dedicated Log Collectors
PAN-OS 9.0 introduces a new log data format, and as a result, the upgrade procedure may take up to six hours to complete in order for Panorama or the Log Collector to automatically reformat existing log data. During this time, log data is not visible in the ACC and Monitor tabs. Additionally, new log data is not forwarded to the appliance until the upgrade is complete.
Existing log data must be reformatted to the log format introduced in PAN-OS 8.0 upon downgrade using a log migration script provided by Palo Alto Networks. During the reformatting, log data is not visible in the ACC and Monitor tabs. Additionally, new log data is not forwarded to Log Collectors until the reformatting is complete.
All Log Collectors in a collector group must be upgraded at the same time to avoid any log data loss. If the majority of Log Collectors in a collector group are upgraded, the log data for the minority, non-upgraded Log Collectors are not visible in the ACC and Monitor tabs.
For example, if you have three Log Collectors in a collector group, and you upgrade two of the Log Collectors, logs are not forwarded to the third non-upgraded Log Collector. Additionally, the existing log data for the third Log Collector is not displayed in the ACC or Monitor tabs.
Built-In External Dynamic List for Bulletproof HostsNone.
Downgrade from PAN-OS 9.0 to earlier release versions is not supported for firewalls with security policy rules that use the predefined external dynamic lists for bulletproof hosts. Additionally, if Panorama pushes the list to a device group that includes pre-9.0 firewalls, the commit will fail.
Workaround:In either of these cases, remove the bulletproof hosts list from any security policy rules that reference it.
URL Filtering
Release versions earlier than PAN-OS 9.0 allowed you to configure URL Filtering Overrides to create exceptions to URL category enforcement. In PAN-OS 9.0, the URL Filtering profile Overrides tab, where you would configure these block and allow lists, no longer exists.
Now, to configure exceptions to URL categories, you can create a custom URL category (ObjectsCustom ObjectsURL Category). Any URL Filtering overrides that you configured before upgrading to PAN-OS 9.0 are now converted to custom URL Categories. For more details on these changes, see Multi-Category URL Filtering.
If you had URL Filtering overrides configured before up upgrading to PAN-OS 9.0, there are two issues you might see after the upgrade. Each has a workaround that you might consider implementing.
  • The URL Filtering profile might reach its limit for custom URL categories, causing the PAN-OS 9.0 upgrade to fail.
    Workaround: Use this command to reset the ID manager process: debug device-server reset id-manager type vsys-custom-url-category | shared-custom-url-category.
    If that doesn't work, you might need to remove some custom URL categories.
  • In earlier release versions, URL Filtering overrides had priority enforcement ahead of custom URL categories. Block or allow category overrides that are now converted to custom URL categories will now longer receive priority enforcement over other custom URL categories.
    Workaround: To ensure priority enforcement for custom URL categories, especially for sites that you want to allow:
    1. Create a URL Filtering Profile that defines site access for a custom URL category.
      Select ObjectsSecurity ProfilesURL FilteringCategories, and set the Site Access (like allow or block) for Custom URL Categories that you want to exclude from a URL category.
    2. Create a new security policy rule to prioritize enforcement for URL category exceptions. Attach the URL Filtering profile you just created to that rule (PoliciesSecurityActionsProfile SettingsProfiles). Because the firewall evaluates rules from top to bottom, make sure that this rule appears at the top of your security policy (SecurityPolicies).
    The Overrides tab objects are removed and Custom URL Category objects are created for firewalls running PAN-OS 8.1 or earlier releases when managed by a Panorama management server that is upgraded to PAN-OS 9.0.
Split Tunnel to Exclude by Access Route
None.
If you are either downgrading a firewall from PAN-OS 9.0 to PAN-OS 8.1 or pushing a configuration from a Panorama running PAN-OS 9.0 to a firewall running PAN-OS 8.1, you must remove all address groups from the access route-based split tunnel configuration (NetworkGlobalProtectGateways<gateway-config>AgentClient Settings<client-settings-config>Split TunnelAccess Route).
VM-50 and VM-50 LiteIf you upgrade from PAN-OS 8.1.7 or earlier and you are using predefined reports, the reports are disabled upon upgrade. The VM-50 and VM-50 Lite do not support predefined reports starting in PAN-OS 8.1.8.None.
BGP Minimum Route Advertisement Interval
If you upgrade from PAN-OS 8.0.11 (or a later PAN-OS 8.0 release) to a PAN-OS 9.0 release, the CLI operational command set system setting bgp-mrai-timer value is deprecated. Configure the minimum route advertisement interval for a BGP peer in the user interface instead (NetworkVirtual Routersvirtual routerBGPPeer GroupPeerConnection Options).
If you downgrade from PAN-OS 9.0 to PAN-OS 8.0.11 (or a PAN-OS 8.0 release later than PAN-OS 8.0.11), the minimum route advertisement interval you configured for a BGP peer no longer applies to the peer and the user interface to configure the minimum route advertisement interval does not exist. The default value of 30 seconds applies to all BGP peers. Use the CLI operational command set system setting bgp-mrai-timer value to change the interval for all BGP peers.

Related Documentation