Issue ID | Description
--- | ---
WF500-6271 | A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value> Workaround: Gracefully restart the affected Wildfire cluster nodes.
WF500-6259 | When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes. Workaround: Gracefully restart the affected WildFire active controller and passive controller in the cluster.
WF500-6270 | The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers. Workaround: Gracefully restart the WildFire cluster node where the process exit occurred.
WF500-6222 | When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues. Workaround: Do not configure a custom DNS when WildFire secure cluster communication is enabled.
WF500-6176 | When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
PAN-308564 | 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).
PAN-308507 | 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.
PAN-308418 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | 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 (Device Setup Content-ID Advanced DNS Security and uncheck Telemetry Enable).
PAN-304756 `This issue is now resolved. See PAN-OS 11.2.11 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-304576 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | 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.
PAN-303959 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
PAN-302927 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | After an upgrade, the Push to Devices window fails to populate the list of devices automatically. If you manually select devices by clicking Edit Selections, the OK button becomes unresponsive and fails to save or close the selection window. Additionally, clicking Cancel might incorrectly show the device list as empty while retaining the selections in the background.
PAN-301801 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | 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.
PAN-297610 `This issue is now resolved. See` PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.10-h2 Addressed Issues. | 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 `This issue is now resolved. See` PAN-OS 11.2.10 Addressed Issues | (`VM-Series firewalls on 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-296752 `This issue is now resolved. See` PAN-OS 11.2.10 Addressed Issues | 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.
PAN-295803 `This issue is now resolved. See` PAN-OS 11.2.11 Addressed Issues, PAN-OS 11.2.7-h10 Addressed Issues and PAN-OS 11.2.10-h3 Addressed Issues | A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.
PAN-295645 | When a WildFire cluster is configured centrally using Panorama, it initiates a series of processes, including a software install and reboot, in an order that will leave the resulting WildFire cluster in an unusable state.
PAN-294179 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | On the Panorama Config Audit page, some commit versions might display incorrect or missing data. Fields such as, COMMITTED BY, COMMIT DATE, and OBJECT CHANGES might not be visible for some commit versions. Sometimes, commit versions can disappear after a refresh and the commit description field might display corrupted characters.
PAN-291661 `This issue is now resolved. See` PAN-OS 11.2.10 Addressed Issues | 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.
PAN-288525 | 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 (Objects Security Profiles Anti-Spyware) action for the HTTP Command and Control detector to alert.
PAN-285061 | When Enterprise DLP is enabled, file uploads might unexpectedly fail when 100 continue response is received from the server during file uploads.
PAN-284700 | 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.
PAN-283429 | 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.
PAN-278688 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | (`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 (Objects Security Profiles Anti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.
PAN-273158 `This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues` | (`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.
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-260212 | When viewing Applications (Objects Applications), child App-IDs may be listed under the incorrect container App-ID.
PAN-259853 | 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 ( Device Setup Service Service Router Configuration).
PAN-259423 | 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.
PAN-254236 | 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.
PAN-254108 | when upgrading or downgrading a Panorama management server (Panorama Software), managed device (Panorama Device Deployment Software), or standalone firewall (Device Software), Base Releases and Preferred Releases settings are checked (enabled) by default and cause no PAN-OS software images to display. Workaround: Uncheck (disable) Base Releases or Preferred Releases to display either the available base PAN-OS or preferred PAN-OS releases available to download and install.
PAN-253963 | The auto commit job may take longer than expected to complete when the Panorama management server is in Panorama or Log Collector mode.
PAN-252661 | 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.
PAN-250246 | Panorama and the firewall display inconsistent IP addresses for dynamic address group members after manually syncing.
PAN-250062 | Device telemetry might fail at configured intervals due to bundle generation issues.
PAN-248836 | 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.
PAN-247728 | 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.
PAN-241994 | 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.
PAN-239612 | 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.
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-236649 | 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.
PAN-234015 | The X-Forwarded-For (XFF) value is not displayed in traffic logs.
PAN-207442 | For M-700 appliances in an active/passive high availability (Panorama High Availability) configuration, the active-primary HA peer configuration sync to the secondary-passive HA peer may fail. When the config sync fails, the job Results is Successful (Tasks), however the sync status on the Dashboard displays as Out of Sync for both HA peers. Workaround: Perform a local commit on the active-primary HA peer and then synchronize the HA configuration. Log in to the Panorama web interface of the active-primary HA peer. Select Commit and Commit to Panorama. In the active-primary HA peer Dashboard, click Sync to Peer in the High Availability widget.
2. 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. Log in to the Dedicated Log Collector CLI. Confirm the Dedicated Log Collector is disconnected from Panorama.
       admin> show panorama-status
3. Verify the Connected status is no. Restart the mgmtsrvr process.
       admin> debug software restart process management-server
PAN-197588 | The PAN-OS ACC (Application Command Center) does not display a widget detailing statistics and data associated with vulnerability exploits that have been detected using inline cloud analysis.
PAN-197419 | (`PA-1400 Series firewalls only`) In Network Interface Ethernet, the power over Ethernet (PoE) ports do not display a Tag value.
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-195968 | (`PA-1400 Series firewalls only`) When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the CLI prints an error depending on whether an interface type was selected on the non-PoE port or not. If an interface type, such as tap, Layer 2, or virtual wire, was selected before PoE was configured, the error message will not include the interface name (eg. ethernet1/4). If an interface type was not selected before PoE was configured, the error message will include the interface name.
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 and select Commit Push to Devices.
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-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.