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.3.md
+209 -98
View File
@@ -6,18 +6,38 @@ version: 11.1.3
## 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-298505
```caveat
This issue is now resolved. See PAN-OS 11.1.6-h20 Addressed Issues, PAN-OS 11.1.10-h7 Addressed Issues, and 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-294179
```caveat
This issue is now resolved. See PAN-OS 11.1.6-h17 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-291288
An active firewall might unexpectedly reboot due to a pan_task crash caused by a page allocation failure. This issue is observed after a period of runtime with traffic and telemetry collection.
## 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
@@ -28,51 +48,54 @@ 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-287871
```caveat
This issue affects PAN-OS 11.1.3-h2
```
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
## 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-281885
@@ -80,24 +103,35 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
## PAN-280532
```caveat
This issue is now resolved. See PAN-OS 11.1.10 Addressed Issues.
```
When you use a single syslog server over TCP for log forwarding, and the connectivity to the syslog server breaks, syslog forwarding does not resume even after the connectivity to the server restores.
Workaround: Performing one of the following tasks:
**Workaround:** Performing one of the following tasks:
Reboot the firewall.
Temporarily, configure syslog to use UDP, commit the configuration, revert to TCP, and then commit.
- Reboot the firewall.
- Temporarily, configure syslog to use UDP, commit the configuration, revert to TCP, and then commit.
## PAN-280471
When applying filters or searching for logs in the PanoramaMonitorLogssection, you might experience slow performance.
When applying filters or searching for logs in the **Panorama** > **Monitor** > **Logs**section, you might experience slow performance.
## PAN-279621
```caveat
This issue is now resolved. See PAN-OS 11.1.9 Addressed Issues.
```
Early aging and removal of firewall session while they are still active can lead to intermittent instabilities and crashes for proxy traffic, the Content and Threat detection engine, and any data-path processing.
## 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-278296
@@ -106,26 +140,50 @@ The system MAC address of the aggregate interface is the same on both the active
## PAN-277417
```caveat
This issue is now resolved. See PAN-OS 11.1.9 Addressed Issues.
```
Memory leak issues can occur during the parsing of server certificates used for SSL Inbound Inspection, preventing the firewall from completing inspection.
## PAN-277034
```caveat
This issue is now resolved. See PAN-OS 11.1.10-h5 Addressed Issuesand PAN-OS 11.1.6-h19 Addressed Issues
```
WildFire reports might not fully display or be downloadable because some static resources fail to load.
## PAN-275601
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.
```caveat
This issue is now resolved. See PAN-OS 11.1.10 Addressed Issues
```
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.`
## PAN-273300
When upgrading Panorama from PAN-OS 10.2 or PAN-OS 11.0 to PAN-OS 11.1 or a later release, Panorama fails to upgrade if it is operating within a Collector Group. The following error appears:Error: Traceback (most recent call last):File "/opt/panrepo/releases/<PANOS release version>/validate"... (min ([dts['min'] for dts in 10g_type_intv_dir.values() if dts|'min']])-strftime ('%Y-%m-%d'),
```caveat
This issue is now resolved. See PAN-OS 11.1.6-h1 Addressed Issues
```
When upgrading Panorama from PAN-OS 10.2 or PAN-OS 11.0 to PAN-OS 11.1 or a later release, Panorama fails to upgrade if it is operating within a Collector Group. The following error appears:`Error: Traceback (most recent call last):File "/opt/panrepo/releases/<PANOS release version>/validate"... (min ([dts['min'] for dts in 10g_type_intv_dir.values() if dts|'min']])-strftime ('%Y-%m-%d'),`
## PAN-265336
```caveat
(PAN-OS 11.1.3-h6 only)
```
Copper ports flap when generating a technical support file, executing telemetry, or retrieving port status using a Management Data Input/Output (MDIO) read.
## PAN-263987
```caveat
This issue is now resolved. See PAN-OS 11.1.4-h4 Addressed Issues.
```
When a NAT traversal (NAT-T or UDP encapsulation) IPSec tunnel is terminated on a Palo Alto Networks firewall and the NAT rule applied to the NAT-T IPSec tunnel is also on the same firewall, then the data traffic flowing through the NAT-T IPSec tunnel can't be NATed correctly.
## PAN-263940
@@ -138,14 +196,30 @@ Dereferencing a NULL pointer that occurs might cause pan_task processes to crash
## 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-259769
```caveat
This issue is now resolved. See PAN-OS 11.1.3-h6 Addressed Issues
```
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
## PAN-259733
```caveat
This issue is now resolved. See PAN-OS 11.1.3-h2 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
```caveat
This issue is now resolved. See PAN-OS 11.1.3-h4 Addressed Issues.
```
The Panorama web interface intermittently displays logs or fails to display logs completely.
## PAN-255868
@@ -156,32 +230,56 @@ PA-3400 Series firewalls only
After enabling kernel data collection during a silent reboot, the firewall fails and reboots to maintenance mode.
Workaround: To recover the firewall, initiate a reboot from maintenance mode.
**Workaround:** To recover the firewall, initiate a reboot from maintenance mode.
## PAN-255579
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues.
```
Demo Mode and Log Forwarding: PA-7500 Series firewalls and Panorama display data plane logs after a delay.
## PAN-255285
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues.
```
If only the HCSI-A link is connected on NGFW cluster nodes (the HSCI-B link is not connected) and the management interfaces goes down, the situation will result in a split brain.
## PAN-255116
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
When QoS is applied, traffic on an NGFW cluster node going from an MC-LAG interface to a destination stops when a member of the MC-LAG goes down.
## PAN-254927
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
Certain types of data packets sent to threat inspection processing on the Networking cards of PA-7500 Series firewalls cause a pan_task crash.
## PAN-254827
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
When you change an IP address on a management interface on any of the NGFW cluster nodes, there's no workflow in cluster-config to detect this change, so the subsequent commit-all will not push the updated management IP address.
Workaround: You must manually make an unrelated change to cluster-config in order for Panorama to detect this change; the subsequent commit-all will push the cluster-config with the updated management IP address to cluster-manager.
**Workaround:** You must manually make an unrelated change to cluster-config in order for Panorama to detect this change; the subsequent commit-all will push the cluster-config with the updated management IP address to cluster-manager.
## PAN-254351
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
An NGFW cluster node could get stuck in suspended state in some cases when you use GRE tunnel termination with keepalive enabled on both ends.
## PAN-254240
@@ -194,10 +292,18 @@ The auto commit job may take longer than expected to complete when the Panorama
## PAN-253466
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
In the event of a cluster manager restart on the leader node of an NGFW cluster, traffic stops because the state machine transitions to unknown and the leader is not changing.
## PAN-253466
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
On an NGFW cluster node, an expected packet buffer leak occurs with FTP/SIP traffic over an extended period of time.
## PAN-252358
@@ -210,7 +316,11 @@ In the event of a corosync restart, an NGFW cluster node goes to failed state.
## PAN-251639
When a Wildfire Analysis security profile is enabled, an out of memory condition might occur due to a memory leak in the varrcvr process.
```caveat
This issue is now resolved. See PAN-OS 11.1.4 Addressed Issues.
```
When a Wildfire Analysis security profile is enabled, an out of memory condition might occur due to a memory leak in the `varrcvr` process.
## PAN-251551
@@ -222,6 +332,10 @@ When an NGFW cluster agent crashes and doesn't recover, leader election will tak
## PAN-251501
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
Upon a reboot, an NGFW cluster node will occasionally fail to rejoin a cluster due to a timing issue.
## PAN-250903
@@ -234,18 +348,34 @@ In a congestion scenario on an HSCI port of an NGFW cluster node, the QoS priori
## PAN-250062
```caveat
This issue is now resolved. See PAN-OS 11.1.4-h4 Addressed Issues.
```
Device telemetry might fail at configured intervals due to bundle generation issues.
## PAN-250043
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
On an NGFW cluster node, if you configure a QoS interface with an Egress Max (Mbps) that exceeds 68000, the operation will fail with a message indicating "...is not a valid reference.…" The QoS Max bandwidth on any interface cannot be configured to be more than 68000.
## PAN-249727
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
On an NGFW cluster node, the Custom/Pre-defined URL category is not part of the session flow data and a promoted session after failover does not include it.
## PAN-248762
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
A firewall using the Advanced Routing Engine configured with OSPF crashes when connecting to the neighbor while exchanging route maps.
## PAN-247974
@@ -266,17 +396,22 @@ Cloud application information is missing from traffic logs on NGFW cluster nodes
## PAN-237106
```caveat
This issue is now resolved. See PAN-OS 11.1.8 Addressed Issues
```
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 can be at most 40 characters`
- `db-serialno is invalid`
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>
**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>
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
## PAN-234015
@@ -284,6 +419,10 @@ The X-Forwarded-For (XFF) value is not displayed in traffic logs.
## PAN-227978
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
The UI widget does not accurately list the status of the port when NGFW clustering is enabled.
## PAN-224502
@@ -292,7 +431,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
@@ -304,21 +443,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
@@ -326,37 +457,18 @@ If you disable Advanced Routing, remove logical routers, and downgrade from PAN-
## 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
@@ -368,11 +480,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
@@ -388,23 +500,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
@@ -412,29 +524,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
@@ -446,4 +553,8 @@ If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of th
## PAN-164885
On the Panorama management server, pushes to managed firewalls (CommitPush to Devices or Commit and Push) may fail when an EDL (ObjectsExternal Dynamic Lists) is configured to Check for updates every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
```caveat
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues
```
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.