aaron.axvig/firewallissues
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update PAN-OS 11.1 files

Browse Source
This commit is contained in:
aaron.axvig
2026-04-15 14:57:19 -05:00
parent 8a243e3d9c
commit 10f549ef2a
84 changed files with 3207 additions and 3509 deletions
Download Patch File Download Diff File Expand all files Collapse all files
web/data/issues/PAN-OS/known/11.1.11.md
+80 -104
View File
@@ -4,51 +4,61 @@ product: PAN-OS
version: 11.1.11
---
## 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-307795
```caveat
This issue is now resolved. See PAN-OS 11.1.13-h1 Addressed Issues.
```
On a standalone Panorama, the system incorrectly generates system logs indicating a lost connection to its peer even when High Availability is not configured. You can safely ignore these logs, as they do not affect operations.
## PAN-306502
```caveat
This issue is now resolved. See PAN-OS 11.1.13 Addressed Issues.
```
TLS sessions using version 1.2 or earlier may fail when session traffic matches a decryption policy rule with the no-decrypt action under either of the following conditions:
If both of these conditions are met, the session is guaranteed to fail.
If both of these conditions are met, the session is guaranteed to fail.
- Both HTTP header insertion (**Objects** > **Security Profiles** > **URL Filtering** > **HTTP Header Insertion**) and SSL/TLS handshake inspection (**Device** > **Setup** > **Session** > **Decryption Settings** > **SSL Decryption Settings**) are enabled.
- **Log Successful SSL Handshake** is not enabled in the decryption policy rule and neither **Block sessions with expired certificates** nor **Block sessions with untrusted issuers** is enabled in the attached decryption profile.
If both of these conditions are met, the session is guaranteed to fail.
**Workaround:** Perform one of the following tasks:
Both HTTP header insertion (ObjectsSecurity ProfilesURL FilteringHTTP Header Insertion) and SSL/TLS handshake inspection (DeviceSetupSessionDecryption SettingsSSL Decryption Settings) are enabled.
Both HTTP header insertion (ObjectsSecurity ProfilesURL FilteringHTTP Header Insertion) and SSL/TLS handshake inspection (DeviceSetupSessionDecryption SettingsSSL Decryption Settings) are enabled.
Log Successful SSL Handshake is not enabled in the decryption policy rule and neither Block sessions with expired certificates nor Block sessions with untrusted issuers is enabled in the attached decryption profile.
Log Successful SSL Handshake is not enabled in the decryption policy rule and neither Block sessions with expired certificates nor Block sessions with untrusted issuers is enabled in the attached decryption profile.
Workaround: Perform one of the following tasks:
Enable Log Successful SSL Handshake in all no-decrypt decryption policy rules.
Enable Log Successful SSL Handshake in all no-decrypt decryption policy rules.
Enable either Block sessions with expired certificates or Block sessions with untrusted issuers in the decryption profiles attached to the no-decrypt decryption policy rules.
- Enable **Log Successful SSL Handshake** in all no-decrypt decryption policy rules.
- Enable either **Block sessions with expired certificates** or **Block sessions with untrusted issuers** in the decryption profiles attached to the no-decrypt decryption policy rules.
## PAN-305301
```caveat
This issue is now resolved. See PAN-OS 11.1.13-h1 Addressed Issues.
```
The timing of GlobalProtect lifetime expiry or inactivity logout notifications used for GlobalProtect SSL tunnels may cause the pan_task process to stop responding and the dataplane to restart.
Workaround: Select Network > GlobalProtect > Gateways > <gateway-config> > Agent > <agent-config> > Connection Settings and change the value of both Notify Before Lifetime Expires (min) and Notify Before Inactivity Logout (min) to 0.
**Workaround:** Select **Network > GlobalProtect > Gateways > <gateway-config> > Agent > <agent-config> > Connection Settings** and change the value of both **Notify Before Lifetime Expires (min)** and **Notify Before Inactivity Logout (min)** to 0.
## PAN-304756
```caveat
This issue is now resolved. See PAN-OS 11.1.13-h1 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 might result in incomplete or inconsistent configurations across virtual systems.
## PAN-304576
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.
**Workaround:** Disable HTTP/2 server push using the `set deviceconfig setting http2 server-push no` CLI command.
## PAN-303959
@@ -56,10 +66,18 @@ Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually dro
## PAN-303051
```caveat
This issue is now resolved. See PAN-OS 11.1.13 Addressed Issues.
```
The reportd process experiences a memory leak because it retains memory that was temporarily used for report generation. Once a task is complete, the process fails to release this memory for reuse, leading to continuous accumulation and eventual memory exhaustion on the Panorama device.
## PAN-298505
```caveat
This issue is now resolved. See PAN-OS 11.1.12 Addressed Issues
```
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.
## PAN-297295
@@ -68,29 +86,19 @@ After upgrading multi-vsys firewalls, the sequence of the virtual system IDs (vs
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.
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_v5D4_v2/DS4_v2 to D8ds_v5D5_v2/DS5_v2 to D16ds_v5 Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
**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
- 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.
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
## 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-292202
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.
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.
## PAN-289432
@@ -106,7 +114,7 @@ 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.
**Workaround:** Enable auto-negotiation on the connected peer firewall.
## PAN-286848
@@ -124,17 +132,17 @@ URL-continue and override continue selections will function like a general URL-b
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.
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
## 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.
**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-276920
URL filtering response pages may load slowly or fail to display when users request websites that are blocked in the URL Filtering profile (site access for the corresponding URL category is block, continue, or override) attached to the matching Security policy rule. This occurs on an intermittent basis.
URL filtering response pages may load slowly or fail to display when users request websites that are blocked in the URL Filtering profile (site access for the corresponding URL category is **block**, **continue**, or **override**) attached to the matching Security policy rule. This occurs on an intermittent basis.
## PAN-275047
@@ -150,7 +158,7 @@ The ElasticSearch cluster health status might continue to remain yellow for an e
## 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.
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-254240
@@ -182,7 +190,7 @@ The autocommit time of the VM-Series firewall running PAN-OS 11.1.0 might take l
## PAN-220180
Configured botnet reports (MonitorBotnet) are not generated.
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
## PAN-207733
@@ -194,21 +202,13 @@ When a DHCPv6 client is configured on HA Active/Passive firewalls, the Passive f
## 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.
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.
**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.
Log in to the Panorama web interface of the active-primary HA peer.
Select Commit and Commit to Panorama.
Select Commit and Commit to Panorama.
In the active-primary HA peer Dashboard, click Sync to Peer in the High Availability widget.
In the active-primary HA peer Dashboard, click Sync to Peer in the High Availability widget.
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/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
@@ -216,41 +216,22 @@ If you disable Advanced Routing, remove logical routers, and downgrade from PAN-
## PAN-206913
When a DHCPv6 client is configured on HA Active/Passive firewalls, releasing the IPv6 address from the client (using Release in the UI or using the request dhcp client ipv6 release all CLI command) releases the IPv6 address from the Active firewall, but not the Passive firewall.
When a DHCPv6 client is configured on HA Active/Passive firewalls, releasing the IPv6 address from the client (using Release in the UI or using the `request dhcp client ipv6 release all` CLI command) releases the IPv6 address from the Active firewall, but not the Passive firewall.
## 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.
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.
**Workaround:** Restart the `mgmtsrvr` process on the Dedicated Log Collector.
Log in to the Dedicated Log Collector CLI.
Log in to the Dedicated Log Collector CLI.
Confirm the Dedicated Log Collector is disconnected from Panorama.admin> show panorama-status Verify the Connected status is no.
Confirm the Dedicated Log Collector is disconnected from Panorama.
admin> show panorama-status Verify the Connected status is no.
admin> show panorama-status
admin> show panorama-status
Verify the Connected status is no.
Restart the mgmtsrvr process.admin> debug software restart process management-server
Restart the mgmtsrvr process.
admin> debug software restart process management-server
admin> debug software restart process management-server
admin> debug software restart process management-server
1. [Log in to the Dedicated Log Collector CLI](https://docs.paloaltonetworks.com/panorama/11-0/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-197588
@@ -262,11 +243,11 @@ The PAN-OS ACC (Application Command Center) does not display a widget detailing
PA-1400 Series firewalls only
```
In NetworkInterfaceEthernet, the power over Ethernet (PoE) ports do not display a Tag value.
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 (CommitPush to DevicesEdit Selections or CommitCommit and PushEdit Selections).
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
@@ -282,23 +263,23 @@ When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the
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.
In **Network** > **Interface** > **Ethernet**, 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.
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 CommitPush to Devices.
**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-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.
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.
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
## PAN-184708
@@ -306,29 +287,24 @@ Workaround: Use CommitPush to Devices to synchronize the templates.
Panorama managed firewalls
```
Scheduled report emails (MonitorPDF ReportsEmail Scheduler) are not emailed if:
Scheduled report emails (**Monitor** > **PDF Reports** > **Email 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 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.
A scheduled report contains only a SaaS Application Usage Report.
**Workaround:** To receive a scheduled report email for all other PDF report types:
Workaround: To receive a scheduled report email for all other PDF report types:
Select MonitorPDF ReportsReport Groups and remove all SaaS Application Usage reports from all Report Groups.
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.
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
Commit.() Select CommitCommit and Push
() Select CommitCommit and Push
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-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.
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
## PAN-183404