PAN-OS 11.1.5 Known Issues
Focus
Focus

PAN-OS 11.1.5 Known Issues

Table of Contents

PAN-OS 11.1.5 Known Issues

PAN-OSĀ® 11.1.5 known issues.
The following list includes only outstanding known issues specific to PAN-OSĀ® 11.1.5. This list includes issues specific to Panoramaā„¢, GlobalProtectā„¢, VM-Series plugins, and WildFireĀ®, as well as known issues that apply more generally or that are not identified by an issue ID.
Issue ID
Description
PAN-263940
On a PA-7500 Series firewall node in an NGFW cluster, if the data processing card is in slot 6, packet drops are expected.
PAN-262556
The ElasticSearch cluster health status might continue to remain yellow for an extended period after upgrading to PAN-OS 11.1
PAN-260851
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (ObjectsApplications) tag.
PAN-259733
This issue is now resolved. See PAN-OS 11.1.4-h1 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-257615
This issue is now resolved. See PAN-OS 11.1.4-h1 Addressed Issues.
The Panorama web interface intermittently displays logs or fails to display logs completely.
PAN-254240
In the event of an HSCI flap on an NGFW cluster node, traffic reconvergence takes three to four seconds.
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-252358
In the event of a corosync restart, an NGFW cluster node goes to failed state.
PAN-251551
When an NGFW cluster agent crashes and doesn't recover, leader election will take approximately 45 seconds to begin and traffic failover will occur during that time.
PAN-250903
In a congestion scenario on an HSCI port of an NGFW cluster node, the QoS priorities of cross node traffic streams might be reversed if you're using the default QoS profile with class1 to class8 set as high to low.
PAN-247974
LACP flap is expected during a device failover in an NGFW cluster due to an L2 ctrld restart on the new leader node.
PAN-240529
Cloud application information is missing from traffic logs on NGFW cluster nodes.
PAN-234015
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
PAN-224502
The autocommit time of the VM-Series firewall running PAN-OS 11.1.0 might take longer than expected.
PAN-220180
Configured botnet reports (MonitorBotnet) are not generated.
PAN-219644
Firewalls forwarding logs to a syslog server over TLS (ObjectsLog Forwarding) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
PAN-207733
When a DHCPv6 client is configured on HA Active/Passive firewalls, if the DHCPv6 server goes down, after the lease time expires, the DHCPv6 client should enter SOLICIT state on both the Active and Passive firewalls. Instead, the client is stuck in BOUND state with an IPv6 address having lease time 0 on the Passive firewall.
PAN-207611
When a DHCPv6 client is configured on HA Active/Passive firewalls, the Passive firewall sometimes crashes.
PAN-207442
For M-700 appliances in an active/passive high availability (PanoramaHigh 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.
  1. Log in to the Panorama web interface of the active-primary HA peer.
  2. Select Commit and Commit to Panorama.
  3. In the active-primary HA peer Dashboard, click Sync to Peer in the High Availability widget.
PAN-207040
If you disable Advanced Routing, remove logical routers, and downgrade from PAN-OS 11.0.0 to a PAN-OS 10.2.x or 10.1.x release, subsequent commits fail and SD-WAN devices on Panorama have no Virtual Router name.
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 (PanoramaManaged 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. Confirm the Dedicated Log Collector is disconnected from Panorama.
    admin> show panorama-status
    Verify the Connected status is no.
  2. 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 NetworkInterfaceEthernet, 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 (CommitPush to DevicesEdit Selections or CommitCommit and PushEdit 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-194978
(PA-1400 Series firewalls only) In NetworkInterfaceEthernet, hovering the mouse over a power over Ethernet (PoE) Link State icon does not display link speed and link duplex details.
PAN-187685
On the Panorama management server, the Template Status displays no synchronization status (PanoramaManaged DevicesSummary) 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 CommitPush 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-186283
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
Workaround: Use CommitPush to Devices to synchronize the templates.
PAN-184708
Scheduled report emails (MonitorPDF ReportsEmail Scheduler) are not emailed if:
  • A scheduled report email contains a Report Group (MonitorPDF ReportsReport 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 MonitorPDF ReportsReport Groups and remove all SaaS Application Usage reports from all Report Groups.
  2. Select MonitorPDF ReportsEmail 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.
    (Panorama managed firewalls) Select CommitCommit and Push
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.