Add files
This commit is contained in:
@@ -4,58 +4,80 @@ product: PAN-OS
|
||||
version: 11.1.10
|
||||
---
|
||||
|
||||
## 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 affects PAN-OS 11.1.10-h7 through 11.1.10-h11. This issue is now resolved. See PAN-OS 11.1.10-h12 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.10-h10 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.10-h12 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
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## 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.10-h7 Addressed Issuesand 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
|
||||
@@ -64,32 +86,38 @@ 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
|
||||
|
||||
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.
|
||||
- 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-296977
|
||||
|
||||
When you apply a filter in Network > Interfaces and then try to view Ethernet interface details using the web interface, the web interface becomes unresponsive.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
When you apply a filter in **Network > Interfaces** and then try to view **Ethernet** interface details using the web interface, the web interface becomes unresponsive.
|
||||
|
||||
## PAN-294179
|
||||
|
||||
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.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.10-h4 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-293673
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 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-292202
|
||||
@@ -104,14 +132,26 @@ Could not get parameters for double encryption. This occurred when the certifica
|
||||
|
||||
## PAN-290996
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.10-h1 Addressed Issues and PAN-OS 11.1.11 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-290235
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues.
|
||||
```
|
||||
|
||||
The dscd process crashes continuously on MIPS platforms (for example, PA-850 firewalls) due to a runtime error related to an invalid memory address or nil pointer dereference. This occurs when the golang library upgrade in CIE is not compatible with the MIPS platform.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
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-289383
|
||||
@@ -122,14 +162,22 @@ 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-288097
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287056
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.10-h1 Addressed Issues and PAN-OS 11.1.11 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-286848
|
||||
@@ -146,81 +194,83 @@ URL-continue and override continue selections will function like a general URL-b
|
||||
|
||||
## PAN-286306
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.10-h1 Addressed Issues and PAN-OS 11.1.11 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.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
When you run Commit and Push operations as a single action.
|
||||
This issue is more likely to occur in the following scenarios:
|
||||
|
||||
When you run Commit and Push operations as a single action.
|
||||
- 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.
|
||||
|
||||
When you trigger multiple parallel commit-all jobs at the same time.
|
||||
**Workaround:** Perform one of the following steps:
|
||||
|
||||
When you trigger multiple parallel commit-all jobs at the same time.
|
||||
|
||||
Device groups and templates have different configuration synchronization versions.
|
||||
|
||||
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.
|
||||
- Perform commit and push as two separate, sequential steps.
|
||||
- Perform a full push instead of selective push.
|
||||
|
||||
## PAN-285894
|
||||
|
||||
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-282854
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
The Elasticsearch cluster fails to start after deploying dedicated log collectors in a multi-collector environment.
|
||||
|
||||
**Workaround:** Restart all the involved log collectors.
|
||||
|
||||
## 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
|
||||
|
||||
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 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
|
||||
|
||||
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
|
||||
|
||||
A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||
- 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
|
||||
|
||||
To enable this fix, run the CLI command bug dataplane set ssl-decrypt accumulate-client-hello disjoined yes
|
||||
|
||||
## PAN-279415
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.11 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-277034
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.1.10-h5 Addressed Issues
|
||||
```
|
||||
|
||||
WildFire reports might not fully display or be downloadable because some static resources fail to load.
|
||||
|
||||
## 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
|
||||
|
||||
@@ -236,7 +286,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
|
||||
|
||||
@@ -268,7 +318,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
|
||||
|
||||
@@ -280,21 +330,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
|
||||
|
||||
@@ -306,36 +348,17 @@ When a DHCPv6 client is configured on HA Active/Passive firewalls, releasing the
|
||||
|
||||
## 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.
|
||||
|
||||
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.
|
||||
**Workaround:** Restart the mgmtsrvr process on the Dedicated Log Collector.
|
||||
|
||||
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
|
||||
|
||||
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
|
||||
|
||||
3. Restart the mgmtsrvr process.
|
||||
admin>debug software restart process management-server
|
||||
|
||||
## PAN-197588
|
||||
@@ -348,11 +371,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
|
||||
|
||||
@@ -368,23 +391,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
|
||||
|
||||
@@ -392,29 +415,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:
|
||||
|
||||
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.
|
||||
**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.
|
||||
|
||||
Commit.() Select CommitCommit and Push
|
||||
|
||||
() Select CommitCommit and Push
|
||||
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
|
||||
|
||||
|
||||
@@ -0,0 +1,129 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: PAN-OS
|
||||
version: 11.1.6-h29
|
||||
---
|
||||
|
||||
## PAN-316911
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls on Amazon Web Services (AWS) environments only
|
||||
```
|
||||
|
||||
Fixed an issue where a newly bootstrapped firewall required a management server restart, relicensing, or license push from Panorama to invoke the device certificate.
|
||||
|
||||
## PAN-314061
|
||||
|
||||
Fixed an issue where traffic was disrupted during IPSec rekey operations due to a 2 second delay in sending the DELETE message for the previous Security Association (SA) to the peer gateway after a new SA was negotiated.
|
||||
|
||||
## PAN-313850
|
||||
|
||||
```caveat
|
||||
PA-1400 Series firewalls in HA configurations only
|
||||
```
|
||||
|
||||
Fixed an issue where a split-brain condition occurred and HA1/HA2 links went down while upgrading when the HA configuration used dataplane interfaces for HA1 and a combination of HSCI and Ethernet interfaces for HA2.
|
||||
|
||||
## PAN-313623
|
||||
|
||||
Fixed an issue where the /opt/pancfg/mgmt/ssl/private/ directory on Palo Alto Networks devices with TPM support became 100% utilized due to an accumulation of undeleted .pub_pem files. This occurred because executing the show device-certificate status CLI command initiated a process that generated these files but failed to remove them, which prevented the fetching of new device certificates.
|
||||
|
||||
## PAN-312706
|
||||
|
||||
Fixed an issue where the firewalls restarted due to a function lacking a NULL-pointer sanity check.
|
||||
|
||||
## PAN-311250
|
||||
|
||||
```caveat
|
||||
Panorama appliances and Log Collectors only
|
||||
```
|
||||
|
||||
Fixed an issue where logs from multiple devices were not visible on Panorama even though the Elasticsearch health status on the dedicated Log Collectors appeared green.
|
||||
|
||||
## PAN-309300
|
||||
|
||||
Fixed an issue where management plane system resources configuration size exceeded 28 MB for over 4 hours, and the following error message was displayed: Configuration size reaching device capacity limit.
|
||||
|
||||
## PAN-308786
|
||||
|
||||
(Panorama appliances only) Fixed an issue where traffic log queries using the device_name filter returned no results, and complex log queries that included negation operators produced incorrect outputs.
|
||||
|
||||
## PAN-308654
|
||||
|
||||
Fixed an issue where the Elasticsearch Close Indices process closed more indices than expected and dropped the number of open shards below the minimum of 800 per Elasticsearch instance. This occurred because the process did not correctly account for the number of Elasticsearch instances when calculating the maximum number of allowed open shards.
|
||||
|
||||
## PAN-308507
|
||||
|
||||
```caveat
|
||||
Panorama managed firewalls only
|
||||
```
|
||||
|
||||
Fixed an issue where the firewall intermittently failed to maintain active log forwarding streams to Cortex Data Lake even when duplicate logging and enhanced application logging were enabled.
|
||||
|
||||
## PAN-306555
|
||||
|
||||
Fixed an issue where the firewall stopped responding, which led to service outages.
|
||||
|
||||
## PAN-304718
|
||||
|
||||
Fixed an issue where OSPF and BGP outages occurred due to an all_task process restart during clientless VPN content rewrite processing.
|
||||
|
||||
## PAN-304696
|
||||
|
||||
Fixed an issue where the Cloud User-ID connection timed out because the firewall took too long to process the OCSP response.
|
||||
|
||||
## PAN-298945
|
||||
|
||||
Fixed an issue where OSCP HTTP POST requests were not formatted correctly, which caused failures with strict responders.
|
||||
|
||||
## PAN-298617
|
||||
|
||||
Optimized the commit workflow to reduce the size of the effective configuration, resulting in lower memory consumption.
|
||||
|
||||
## PAN-297005
|
||||
|
||||
Fixed an issue where exporting custom reports resulted in empty CSV files.
|
||||
|
||||
## PAN-296694
|
||||
|
||||
Fixed an issue where the firewall rebooted due to the useridd process repeatedly restarting during an IP-port data type writes to the redis from multiple sources such as TSA or XML in a scale environment.
|
||||
|
||||
## PAN-296202
|
||||
|
||||
```caveat
|
||||
Firewalls in active/active HA configurations only
|
||||
```
|
||||
|
||||
Added a log enhancement to capture an issue where, when a commit operation was in progress, newly deployed IP address tags that used the XML API were not immediately reflected in address group resolution, which delayed IP address mapping to address groups and caused traffic to be incorrectly allowed or denied.
|
||||
|
||||
## PAN-291067
|
||||
|
||||
Fixed an issue where the devsrvr process periodically exceeded its virtual memory limit and restarted, which led to intermittent outages.
|
||||
|
||||
## PAN-290157
|
||||
|
||||
Fixed an issue on Panorama where the configd process stopped responding when filtering in the **Config Audit** window, which caused Panorama to restart unexpectedly.
|
||||
|
||||
## PAN-288175
|
||||
|
||||
Addressed a stack buffer overflow memory leak under plugin management code path.
|
||||
|
||||
## PAN-287584
|
||||
|
||||
Fixed an issue on the web interface where the address object pop up window only displayed a maximum of four address objects in the policy rule even after expanding the window.
|
||||
|
||||
## PAN-278688
|
||||
|
||||
Fixed an issue where DNS Security threat logs were not displayed on the firewall when packet capture was enabled and the domain name length was 62 characters.
|
||||
|
||||
## PAN-273158
|
||||
|
||||
```caveat
|
||||
PA-7000 Series firewalls only
|
||||
```
|
||||
|
||||
Fixed an issue where an incorrect ASIC configuration caused silent packet drops or application slowness when receiving a mix of jumbo and non-jumbo packets.
|
||||
|
||||
## PAN-271643
|
||||
|
||||
Fixed an issue where, when a commit job ID was higher than 65535, the XML API truncated the ID to a 16-bit unsigned integer due to an incorrect type case during printing, which resulted in an incorrect job ID being reported compared to the CLI output for the same commit.
|
||||
Reference in New Issue
Block a user