Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the Don't Fragment (DF) bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.

Workaround: Allow fragmenting packets with DF bit set (debug dataplane set ip4-ignore-df yes).

Strata Logging Service (SLS) log-forwarding streams intermittently show as inactive. When checking the status of log-forwarding connections, one or more streams are reported as inactive. Restarting the log-receiver process temporarily resolves the issue, but the streams become inactive again after approximately 1-2 hours. This intermittent inactivity results in log loss.

When Advanced DNS Security is enabled and experiences unusually high loads, DNS traffic sessions may be impacted, resulting in DNS resolution failures. Traffic logs for these sessions show an end-reason of resources-unavailable.

Workaround: Disable Advanced DNS Security telemetry (DeviceSetupContent-IDAdvanced DNS Security and uncheck Telemetry Enable).

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.

Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.

Workaround: Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.

Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.

On Log Collectors, the Elasticsearch process might fluctuate between green and red states, causing log collection interruptions. This issue occurs when the number of shards exceeds the supported threshold of 1,000 shards per Elasticsearch instance.

After upgrading multi-vsys firewalls, the sequence of the virtual system IDs (vsys ID) changes causing auto-commit failures with validation errors. This occurs when the multi-vsys firewall has virtual systems managed by Panorama, and the vsys ID sequence breaks when unused virtual systems are deleted and the changes are pushed to the firewall.

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.

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.

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

The PA-1410 firewalls experience a spike in the management plane CPU utilization when the monitor-dp process attempts to retrieve the power cycle count from the NVMe drive’s SMART data. This condition leads to repeated reboots of the device, requiring a hard reset for recovery.

A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.

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.

Upgrading to an affected release causes the firewall to reboot multiple times if the config contains an EDL (External Dynamic List) that doesn't have an associated certificate profile.

The system logs repeatedly displayed the alert `Clearing snmpd.log due to log overflow` due to the SNMP counters rolling over. This is a benign message and does not impact device functionality.

(PA-460 firewalls only) The firewall experiences an out-of-memory (OOM) condition and displays an error message. This issue causes the device to crash and reboot unexpectedly.

Upon upgrade, the ElasticSearch health status intermittently transitions to the Red status for sometime, and then auto-recovers back to Green. During the Red status periods, the cluster logs are unavailable. This occurs due to disk write operations being excessively slow, failing to meet the minimum time threshold required to save the cluster state.

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.

(PA-800 series firewalls only) Upgrading firewalls to PAN-OS 11.0 or later causes SFP ports to go non-operational when the firewall uses forced port mode and the connected peer device operates without auto-negotiation.

Workaround: Enable auto-negotiation on the connected peer firewall.

When the Enterprise DLP data filtering profile is configured with a Block action and is used in conjunction with Advanced Threat Prevention, which is configured with an action of reset-both, reset-server, reset-client, or drop for the HTTP Command and Control detector, Dropbox file uploads that exceed the maximum configured file size action will fail.

Workaround: Configure the Advanced Threat Prevention Inline Cloud analysis (ObjectsSecurity ProfilesAnti-Spyware) action for the HTTP Command and Control detector to alert.

After upgrading to PAN-OS 11.1.6-h4, 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:

When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays Unknown instead of 25GBase-SR.

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:

When Enterprise DLP is enabled, file uploads might unexpectedly fail when 100 continue response is received from the server during file uploads.

File downloads for content encoded with zstd (Zstandard), such as specific content from box.com, fail when using Enterprise DLP because zstd decompression is not supported in PAN-OS.

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.

When you use custom certificates for the connection between Panorama and a log collector, the automated renewal for the predefined ElasticSearch certificates gets disrupted.

Workaround: Remove the custom certificates before the ElasticSearch certificates expire. This allows the system to correctly identify and renew the predefined ElasticSearch certificates. After the renewal is complete, re-install the custom certificates.

(PA-3260 firewalls only) An interface unexpectedly moves out of Link Aggregation Control Protocol (LACP), which causes an out-of-memory (OOM) condition on the *logrcvr* process, resulting in the interface going down and then automatically coming back up without intervention.

When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:

Service routes configured for a data plane interface might incorrectly route traffic through the management plane interface instead. This issue impacts Syslog and CRL status traffic when the service route lacks a specific destination custom service route.

(PA-7500, PA-5500, and PA-3500 firewalls only) When DNS Security packet capture is enabled and a domain name has a length of 62 characters, the DNS Security threat log entry is not generated. On the affected platforms, this condition can also trigger a pan_task crash due to shared memory corruption.

Workaround: Disable DNS Security packet capture in anti-spyware profiles (ObjectsSecurity ProfilesAnti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.

When Panorama is not internet-connected and you try to upload images to the managed firewalls by using the Validate option, the upload fails with the following error: Failed to create multi-upload job. No valid software deploy targets found.

(PA-7000 Series firewalls only) Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-jumbo packets may cause silent packet drops or application slowness.

When the DHCP server is enabled for GlobalProtect, the commit error message is not properly displayed when Any is selected as the source interface in the service router configuration ( DeviceSetupServiceService Router Configuration).

When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on the GlobalProtect gateway, the gpsvc gets stuck during renewal and after HA failover.

TLSv1.3 hybridized Kyber support in the latest versions of Chrome and Edge browsers results in dropped Client Hello packets when SSL/TLS handshake inspection is enabled.

Workaround: Disable SSL/TLS handshake inspection.

If you change the service route of gp-ip-mgmt in Device > Setup > Services > Service Features > gp-ip-mgmt and Commit, the change won’t take effect. gp-ip-mgmt continues to use the last committed service route.

Workaround: After you change the service route interface for gp-ip-mgmt, navigate to either a GlobalProtect portal or gateway, click OK to save the configuration, and Commit the changes. This commit will include the service route change.

Panorama and the firewall display inconsistent IP addresses for dynamic address group members after manually syncing.

The Advanced DNS Security trial license and trial license information cannot be activated and viewed, respectively, on a managed firewall (with expired or active status) from Panorama. These tasks can only be performed on the firewall.

When Advanced Routing is enabled, IP multicast is not supported. An upcoming version will provide support for this feature. Customers who have multicast configured or who plan to deploy multicast routing should not upgrade to 11.2.0. Additionally, when Advanced Routing is enabled, the BGP dampening configuration isn't applied to any peers or peer group; the configuration is preserved but has no effect on BGP. Customers can use BGP even if they have applied a Dampening profile to a specific set of peers. The issue doesn't affect any other BGP features.

The VMX hardware version was upgraded from vmx-10 to vmx-15 on ESXi and NSX-T. Support for vmx-15 is supported on ESXi 6.7 U2 and onwards. Palo Alto Networks recommends that you upgrade your ESXi version if it is less than 6.7 U2. For more information, see the compatibility matrix.

When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCPv4 relay agent functions successfully, but DHCPv6 relay agent doesn't work.

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:

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>

If you change the configuration of a firewall acting as a PPPoEv4 or PPPoEv6 client, old routes from the Forwarding Information Base (FIB) and route table for an inherited configuration with dynamic-identifier or client remain visible. Old routes also remain visible for an inherited interface when you execute the CLI command, show interface all.

Workaround: Unconfigure and configure the Inherited Interface.

The X-Forwarded-For (XFF) value is not displayed in traffic logs.