PAN-OS 10.2.3 Known Issues
PAN-OS® 10.2.3 known issues.
The following list includes only outstanding known issues specific to PAN-OS
®10.2.3. 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
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (
with the Action set to
Data Filtering Profiles
Blockto a Security policy rule (
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 any logs (
) if there are over 500 users behind the firewall.
PA-3400 Series and PA-5440 firewalls only) The I7_misc memory pool on this platform is undersized and can cause a loss of connectivity when reaching the limit of the memory pool. Certain features, like using a decryption profile with Strip ALPN disabled, can lead to depleting the memory pool and causing a connection loss.
Workaround:Disable HTTP2 by enabling Strip ALPN in the decryption profile or avoid usage of the I7_misc memory pool.
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.
GCP BigTable might hang when GCP CBT CLI commands are issued in cases where google-base traffic is erroneously classified as unknown-tcp.
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
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 the firewall processes an unusually high amount of DNS traffic through the DNS Security service or when the dataplane cache is rebooted or the cache output is generated, the dataplane pan-task process (all_pktproc) might fail, resulting in firewall crashes or the inability/reduced capability to process network traffic.
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.
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.
PA-5450 firewall only) Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
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.
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.
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
On PA-3400 & PA-5400 series firewalls (minus the PA-5450), the CLI and SNMP MIB walk do not display the Model and Serial-number of the Fan tray and PSUs.
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 routed and zebrad daemons 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.
On the Panorama management server,
Validate Device Group(
erroneously issues a CommitAll operation instead of a ValidateAll operation when multiple device groups are included in the push and results in no configuration validation.
Commit and Push
Workaround:Validate device group configurations using one of the following methods.
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:
When the firewall has Advanced Routing enabled, a static route stays active after the interface goes down.
Workaround: For firewalls that support Bidirectional Forwarding Detection (BFD), configure BFD for the static route.
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.
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
Recommended For You
Recommended videos not found.