Add data for 10.2 issues, addressed and known
This commit is contained in:
@@ -0,0 +1,986 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.0
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WIF-495
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, edits made to an existing data filtering profile (**Objects > DLP > Data Filtering Profiles**) can result in matching traffic not being detected by Enterprise DLP.
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-264281
|
||||
|
||||
When upgrading a ZTP firewall from PAN-OS 10.2 to PAN-OS 11.1 or later versions, if you use the **To SW Version** column to specify the target PAN-OS version, the upgrade process downloads and installs the intermediary base version containing an expired root certificate. This causes the ZTP firewall to lose connection with Panorama
|
||||
|
||||
**Workaround:** Follow the standard upgrade process from Panorama, which you use for non-ZTP firewalls, to upgrade to the target PAN-OS version that contains the valid root certificate.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-241536
|
||||
|
||||
On the Panorama management server, a user with an Admin Role is unable to modify or add filters to profiles under **Panorama** > **Network** > **Routing** > **Routing Profiles** > **Filters**, despite having the necessary read and write privileges.
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-229702
|
||||
|
||||
After upgrading a Panorama HA pair to PAN-OS 11.1, the ElasticSearch connectivity might fail to establish. The issue occurs because the client certificate on one of the Panorama devices does not have the necessary Extended Key Usage (EKU) set for server authentication, which is required for secure TLS communication.
|
||||
|
||||
**Workaround:**Contact Customer Support to renew the root client certificate.
|
||||
|
||||
## PAN-227344
|
||||
|
||||
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||
|
||||
## PAN-225337
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||
|
||||
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||
|
||||
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||
|
||||
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||
|
||||
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||
|
||||
## PAN-223488
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-222253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-221015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||
|
||||
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||
|
||||
`admin>``debug elasticsearch es-restart optional all`
|
||||
|
||||
## PAN-219644
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||
|
||||
## PAN-218521
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-215778
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||
|
||||
`504 Gateway timeout`
|
||||
|
||||
## PAN-215082
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209937
|
||||
|
||||
Certificate-based authentication for administrator accounts may be unable to log into the Panorama or firewall web interface with the following error:
|
||||
|
||||
`Bad Request - Your browser sent a request that this server could not understand`
|
||||
|
||||
## PAN-208325
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||
|
||||
- M-300 and M-700
|
||||
- PA-410 Firewall
|
||||
- PA-440, PA-450, and PA-460 Firewalls
|
||||
- PA-3400 Series
|
||||
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||
- PA-5450 Firewall
|
||||
|
||||
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||
|
||||
`admin>``request certificate fetch`
|
||||
|
||||
## PAN-207629
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.
|
||||
|
||||
## PAN-206909
|
||||
|
||||
The Dedicated Log Collector is unable to reconnect to the Panorama management server if the `configd` process crashes. This results in the Dedicated Log Collector losing connectivity to Panorama despite the managed collector connection `Status` (**Panorama** > **Managed Collector**) displaying `connected` and the managed colletor `Health` status displaying as healthy.
|
||||
|
||||
This results in the local Panorama config and system logs not being forwarded to the Dedicated Log Collector. Firewall log forwarding to the disconnected Dedicated Log Collector is not impacted.
|
||||
|
||||
**Workaround:** Restart the `mgmtsrvr` process on the Dedicated Log Collector.
|
||||
|
||||
1. [Log in to the Dedicated Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli).
|
||||
2. Confirm the Dedicated Log Collector is disconnected from Panorama.
|
||||
`admin>``show panorama-status`
|
||||
Verify the `Connected` status is `no`.
|
||||
3. Restart the `mgmtsrvr` process.
|
||||
`admin>``debug software restart process management-server`
|
||||
|
||||
## PAN-206268
|
||||
|
||||
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.
|
||||
|
||||
## PAN-206253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-206243
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.
|
||||
|
||||
## PAN-205187
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.
|
||||
|
||||
`admin>``request restart software`
|
||||
|
||||
## PAN-204663
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-201855
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting 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 Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||
|
||||
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||
|
||||
## PAN-199557
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||
|
||||
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||
|
||||
## PAN-197341
|
||||
|
||||
On the Panorama management server, if you create multiple device group **Objects** with the same name in the Shared device group and any additional device groups (**Panorama** > **Device Groups**) under the same device group hierarchy that are used in one or more **Policies**, renaming the object with a shared name in any device group causes the object name to change in the policies where it is used. This issue applies only to device group objects that can be referenced in a Security policy rule.
|
||||
|
||||
For example:
|
||||
|
||||
1. You create a parent device group `DG-A` and a child device group `DG-B`.
|
||||
2. You create address objects called `AddressObjA` in the `Shared`, `DG-A` and `DG-B` device groups and add `AddressObjA` to a Security policy rule under `DG-A` and `DG-B`.
|
||||
3. Later, you change the `AddressObjA` name in the `Shared` device group to `AddressObjB`.
|
||||
|
||||
Changing the name of the address object in the `Shared` device group causes the references in the Policy rule to use the renamed `Shared` object instead of the device group object.
|
||||
|
||||
## PAN-197097
|
||||
|
||||
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196720
|
||||
|
||||
During the CN-Series firewall deployment on Oracle OKEplatform, when you delete the deployment by deleting yamls, the MP/DP pods are stuck in Terminating state.
|
||||
|
||||
**Workaround:** Delete the CN-Series DP pods, MP pods, and then the pan-cni yaml file in a sequential order.
|
||||
|
||||
## PAN-194826
|
||||
|
||||
```caveat
|
||||
WF-500 appliance only
|
||||
```
|
||||
|
||||
System log forwarding does not work over a TLS connection.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-193251
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-192403
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.
|
||||
|
||||
## PAN-191570
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The Traffic Activity and SSL/TLS widgets in the **ACC** erroneously display `Report Error` if there is no SSL data to display.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-190435
|
||||
|
||||
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||
|
||||
## PAN-190311
|
||||
|
||||
```caveat
|
||||
PA-220 and PA-220R firewalls and PA-800 Series firewalls only
|
||||
```
|
||||
|
||||
There is an issue where management connectivity to the firewall is lost due to the expiration of the DHCP lease, which causes the IP configuration on the management port to be purged.
|
||||
|
||||
## PAN-189425
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) 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)`
|
||||
|
||||
## PAN-189395
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
Running any version of PAN-OS 10.2 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.
|
||||
|
||||
## PAN-189380
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
|
||||
2. Restart the firewall.
|
||||
`admin>` `request restart system`
|
||||
|
||||
## PAN-189361
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
Panorama is unable to distribute antivirus signature updates to firewalls with only an Advanced Threat Prevention license. Firewalls with previously installed and active Threat Prevention license are unaffected.
|
||||
|
||||
## PAN-189298
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On deploying the HA with 10.2.0-98 in Packet-mmap mode, the session sync for an existing session fails after restarting an active DP in Packet-mmap mode.
|
||||
|
||||
## PAN-189214
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
When the Advanced Threat Prevention license is present on a firewall without a Threat Prevention license, the antivirus signature update packages that are normally available to install under **Device** > **Dynamic Updates** are not displayed.
|
||||
|
||||
**Workaround:** Use the `request anti-virus upgrade {info | download | install}` CLI commands to retrieve a list of available antivirus updates and the download and installation status, download specific antivirus packages, and to install antivirus packages.Optionally, you can schedule recurring automatic updates using the following CLI command: `set deviceconfig system update-schedule anti-virus recurring`.
|
||||
|
||||
## PAN-189206
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
Device Group and Template administrator roles don't support a context switch between the Panorama and firewall web interface.
|
||||
|
||||
**Workaround:** Use a Superuser or Panorama administrator role to context switch.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189106
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, you must uninstall the ZTP Plugin 2.0 before you can successfully downgrade to PAN-OS 10.1. After successful downgrade, you must reinstall the latest ZTP Plugin 1.0 version.
|
||||
|
||||
**Workaround:** Before you downgrade Panorama to PAN-OS 10.1, uninstall ZTP Plugin 2.0. After you successfully downgrade Panorama to PAN-OS 10.1, re-install ZTP Plugin 1.0 and re-enable ZTP functionality.
|
||||
|
||||
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||
2. [Uninstall the ZTP Plugin](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/manage-firewalls/set-up-zero-touch-provisioning/uninstall-the-ztp-plugin.html).
|
||||
3. Downgrade Panorama to PAN-OS 10.1.
|
||||
4. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||
5. [Install the ZTP plugin](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/manage-firewalls/set-up-zero-touch-provisioning/install-the-ztp-plugin/install-the-ztp-plugin-on-panorama.html).
|
||||
6. Select **Panorama** > **Zero Touch Provisioning** and check (enable) **ZTP**.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-189057
|
||||
|
||||
```caveat
|
||||
HA configuration
|
||||
```
|
||||
|
||||
On the Panorama management server, Panorama enters a `non-functional` state due to `php.debug.log` life taking up too much space.
|
||||
|
||||
**Workaround:** Disable the debug flag for Panorama.
|
||||
|
||||
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
|
||||
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
|
||||
`https://<panorama_ip>/debug`
|
||||
3. Uncheck (disable) **Debug** or **Clear Debug**.
|
||||
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.
|
||||
|
||||
## PAN-189032
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
When the firewall has Advanced Routing enabled, an OSPFv3 interface configured with the p2mp link type causes the commit to fail.
|
||||
|
||||
## PAN-188956
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
After successful upgrade to PAN-OS 10.2, logging in to the firewall or Panorama web interface from the same Internet browser window or session from which the firewall or Panorama was upgraded displays the following error:
|
||||
|
||||
`Your login session has expired and you have been logged out for security reasons. Please log in again if you wish to continue.`
|
||||
|
||||
**Workaround:** The following are different ways to log in to the firewall or Panorama web interface after upgrading to PAN-OS 10.2.
|
||||
|
||||
- Close the browser and log in to the firewall or Panorama web interface from an entirely new browser session.
|
||||
- Clear your browser cache for the browser from which you upgraded the firewall or Panorama.
|
||||
- Log in to the firewall or Panorama web interface from the browser in Incognito mode.
|
||||
If you upgraded the firewall or Panorama from a browser in Incognito mode, close the browser and log in to the firewall or Panorama web interface from an entirely new browser session.
|
||||
- Log in to the firewall or Panorama web interface from a different browser than the one used to upgrade to PAN-OS.
|
||||
|
||||
## PAN-188904
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
|
||||
|
||||
## PAN-188489
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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** (**Panorama** > **Templates** > **Add Stack**) is enabled.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188064
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
|
||||
|
||||
## PAN-188052
|
||||
|
||||
Devices in FIPS-CC mode are unable to connect to servers utilizing ECDSA-based host keys that impacts exporting logs (**Device** > **Scheduled Log Export**), exporting configurations (**Device** > **Scheduled Config Export**), or the `scp export` command in the CLI.
|
||||
|
||||
**Workaround:** Use RSA-based host keys on the destination server.
|
||||
|
||||
## PAN-187846
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, a selective push (**Commit** > **Push to Devices** > **Push Changes Made By** and **Commit** > **Commit and Push** > **Commit and Push Changes Made By**) may push an incorrect configuration to managed firewalls causing the firewalls to display as *Out of Sync* if the Panorama pushed version for the Shared Policy and Template configuration (**Panorama** > **Managed Devices** > **Summary**) are 20 version or more older than the current local running configuration on Panorama.
|
||||
|
||||
To determine the current configuration version, select **Panorama** > **Config Audit**and expand the **Local Running config** menu to review the list of Panorama configuration versions.
|
||||
|
||||
**Workaround**: Push a more recent configuration to your managed firewalls before performing a selective push.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187234
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
|
||||
|
||||
## PAN-186913
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** 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.
|
||||
|
||||
**Workaround:** Validate device group configurations using one of the following methods.
|
||||
|
||||
- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
|
||||
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.
|
||||
|
||||
## PAN-186886
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
Individual configuration objects cannot be viewed when you commit selective configuration changes (**Commit** > **Commit Changes Made By**) on a multi-vsys firewall.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186262
|
||||
|
||||
The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.
|
||||
|
||||
**Workaround:** Reboot Panorama if it becomes unresponsive.
|
||||
|
||||
## PAN-186137
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
The management interface of the PA-3400 Series firewall incorrectly displays 10G port speed as an option. 10G speed is not supported on the PA-3400 Series firewall management port and cannot be configured.
|
||||
|
||||
## PAN-186134
|
||||
|
||||
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.
|
||||
|
||||
**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.
|
||||
|
||||
## PAN-185966
|
||||
|
||||
The `debug skip-cert-renewal-check-syslog yes` command is not available on Log Collector CLI to stop the Dedicated Log Collector from trying to renew the device certificate and displaying the following error:
|
||||
|
||||
`No valid device certificate found`
|
||||
|
||||
## PAN-185286
|
||||
|
||||
```caveat
|
||||
PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||
|
||||
## PAN-184708
|
||||
|
||||
```caveat
|
||||
Panorama managed firewalls
|
||||
```
|
||||
|
||||
Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:
|
||||
|
||||
- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
|
||||
- A scheduled report contains only a SaaS Application Usage Report.
|
||||
|
||||
**Workaround:** To receive a scheduled report email for all other PDF report types:
|
||||
|
||||
1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
|
||||
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
|
||||
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
|
||||
3. **Commit**.
|
||||
() Select **Commit** > **Commit and Push**
|
||||
|
||||
## PAN-184702
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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**).
|
||||
|
||||
**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).
|
||||
|
||||
## PAN-184474
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183567
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, you must download and install the ZTP Plugin 2.0 after successful upgrade to PAN-OS 10.2. After upgrade to PAN-OS 10.2, the `show plugins installed` command does not display the ZTP plugin until you install ZTP Plugin 2.0.
|
||||
|
||||
**Workaround:** After Panorama successfully upgrades to PAN-OS 10.2, manually download and install the ZTP Plugin 2.0.
|
||||
|
||||
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||
2. Select **Panorama** > **Plugins** and search for the `ztp` plugin.
|
||||
3. **Download** and **Install** ZTP Plugin 2.0.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-182734
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||
|
||||
## PAN-182492
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
The WildFire analysis report cannot be viewed from the firewall WildFire submission log entry page.
|
||||
|
||||
**Workaround**: You can retrieve the Wildfire analysis reports through the WildFire API or the WildFire portal.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-179420
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, a selective push (**Commit** > **Push to Devices** > **Push Changes Made By** and **Commit** > **Commit and Push** > **Commit and Push Changes Made By** to managed firewalls fails if you rename an existing device group, template, or template stack that was already pushed to your managed firewalls and you selectively committed specific configuration objects from the renamed device group, template, or template stack.
|
||||
|
||||
**Workaround:** After you rename the existing device group, template, or template stack, **Push** (**Commit** > **Push to Devices** all configuration changes for the named device group, template, or template stack.
|
||||
|
||||
## PAN-178195
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
The URL filtering logs generated by traffic analyzed by Advanced URL filtering cloud inline categorization does not display the name of the URL.
|
||||
|
||||
## PAN-177455
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-176693
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
The Activity (ACT) LEDs on the RJ-45 ports of the M-300 and M-700 appliances do not blink while processing network traffic.
|
||||
|
||||
## PAN-176156
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
Executing `show running resource-monitor` with the `ingress-backlogs` option produces the following server error: `Dataplane is not up or invalid target-dp(*.dp*)`.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-172132
|
||||
|
||||
```caveat
|
||||
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
QoS fails to run on a tunnel interface (for example, tunnel.1).
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-171069
|
||||
|
||||
Local Log Collectors for Panorama management servers in active/passive high availability (HA) configuration cannot be added to the same Collector Group (**Panorama** > **Collector Groups**).
|
||||
|
||||
**Workaround:** Before you upgrade your Panorama servers to PAN-OS 10.1.0, configure HA (**Panorama** > **High Availability**), add the local Log Collectors of the HA peers to the same Collector Group, and upgrade to PAN 10.1.0.
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
|
||||
## PAN-163676
|
||||
|
||||
Next-Gen Firewalls are unable to connect to a syslog server when the certificates required to connect to the syslog server are part of a Certificate Profile (**Device** > **Certificate Management** > **Certificate Profile**) if the **Use OCSP** setting is enabled to check the revocation status of certificates.
|
||||
|
||||
**Workaround:** Enable **Use CRL** to check the revocation status of certificates in the Certificate Profile.
|
||||
@@ -0,0 +1,643 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.10
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-280196
|
||||
|
||||
After generating hipmatch/userid logs, the hipmatch logs written counter is missing from debug log-receiver statistics. This causes the firewall to match a HIP object but not on the HIP profile that contained the object.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.10-h2
|
||||
```
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-286306
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||
|
||||
## PAN-286255
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.10-h17
|
||||
```
|
||||
|
||||
When a firewall receives an unexpected termination request for certain SSL sessions , NGFW dataplane might experience a slow buffer resource leak.
|
||||
|
||||
**Workaround**: Disable accumulation proxy on the NGFW.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-282236
|
||||
|
||||
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279746
|
||||
|
||||
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||
|
||||
## PAN-275077
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
DNS Security intermittently logs malicious domain URLs as alert instead of taking a **sinkhole** action, even when configured to sinkhole malicious DNS domains.
|
||||
|
||||
## PAN-270549
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h2 through PAN-OS 10.2.10-h12) This issue is now resolved. See PAN-OS 10.2.10-h14 Addressed Issues.
|
||||
```
|
||||
|
||||
Some TLS connections are not handled correctly leading to an instability in the dataplane of PAN-OS.
|
||||
|
||||
## PAN-269106
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
When using a cloud-based ML detection engine (MICA), the `wifclient` might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||
|
||||
**Workaround**: Disable CRL using the following CLI command:`debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False`
|
||||
|
||||
## PAN-269052
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
Traffic might be blocked by a URL Filtering profile that isn't associated with the Security policy rule that the traffic matches.
|
||||
|
||||
## PAN-268823
|
||||
|
||||
```caveat
|
||||
PA-5250 firewall only
|
||||
```
|
||||
|
||||
Applying filters under **Monitor** > **Log Display** either causes the logs to load slowly or not load at all.
|
||||
|
||||
## PAN-268815
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||
```
|
||||
|
||||
When using IoT Security, the `wifclient` might exit multiple times causing the firewall to reboot.
|
||||
|
||||
**Workaround**: Uninstall the IoT Security license and disable **Enable enhanced application logging** (**Device** > **Management** > **Cloud Logging** > **Cloud Logging Settings**).
|
||||
|
||||
## PAN-268260
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
On hardware firewalls where, when SSL decryption was enabled on layer 2, vwire, TAP, VLAN deployments, and Client Hello messages spanned multiple TCP segments, some SSL decryption sessions failed.
|
||||
|
||||
## PAN-267671
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
Exporting reports in PDF or CSV format and processing hourly scheduled report results can potentially trigger memory leaks. As a result, this can lead to process crashes and firewall reboots.
|
||||
|
||||
## PAN-266900
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)
|
||||
```
|
||||
|
||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||
|
||||
## PAN-263226
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h2 and 10.2.10-h3 only)
|
||||
```
|
||||
|
||||
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||
|
||||
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-261429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||
```
|
||||
|
||||
The command `show auth radius-require-msg-authentic` might return no output.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259997
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
On PA-3410, PA-3420, and PA-3430 firewalls, the install fails when upgrading from PAN-OS 10.2.3-h3 and later 10.2 releases to PAN-OS 10.2.10 due the number of configured vsys zones exceeding the zone limit in PAN-OS 10.2.10.
|
||||
|
||||
**Workaround:** Before installing PAN-OS 10.2.10, reduce the number of security zones to 40 zones or fewer for PA-3410 and PA-3420 firewalls, and to 100 zones or fewer for PA-3430 firewalls.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-259733
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10-h2 Addressed Issues.
|
||||
```
|
||||
|
||||
Custom reports created in PAN-OS are not deleted as expected, resulting in high memory use by the reportd process. This can lead to issues, such as out-of-memory conditions, content installation failures, and unexpected firewall reboots.
|
||||
|
||||
## PAN-259344
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
Performing a configuration commit on a firewall, either locally or from Panorama, causes a memory leak by the configd process and results in an out-of-memory (OOM) condition.
|
||||
|
||||
## PAN-258570
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.10-h9 only)This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
The varrcvr process might progressively use more memory resulting in unexpected reboots when WildFire file forwarding is handling PE files.
|
||||
|
||||
## PAN-257957
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.12 Addressed Issues.Affects 10.2.10-h3 and later 10.2 releases.
|
||||
```
|
||||
|
||||
If you enable FIPS-CC mode and use the PAP or CHAP authentication methods for your RADIUS server, the authd process may restart unexpectedly. To avoid this issue, use one of the following workarounds:
|
||||
|
||||
- If you use PAN-OS 10.2.10-h3, 10.2.11, or an earlier version, configure the RADIUS server so that it does not send the message authenticator back to client.
|
||||
- Use other protocols, such as LDAP, Kerberos, TACACS+, SAML, RADIUS EAP, instead of RADIUS PAP or CHAP.
|
||||
- Change from FIPS mode to normal mode.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-226361
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10-h7 Addressed Issues.
|
||||
```
|
||||
|
||||
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,528 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.11
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279746
|
||||
|
||||
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||
|
||||
## PAN-265336
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11-h2 Addressed Issues.
|
||||
```
|
||||
|
||||
Copper ports flap when generating a technical support file, executing telemetry, or retrieving port status using a Management Data Input/Output (MDIO) read.
|
||||
|
||||
## PAN-264680
|
||||
|
||||
```caveat
|
||||
PA-220 firewalls only
|
||||
```
|
||||
|
||||
**Device** > **Setup** is not displayed when the Enterprise Data Loss Prevention (E-DLP) plugin is installed.
|
||||
|
||||
**Workaround:** Uninstall the Enterprise DLP plugin.
|
||||
|
||||
1. Log in to the firewall web interface.
|
||||
2. Select **Device** > **Plugins**.
|
||||
3. Search for `dlp`.
|
||||
4. **Uninstall**.
|
||||
|
||||
## PAN-264580
|
||||
|
||||
```caveat
|
||||
PA-3400 Series firewalls only
|
||||
```
|
||||
|
||||
Upgrading to PAN-OS 10.2.11 results in the following error: `Target image validation failed with error invalid literal for int() with base 10`.
|
||||
|
||||
## PAN-263226
|
||||
|
||||
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||
|
||||
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-261429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||
```
|
||||
|
||||
The command `show auth radius-require-msg-authentic` might return no output.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-257957
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.12 Addressed Issues.Affects 10.2.11-h1 and later 10.2 releases.
|
||||
```
|
||||
|
||||
If you enable FIPS-CC mode and use the PAP or CHAP authentication methods for your RADIUS server, the authd process may restart unexpectedly. To avoid this issue, use one of the following workarounds:
|
||||
|
||||
- If you use PAN-OS 10.2.10-h3, 10.2.11, or an earlier version, configure the RADIUS server so that it does not send the message authenticator back to client.
|
||||
- Use other protocols, such as LDAP, Kerberos, TACACS+, SAML, RADIUS EAP, instead of RADIUS PAP or CHAP.
|
||||
- Change from FIPS mode to normal mode.
|
||||
|
||||
## PAN-257601
|
||||
|
||||
```resolved
|
||||
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
|
||||
```
|
||||
|
||||
Networking cards can experience an internal link fault, causing path monitoring failure on the Dataplane Processing Card (DPC).
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in Traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-226361
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11-h4 Addressed Issues.
|
||||
```
|
||||
|
||||
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling the [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a JavaScript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
After triggering a soft reboot on an M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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 an M-700 appliance.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific websites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,467 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.12
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279746
|
||||
|
||||
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-261429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||
```
|
||||
|
||||
The command `show auth radius-require-msg-authentic` might return no output.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-257601
|
||||
|
||||
```resolved
|
||||
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
|
||||
```
|
||||
|
||||
Networking cards can experience an internal link fault, causing path monitoring failure on the Dataplane Processing Card (DPC).
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,622 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.13
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-297775
|
||||
|
||||
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||
|
||||
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-293673
|
||||
|
||||
When the firewall generates a high volume of logs and attempts to export these logs to an FTP server, it may consume excessive memory leading to all PAN-OS processes crashing.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-289102
|
||||
|
||||
```caveat
|
||||
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||
```
|
||||
|
||||
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||
|
||||
## PAN-288930
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||
```
|
||||
|
||||
When ACE (App-ID Cloud Engine) is enabled, traffic from cloud applications might intermittently match an incorrect **cloud-apps** policy rule.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-287056
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||
|
||||
## PAN-286306
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||
|
||||
## PAN-286255
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.13-h5 This issue is now resolved. See PAN-OS 10.2.13-h7 Addressed Issues.
|
||||
```
|
||||
|
||||
When a firewall receives an unexpected termination request for certain SSL sessions , NGFW dataplane might experience a slow buffer resource leak.
|
||||
|
||||
**Workaround**: Disable accumulation proxy on the NGFW.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-285941
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||
```
|
||||
|
||||
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-284066
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
After an upgrade, the `IF-MIB::ifInErrors` SNMP polled values display errors that don't match the results from the `show interface` CLI command.
|
||||
|
||||
## PAN-283467
|
||||
|
||||
```caveat
|
||||
PA-3400 Series firewalls only
|
||||
```
|
||||
|
||||
The firewall might unexpectedly reboot and enter maintenance mode due to a ctd-agent out-of-memory (OOM) condition when undergoing advanced services load testing with a high volume of IoT EAL log forwarding.
|
||||
|
||||
**Workaround:** Limit the number of EAL logs generated by the firewall using the following CLI command: `debug iot eal key-value EAL_PENDING_BYTES=1000`.
|
||||
|
||||
## PAN-283331
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
Selective pushes to managed devices fail when the **User ID Master Device** is configured.
|
||||
|
||||
## PAN-282236
|
||||
|
||||
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279901
|
||||
|
||||
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||
|
||||
- The segmented Client Hello packets arrive out-of-order
|
||||
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||
- The first segment of the Client Hello packets is less than 5 bytes
|
||||
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||
|
||||
## PAN-279746
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h1 through PAN-OS 10.2.13-h4) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||
```
|
||||
|
||||
An SSL/TLS Client Hello may not be transmitted out of the firewall if the Client Hello arrives in multiple TCP segments and the traffic is not subject to SSL decryption (for example, SMTP over SSL).
|
||||
|
||||
## PAN-279604
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h3 only) This issue is now resolved. See PAN-OS 10.2.13-h4 Addressed Issues.
|
||||
```
|
||||
|
||||
The scheduled SaaS application usage reports are incorrectly generated and only the login page appears instead of the intended report content.
|
||||
|
||||
## PAN-275077
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
DNS Security intermittently logs malicious domain URLs as alert instead of taking a **sinkhole** action, even when configured to sinkhole malicious DNS domains.
|
||||
|
||||
## PAN-270849
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
The configd process leaks a small amount of memory in every commit.
|
||||
|
||||
## PAN-269106
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
When using a cloud-based ML detection engine (MICA), the `wifclient` might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||
|
||||
**Workaround**: Disable CRL using the following CLI command:`debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False`
|
||||
|
||||
## PAN-269052
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h4 and later 10.2.13 releases) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic might be blocked by a URL Filtering profile that isn't associated with the Security policy rule that the traffic matches.
|
||||
|
||||
## PAN-268815
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||
```
|
||||
|
||||
When using IoT Security, the `wifclient` might exit multiple times causing the firewall to reboot.
|
||||
|
||||
**Workaround**: Uninstall the IoT Security license and disable **Enable enhanced application logging** (**Device** > **Management** > **Cloud Logging** > **Cloud Logging Settings**).
|
||||
|
||||
## PAN-266900
|
||||
|
||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-261429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||
```
|
||||
|
||||
The command `show auth radius-require-msg-authentic` might return no output.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,470 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.15
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-289102
|
||||
|
||||
```caveat
|
||||
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||
```
|
||||
|
||||
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-287056
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||
|
||||
## PAN-286306
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285941
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||
```
|
||||
|
||||
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-284066
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||
```
|
||||
|
||||
After an upgrade, the `IF-MIB::ifInErrors` SNMP polled values display errors that don't match the results from the `show interface` CLI command.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279901
|
||||
|
||||
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||
|
||||
- The segmented Client Hello packets arrive out-of-order
|
||||
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||
- The first segment of the Client Hello packets is less than 5 bytes
|
||||
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||
|
||||
## PAN-266900
|
||||
|
||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,369 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.16
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-297775
|
||||
|
||||
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||
|
||||
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-293673
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h4 Addressed Issues
|
||||
```
|
||||
|
||||
When the firewall generates a high volume of logs and attempts to export these logs to an FTP server, it may consume excessive memory leading to all PAN-OS processes crashing.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-287056
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||
|
||||
## PAN-286306
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-279901
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.16 and PAN-OS 10.2.16-h1)
|
||||
```
|
||||
|
||||
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||
|
||||
- The segmented Client Hello packets arrive out-of-order
|
||||
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||
- The first segment of the Client Hello packets is less than 5 bytes
|
||||
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,357 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.18
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-266900
|
||||
|
||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
@@ -0,0 +1,776 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.1
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-228273
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||
|
||||
## PAN-227344
|
||||
|
||||
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||
|
||||
## PAN-225337
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||
|
||||
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||
|
||||
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||
|
||||
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||
|
||||
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||
|
||||
## PAN-223488
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-222253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-221015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||
|
||||
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||
|
||||
`admin>``debug elasticsearch es-restart optional all`
|
||||
|
||||
## PAN-219644
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||
|
||||
## PAN-218521
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-215778
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||
|
||||
`504 Gateway timeout`
|
||||
|
||||
## PAN-215082
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208325
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||
|
||||
- M-300 and M-700
|
||||
- PA-410 Firewall
|
||||
- PA-440, PA-450, and PA-460 Firewalls
|
||||
- PA-3400 Series
|
||||
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||
- PA-5450 Firewall
|
||||
|
||||
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||
|
||||
`admin>``request certificate fetch`
|
||||
|
||||
## PAN-207629
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.
|
||||
|
||||
## PAN-206268
|
||||
|
||||
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.
|
||||
|
||||
## PAN-206253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-206243
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.
|
||||
|
||||
## PAN-205187
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.
|
||||
|
||||
`admin>``request restart software`
|
||||
|
||||
## PAN-204663
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-201855
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting 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 Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||
|
||||
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||
|
||||
## PAN-199557
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||
|
||||
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||
|
||||
## PAN-197097
|
||||
|
||||
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-194826
|
||||
|
||||
```caveat
|
||||
WF-500 appliance only
|
||||
```
|
||||
|
||||
System log forwarding does not work over a TLS connection.
|
||||
|
||||
## PAN-194708
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
URL filtering logs (**Monitor** > **Logs** > **URL Filtering**) 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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-193251
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-192403
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.
|
||||
|
||||
## PAN-190735
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
Certain webpages that use chunked-encoded data transfers might not load properly when analyzed by Advanced URL Filtering cloud inline categorization.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-190435
|
||||
|
||||
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||
|
||||
## PAN-189425
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) 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)`
|
||||
|
||||
## PAN-189395
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
Running any version of PAN-OS 10.2.1 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.
|
||||
|
||||
## PAN-189380
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
|
||||
2. Restart the firewall.
|
||||
`admin>` `request restart system`
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-189057
|
||||
|
||||
```caveat
|
||||
HA configuration
|
||||
```
|
||||
|
||||
On the Panorama management server, Panorama enters a `non-functional` state due to `php.debug.log` life taking up too much space.
|
||||
|
||||
**Workaround:** Disable the debug flag for Panorama.
|
||||
|
||||
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
|
||||
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
|
||||
`https://<panorama_ip>/debug`
|
||||
3. Uncheck (disable) **Debug** or **Clear Debug**.
|
||||
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.
|
||||
|
||||
## PAN-188904
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
|
||||
|
||||
## PAN-188489
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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** (**Panorama** > **Templates** > **Add Stack**) is enabled.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188064
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187429
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187234
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
|
||||
|
||||
## PAN-186913
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** 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.
|
||||
|
||||
**Workaround:** Validate device group configurations using one of the following methods.
|
||||
|
||||
- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
|
||||
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186262
|
||||
|
||||
The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.
|
||||
|
||||
**Workaround:** Reboot Panorama if it becomes unresponsive.
|
||||
|
||||
## PAN-186134
|
||||
|
||||
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.
|
||||
|
||||
**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.
|
||||
|
||||
## PAN-185286
|
||||
|
||||
```caveat
|
||||
PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||
|
||||
## PAN-184708
|
||||
|
||||
```caveat
|
||||
Panorama managed firewalls
|
||||
```
|
||||
|
||||
Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:
|
||||
|
||||
- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
|
||||
- A scheduled report contains only a SaaS Application Usage Report.
|
||||
|
||||
**Workaround:** To receive a scheduled report email for all other PDF report types:
|
||||
|
||||
1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
|
||||
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
|
||||
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
|
||||
3. **Commit**.
|
||||
() Select **Commit** > **Commit and Push**
|
||||
|
||||
## PAN-184702
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
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**).
|
||||
|
||||
**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).
|
||||
|
||||
## PAN-184474
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-182734
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-176156
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues
|
||||
```
|
||||
|
||||
Executing `show running resource-monitor` with the `ingress-backlogs` option produces the following server error: `Dataplane is not up or invalid target-dp(*.dp*)`.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-172132
|
||||
|
||||
```caveat
|
||||
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
|
||||
```
|
||||
|
||||
QoS fails to run on a tunnel interface (for example, tunnel.1).
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
@@ -0,0 +1,632 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.4
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-228273
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||
|
||||
## PAN-227344
|
||||
|
||||
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||
|
||||
## PAN-227342
|
||||
|
||||
```caveat
|
||||
PA-7000 Series firewalls only
|
||||
```
|
||||
|
||||
In an Active/Active High Availability (HA) setup, enabling hardware offload can result in web traffic being blocked.
|
||||
|
||||
## PAN-225337
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||
|
||||
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||
|
||||
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||
|
||||
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||
|
||||
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||
|
||||
## PAN-223488
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-222253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-221015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||
|
||||
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||
|
||||
`admin>``debug elasticsearch es-restart optional all`
|
||||
|
||||
## PAN-220180
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||
|
||||
## PAN-219644
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||
|
||||
## PAN-218521
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-216821
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
The `reportd` process crashes after you successfully upgrade an M-200 appliance to PAN-OS 10.2.4.
|
||||
|
||||
## PAN-215778
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||
|
||||
`504 Gateway timeout`
|
||||
|
||||
## PAN-215082
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212978
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.4-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
The Palo Alto Networks firewall stops responding when executing an SD-WAN debug operational CLI command.
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-210366
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-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-functional` state and generate a system log (**Monitor** > **Logs** > **System**) with the following message:
|
||||
|
||||
`High root partition usage: going to state Non-Functional`
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-208325
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||
|
||||
- M-300 and M-700
|
||||
- PA-410 Firewall
|
||||
- PA-440, PA-450, and PA-460 Firewalls
|
||||
- PA-3400 Series
|
||||
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||
- PA-5450 Firewall
|
||||
|
||||
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||
|
||||
`admin>``request certificate fetch`
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||
|
||||
## PAN-201855
|
||||
|
||||
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting 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 Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||
|
||||
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||
|
||||
## PAN-199557
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||
|
||||
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||
|
||||
## PAN-198708
|
||||
|
||||
On the Panorama management server, the `File Type` field does not display any data when you view the Detailed Log View in the Data Filtering log (**Monitor** > **Logs** > **Data Filtering** > **<select log>** > **DLP**).
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-196146
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-190435
|
||||
|
||||
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-185286
|
||||
|
||||
```caveat
|
||||
PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-182734
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
|
||||
## PAN-160633
|
||||
|
||||
```caveat
|
||||
PA-3200 Series, PA-5200 Series, and PA-7000 Series firewalls only
|
||||
```
|
||||
|
||||
The dataplane restarts repeatedly due to internal path monitoring failures until a power cycle.
|
||||
@@ -0,0 +1,639 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.6
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-244648
|
||||
|
||||
```caveat
|
||||
PA-5200 Series firewalls only
|
||||
```
|
||||
|
||||
After a factory reset, the firewall may get stuck in maintenance mode and be unable to load the boot image. The firewall fails to enable FIPS-CC mode during this time.
|
||||
|
||||
**Workaround:** The following workaround allows the firewall to boot in normal mode but does not apply to FIPS-CC mode. Attempting to enable FIPS-CC mode after using this workaround will cause the firewall to reboot and re-enter maintenace mode.
|
||||
|
||||
1. Enter maintenance mode.
|
||||
2. Select **Disk Image** > **Advanced Options**.
|
||||
3. Select **Bootstrap** with the options `panos-10.2.8`, `maint`, and `maint`.
|
||||
4. Select **Bootstrap** with the options `panos-10.2.8`, `sysroot0`, and `panos`.
|
||||
5. Select **Bootstrap** with the option `sysroot0`.
|
||||
6. Select **Reboot**.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-234929
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
|
||||
|
||||
## PAN-228515
|
||||
|
||||
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||
|
||||
## PAN-228273
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||
|
||||
## PAN-227344
|
||||
|
||||
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||
|
||||
## PAN-225337
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||
|
||||
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||
|
||||
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||
|
||||
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||
|
||||
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-227368
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
The GlobalProtect app cannot connect to a portal or gateway and GlobalProtect Clientless VPN users cannot access applications if authentication takes longer than 20 seconds.
|
||||
|
||||
**Workaround:** Increase the TCP handshake timeout to the maximum value of 60 seconds.
|
||||
|
||||
## PAN-226768
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in `Connecting` stage after authentication and the GlobalProtect log displays the error message, **User is not in allow list**. This happens when the app is restarted or when the app tries to reconnect after disconnection.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-223488
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||
|
||||
## PAN-223457
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-222418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
|
||||
|
||||
## PAN-222253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-221857
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: **Username from SAML SSO response is different from the input.**.
|
||||
|
||||
## PAN-221126
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
Email server profiles (**Device** > **Server Profiles** > **Email** and **Panorama** > **Server Profiles** > **Email**) to forward logs as email notifications are not forwarded in a readable format.
|
||||
|
||||
**Workaround:** Use a **Custom Log Format** to forward logs as email notifications in a readable format.
|
||||
|
||||
## PAN-221015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||
|
||||
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||
|
||||
`admin>``debug elasticsearch es-restart optional all`
|
||||
|
||||
## PAN-220180
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||
|
||||
## PAN-219644
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||
|
||||
## PAN-218521
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-215082
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-196146
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-193004
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||
```
|
||||
|
||||
The Panorama management server fails to delete old IP Tag data. This causes the `/opt/pancfg` partition to reach maximum capacity which impacts Panorama performance.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-185286
|
||||
|
||||
```caveat
|
||||
PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
@@ -0,0 +1,609 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.7
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-273730
|
||||
|
||||
```caveat
|
||||
PA-7000 Series only
|
||||
```
|
||||
|
||||
The web interface is unresponsive after upgrading to PAN-OS 10.2.7-h18. The following error is generated: `PHP Fatal error: require(): Failed opening required`
|
||||
|
||||
**Workaround:** Use the CLI to downgrade or upgrade to another version.
|
||||
|
||||
## PAN-262263
|
||||
|
||||
```caveat
|
||||
PA-3400 and PA-5400 Series firewalls
|
||||
```
|
||||
|
||||
The links on the firewall's RJ-45 ports may go up and down additional times during a reboot, causing unexpected downtime.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-244673
|
||||
|
||||
Upgrading a flexible-vCPU VM-Series firewall HA deployment from 10.1.x directly to 10.2.3 or later causes the active HA peer to become unresponsive. In this scenario, the upgraded firewall then becomes the active peer.
|
||||
|
||||
**Workaround**: Upgrade the VM-Series firewalls to PAN-OS 10.2.2 before upgrading to the latest PAN-OS 10.2.x version.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-242910
|
||||
|
||||
```caveat
|
||||
PAN-OS 10.2.7, 10.2.7-h1, and 10.2.7-h3 only
|
||||
```
|
||||
|
||||
On the Panorama management server, Panorama administrators (**Panorama** > **Administrators**) that are assigned a custom Panorama admin role (**Panorama** > **Admin Roles**) with **Push All Changes** enabled are unable to push configuration changes to managed firewalls when **Managed Devices** and **Push For Other Admins** are disabled.
|
||||
|
||||
## PAN-242837
|
||||
|
||||
Default login credentials and SSH fail after enabling FIPS-CC Mode on a firewall or Panorama after converting through the Maintenance Recovery Tool (MRT). The firewall or Panorama becomes stuck and requires a factory reset to recover.
|
||||
|
||||
## PAN-242561
|
||||
|
||||
On the PAN-OS 10.2.7-h3 version, GlobalProtect tunnel might disconnect shortly after being established when SSL is used as a transport protocol.
|
||||
|
||||
**Workaround**: Disable Internet Protocol version 6 (TCP/IPv6) on the PANGP Virtual Network Adapter.
|
||||
|
||||
## PAN-238769
|
||||
|
||||
FIPS-CC VM only. Upgrading to 10.1.10-h2 or 10.1.11 will change all locally created security Policy actions to Deny. Re-load the back-up config taken before upgrading or the last version to get the previous config back. Also, Unable to login to FIPSCC Mode devices with default credentials after converting the mode for 10.1.12 release , 10.2.7 release , 11.1.0 , 11.1.1, 11.0.3 versions.
|
||||
|
||||
## PAN-234929
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
|
||||
|
||||
## PAN-228515
|
||||
|
||||
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||
|
||||
## PAN-228273
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||
|
||||
## PAN-227344
|
||||
|
||||
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-226768
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in `Connecting` stage after authentication and the GlobalProtect log displays the error message, **User is not in allow list**. This happens when the app is restarted or when the app tries to reconnect after disconnection.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-223457
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-222418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
|
||||
|
||||
## PAN-222253
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-221857
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: **Username from SAML SSO response is different from the input.**.
|
||||
|
||||
## PAN-221033
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The firewall is responding to an ARP request for an IP address in the firewall's NAT address pool when that IP address isn't in the same subnet as the IP address of the ingress interface.
|
||||
|
||||
## PAN-220180
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||
|
||||
## PAN-219644
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-215082
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-196146
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||
```
|
||||
|
||||
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-185286
|
||||
|
||||
```caveat
|
||||
PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
@@ -0,0 +1,525 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.8
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.8-h10
|
||||
```
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-287056
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-255868
|
||||
|
||||
```caveat
|
||||
PA-3400 Series firewalls only
|
||||
```
|
||||
|
||||
After enabling kernel data collection during a silent reboot, the firewall fails and reboots to maintenance mode.
|
||||
|
||||
**Workaround:** To recover the firewall, initiate a reboot from maintenance mode.
|
||||
|
||||
## PAN-251895
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
When Inline Cloud Analysis features are enabled, the firewall experiences a slow packet buffer leak, resulting in poor performance and dropped traffic.
|
||||
|
||||
**Workaround:** Disable WildFire Inline Cloud Analysis and Advanced Threat Prevention Inline Cloud Analysis on the firewall.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-243951
|
||||
|
||||
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||
|
||||
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||
|
||||
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||
*request high-availability sync-to-remote running-config*
|
||||
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||
|
||||
## PAN-242910
|
||||
|
||||
On the Panorama management server, Panorama administrators (**Panorama** > **Administrators**) that are assigned a custom Panorama admin role (**Panorama** > **Admin Roles**) with **Push All Changes** enabled are unable to push configuration changes to managed firewalls when **Managed Devices** and **Push For Other Admins** are disabled.
|
||||
|
||||
## PAN-242627
|
||||
|
||||
On the Panorama management server, selective configuration pushes fail with the following error message even when a full configuration push from Panorama was previously performed:Failed to generate selective push configuration. Schema validation failed. Please try a full push
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234408
|
||||
|
||||
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-228515
|
||||
|
||||
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||
|
||||
## PAN-226361
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.8-h13 Addressed Issues.
|
||||
```
|
||||
|
||||
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
@@ -0,0 +1,500 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 10.2.9
|
||||
source: common-crawl
|
||||
crawl: CC-MAIN-2026-12
|
||||
---
|
||||
|
||||
## WF500-5854
|
||||
|
||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) 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**.
|
||||
|
||||
## WF500-5843
|
||||
|
||||
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||
|
||||
## WF500-5840
|
||||
|
||||
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||
|
||||
## WF500-5823
|
||||
|
||||
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.
|
||||
|
||||
## WF500-5781
|
||||
|
||||
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||
|
||||
## WF500-5754
|
||||
|
||||
In WildFire appliance clusters, issuing the `show cluster controller` CLI 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).
|
||||
|
||||
## WF500-5632
|
||||
|
||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls in Microsoft Azure environments only
|
||||
```
|
||||
|
||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||
|
||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||
|
||||
- D3_v2/DS3_v2 to D8ds_v5
|
||||
- D4_v2/DS4_v2 to D8ds_v5
|
||||
- D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-295255
|
||||
|
||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.9-h7
|
||||
```
|
||||
|
||||
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||
|
||||
## PAN-291716
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||
```
|
||||
|
||||
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||
```
|
||||
|
||||
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||
```
|
||||
|
||||
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
```caveat
|
||||
Firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 10.2.9-h9
|
||||
```
|
||||
|
||||
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||
|
||||
## PAN-286231
|
||||
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
- When you run **Commit and Push** operations as a single action.
|
||||
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||
- Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||
```
|
||||
|
||||
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||
|
||||
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||
|
||||
## PAN-284073
|
||||
|
||||
The firewall web interface becomes inaccessible and commits fail.
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||
|
||||
## PAN-281370
|
||||
|
||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||
```
|
||||
|
||||
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||
|
||||
## PAN-263226
|
||||
|
||||
```caveat
|
||||
(PAN-OS 10.2.9-h9 only)
|
||||
```
|
||||
|
||||
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||
|
||||
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||
|
||||
## PAN-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-251895
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
When Inline Cloud Analysis features are enabled, the firewall experiences a slow packet buffer leak, resulting in poor performance and dropped traffic.
|
||||
|
||||
**Workaround:**Disable WildFire Inline Cloud Analysis and Advanced Threat Prevention Inline Cloud Analysis on the firewall.
|
||||
|
||||
## PAN-251639
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See. PAN-OS 10.2.9-h9 Addressed Issues. This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
An out of memory condition might occur due to a memory leak in the varrcvr process when a Wildfire Analysis security profile is enabled.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||
|
||||
- `db-serialno can be at most 40 characters`
|
||||
- `db-serialno is invalid`
|
||||
|
||||
**Workaround:**
|
||||
|
||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||
|
||||
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||
|
||||
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-223365
|
||||
|
||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||
|
||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||
|
||||
`admin``debug elasticsearch es-restart all`
|
||||
|
||||
## PAN-229865
|
||||
|
||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||
|
||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||
|
||||
## PAN-226361
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.9-h14 Addressed Issues.
|
||||
```
|
||||
|
||||
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||
|
||||
## PAN-223677
|
||||
|
||||
```caveat
|
||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||
```
|
||||
|
||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||
|
||||
## PAN-222586
|
||||
|
||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||
|
||||
## PAN-221775
|
||||
|
||||
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||
|
||||
## PAN-217307
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||
|
||||
`log-start eq no`
|
||||
|
||||
`log-end eq no`
|
||||
|
||||
`log-end eq yes`
|
||||
|
||||
## PAN-213746
|
||||
|
||||
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||
|
||||
## PAN-213119
|
||||
|
||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||
|
||||
`show -> dis-block-table is unexpected`
|
||||
|
||||
## PAN-212889
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||
```
|
||||
|
||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when 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.
|
||||
|
||||
## PAN-212533
|
||||
|
||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||
|
||||
## PAN-211531
|
||||
|
||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||
|
||||
## PAN-209288
|
||||
|
||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||
|
||||
## PAN-208622
|
||||
|
||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||
|
||||
## PAN-204689
|
||||
|
||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||
|
||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||
|
||||
## PAN-196758
|
||||
|
||||
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 **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||
|
||||
## PAN-196504
|
||||
|
||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||
|
||||
## PAN-194996
|
||||
|
||||
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.
|
||||
|
||||
## PAN-194519
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||
|
||||
## PAN-194515
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||
|
||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||
|
||||
## PAN-194424
|
||||
|
||||
```caveat
|
||||
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:
|
||||
|
||||
`debug software restart process log-receiver`
|
||||
|
||||
## PAN-194202
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-190727
|
||||
|
||||
```caveat
|
||||
PA-5450 firewall only
|
||||
```
|
||||
|
||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||
|
||||
## PAN-189111
|
||||
|
||||
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||
|
||||
## PAN-189076
|
||||
|
||||
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.
|
||||
|
||||
## PAN-188358
|
||||
|
||||
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.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) 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](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||
|
||||
## PAN-187643
|
||||
|
||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||
|
||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||
|
||||
## PAN-187612
|
||||
|
||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||
|
||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||
|
||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||
|
||||
`admin > request plugins dlp reset`
|
||||
|
||||
## PAN-187407
|
||||
|
||||
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 lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-187370
|
||||
|
||||
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.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||
|
||||
## PAN-186282
|
||||
|
||||
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.
|
||||
|
||||
## PAN-184406
|
||||
|
||||
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.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
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.
|
||||
|
||||
## PAN-181823
|
||||
|
||||
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.
|
||||
|
||||
## PAN-180661
|
||||
|
||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||
|
||||
## PAN-180104
|
||||
|
||||
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.
|
||||
|
||||
## PAN-178194
|
||||
|
||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is 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:
|
||||
|
||||
- Define URL exceptions for specific web sites—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||
|
||||
- Configuration settings for each inline ML model—
|
||||
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||
|
||||
## PAN-177455
|
||||
|
||||
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.
|
||||
|
||||
## PAN-175915
|
||||
|
||||
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.
|
||||
|
||||
## PAN-174982
|
||||
|
||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||
|
||||
## PAN-172274
|
||||
|
||||
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`.
|
||||
|
||||
## PAN-171938
|
||||
|
||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||
|
||||
## PAN-164885
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||
```
|
||||
|
||||
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||
Reference in New Issue
Block a user