PAN-OS 10.2.2 Known Issues
Table of Contents
Expand all | Collapse all
PAN-OS 10.2.2 Known Issues
PAN-OS® 10.2.2 known issues.
The following list includes only outstanding known issues specific to PAN-OS
®10.2.2. This list includes issues specific to Panorama™, GlobalProtect™, VM-Series plugins, and WildFire®, as well as known issues that apply more generally or that are not identified by an issue ID.
The WildFire analysis report on the firewall log viewer (
) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
Workaround: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the
Detailed Log View.
In a WildFire appliance cluster, issuing the
show cluster-all peersCLI command when a node within the cluster is being rebooted generates the following error:
Server error : An error occured.
The sample analysis statistics that are returned when issuing the
show wildfire local statisticsCLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
The following WildFire appliance CLI command does not return a signature generation status as expected:
show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
The WildFire appliance might erroneously generate and log the following device certification error:
Device certificate is missing or invalid. It cannot be renewed.
In WildFire appliance clusters, issuing the
show cluster controllerCLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
Workaround:Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
The number of registered WildFire appliances reported in Panorama (
) does not accurately reflect the current status of connected WildFire appliances.
Managed WildFire Appliances
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
and edit the Panorama Settings to enable one of the following:
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the
Sharedobjects in your configuration.
On the M-600 appliance, closed ElasticSearch shards are not deleted from the M-600 appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (
Workaround:Log in to the Log Collector CLI and restart ElasticSearch.
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (
) are not displayed and cannot be configured.
On the Panorama management server, policy rulebase reordering when you
View Rulebase by Groups(
) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
Malformed Requesterror is displayed when you
Test Connectionfor an email server profile (
SMTP over TLSand the
Passwordincludes an ampersand (&).
On M-600 appliances in Panorama or Log Collector mode, the
es-2ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector
EShealth status (
) to be degraded.
Workaround:Log in to the Panorama or Log Collector CLI experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
Firewalls forwarding logs to a syslog server over TLS (
) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
For Panorama-managed firewalls in an Active/Active High Availability (HA) configuration where you configure the firewall HA settings (
) in a template or template stack (
), performing a local commit on one of the HA firewalls triggers an HA config sync on the peer firewall. This causes the HA peer configuration to go
Out of Sync.
M-300 and M-700 appliances may generate erroneous system logs (
) to alert that the M-Series appliance memory usage limits are reached.
On the Panorama management server, the
undefined undefinedif you override an SSH Service Profile (
) Hostkey configured in a Template from the Template Stack.
SSH Service Profile
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (
show -> dis-block-table is unexpected
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (
ACC. This results in the ACC displaying
no data to displaywhen you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
Administrator Typefor an existing administrator (
Role-Basedcustom admin, or vice versa, does not modify the access privileges of the administrator.
On the Panorama management server, admins can still perform a selective push to managed firewalls when
Push All Changesand
Push for Other Adminsare disabled in the admin role profile (
This issue is now resolved. SeePAN-OS 10.2.4-h3 Addressed Issues
On the Panorama management server in a high availability (HA) configuration, the primary HA peer may enter a
primary-non-functionalstate and generate a system log (
) with the following message:
High root partition usage: going to state Non-Functional
Certificates are not successfully generated using SCEP (
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (
) as part of a template or template stack configuration.
For PA-3400 Series firewalls, the default log rate is set too low and the max configurable log rate is incorrectly capped resulting in the firewall not generating more than 6,826 logs per second.
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (
) is generated each time the firewall reaches maximum disk usage capacity.
ElasticSearch may not start properly when a newly installed Panorama virtual appliance powers on for the first time, resulting in the Panorama virtual appliance being unable to query logs forwarded from the managed firewall to a Log Collector.
Workaround:Log in to the Panorama CLI and start the PAN-OS software.
On the Panorama management server, you are unable to Context Switch from one managed firewall to another.
Workaround:After you Context Switch to a managed firewall, you must first Context Switch back to Panorama before you can continue to Context Switch to a different managed firewall.
On the Panorama management server, cloning any template (
) corrupts certificates (
) with the
Block Private Key Exportsetting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
For example, you have template A, B, and C where templates A and B have certificates with the
Block Private Key Exportsetting enabled. Cloning template C corrupts the certificates with
Block Private Key Exportsetting enabled in templates A and B.
Workaround:After cloning a template, delete and re-import the corrupted certificates.
PAN-OS 10.2.2-h1 and later releases.
On the Panorama management server, the Virtual Routers (
) setting is not available when configuring a custom Panorama admin role (
On M-600 appliances in an Active/Passive high availability (HA) configuration, the
configdprocess restarts due to a memory leak on the
ActivePanorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
Workaround:Manually reboot the
ActivePanorama HA peer.
When decryption is enabled, Safari and Google Chrome browsers on Mac computers running macOS Monterey or later reject the server certificates firewalls present. The browsers cannot validate the chain of trust for the certificates because the Authority Key Identifier (AKID) of the server certificates and the Subject Key Identifier (SKID) of the forward trust certificate do not match.
Workaround:Use a forward trust certificate that does not contain AKID or SKID extensions.
When viewing traffic or threat logs from the firewall ACC or Monitor, performing a reverse DNS lookup, for example, when resolving IP addresses to domain names using the
Resolve Hostnamefeature, can cause the appliance to crash and restart if DNS server settings have not been configured.
Workaround:Provide a DNS server setting for the firewall (
). If you cannot reference a valid DNS server, you can add a dummy address.
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you
Push to Devices
Commit and Push
Palo Alto Networks® Next-Gen firewalls experience a logs per second (LPS) degradation after upgrade to PAN-OS 10.2.2.
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
When a DNS request is submitted to the DNS Security service for inspection, the dataplane pan-task process (all_pktproc) might fail during the DNS request process, or when the dataplane cache is reset, or if the cache output is generated through the CLI, resulting in firewall crashes or the inability/reduced capability to process network traffic.
The following CLI commands can trigger a crash of the all_pktproc process:
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
Workaround: Retry the operation.
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, when making changes in the Service Connection and Remote Networks area, the configuration changes do not display in the Push Scope during a commit.
Workaround: For service connection changes, make sure that Service Setup is selected in the Push Scope before you commit. For remote network changes, make sure that Remote Networks is selected in the Push Scope before you commit.
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, after migrating from a single tenant to a multi-tenant Prisma Access deployment and making configuration changes, the Cloud Services plugin shows
No pending changes to commitwhen you hover over the Commit tab, even though there are pending changes to commit.
Workaround: The status shown when hovering over the Commit tab is a cosmetic issue. Commit the pending changes, if required.
WF-500 and WF-500-B appliance only) System log forwarding does not work over a TLS connection.
URL filtering logs (
) erroneously truncate a 16KB Header value and do not display the Header values that follow the truncated 16KB header.
For example, a URL filtering log has 5 Headers. The second Header has a 16KB value. In the URL filtering log, the first header and the value are displayed, second Header value is truncated, and remaining three headers are not displayed.
PA-5450 firewall only) Trying to configure a custom payload format under
PA-5450 firewall only) The Panorama web interface does not display any predefined template stack variables in the dropdown menu under
Workaround:Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
PA-5450 firewall only) Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
Workaround:Restart the log receiver service by running the following CLI command:
PA-5450 firewall only) If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
If SAML is configured as the authentication method for GlobalProtect, authentication on the Portal page is not successful in the browser.
Workaround:Use the GlobalProtect app installed on the endpoint to authenticate.
Certain webpages that use chunked-encoded data transfers might not load properly when analyzed by Advanced URL Filtering cloud inline categorization.
PA-5450 firewall only) Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
Commita configuration change, the
Statusgoes directly from
Completedand does accurately reflect the commit job progress.
On the Panorama management server,
Export Panorama and devices config bundle(
) fails to export. When the export fails, you are redirected to a new window and the following error is displayed:
Failed to redirect error to /var/log/pan/appweb3-panmodule.log (Permission denied)
After you successfully upgrade a PA-3000 Series firewall to PAN-OS 10.2.0 or later release and Enterprise data loss prevention (DLP) plugin 3.0.0 or later release, the first configuration push from the Panorama management server causes the firewall dataplane to crash.
Workaround:Restart the firewall to restore dataplane functionality.
After deleting an MP pod and it comes up, the
show routingcommand output appears empty and traffic stops working.
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
Workaround:Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
On the Panorama management server, dynamic content updates are not automatically pushed to VM-Series firewalls licensed using the Panorama Software Firewall License plugin when
Automatically push content when software device registers to Panorama(
) is enabled.
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
The SCP Server Profile configuration (
are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
On the Panorama management server, the Template Status displays no synchronization status (
) after a bootstrapped firewall is successfully added to Panorama.
Workaround:After the bootstrapped firewall is successfully added to Panorama, log in to the Panorama web interface and select
Push to Devices
If you enable SCTP security using a Panorama template when
SCTP INIT Flood Protectionis enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the
SCTP INIToption is not available in the Zone Protection profile.
Workaround:Log out of the firewall and log in again to make the
SCIT INIToption available on the web interface.
On the Panorama management server, not all data profiles (
) are displayed after you:
DLP Data Filtering Profiles
Workaround:Log in to the Panorama CLI and reset the DLP plugin.
admin > request plugins dlp reset
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to
Hold client request for category lookupand the action set to
Reset-Bothand the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
Workaround: Do not use a logical router instance with no interfaces bound to it.
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
to synchronize the templates.
Push to Devices
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
Workaround:Reboot the Panorama HA pair.
On the Panorama management server, performing a
Commit and Push(
Commit > Commit and Push) may intermittently not push the committed configuration changes to managed firewalls.
Commit > Push to Devicesto push the committed configuration changes to your managed firewalls.
Scheduled report emails (
) are not emailed if:
Workaround:To receive a scheduled report email for all other PDF report types:
On the Panorama management server, an M-700 appliance in Log Collector mode fails to connect to Panorama when added as a managed collector (
Panorama > Managed Collectors
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
Workaround:Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
On the Panorama management server, pushing an unsupported Minimum Password Complexity (
) to a managed firewall erroneously displays
commit time outas the reason the commit failed.
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
Workaround: Reboot the worker nodes before upgrading to PAN-OS 10.2.
A user interface issue in PAN-OS renders the contents of the
Inline MLtab in the
URL Filtering Profileinaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a
License required for URL filtering to functionis unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
Workaround:Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
show running resource-monitorwith the
ingress-backlogsoption produces the following server error:
Dataplane is not up or invalid target-dp(*.dp*).
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
Workaround:Issue the following command to retrieve and update the licenses:
license request fetch.
This issue is now resolved by PAN-189643. SeePAN-OS 10.2.4 Addressed Issues
QoS fails to run on a tunnel interface (for example, tunnel.1).
No results are displayed when you
Show Application Filterfor a Security policy rule (
Show Application Filter