Revise PAN-OS 11.2 known issues
This commit is contained in:
@@ -10,18 +10,34 @@ Strata Logging Service (SLS) log-forwarding streams intermittently show as inact
|
||||
|
||||
## PAN-304756
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues, PAN-OS 11.2.7-h10 Addressed Issues and PAN-OS 11.2.10-h3 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-301801
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
On Log Collectors, the Elasticsearch process might fluctuate between green and red states, causing log collection interruptions. This issue occurs when the number of shards exceeds the supported threshold of 1,000 shards per Elasticsearch instance.
|
||||
|
||||
## PAN-298505
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h4 Addressed Issuesand PAN-OS 11.2.10 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
|
||||
@@ -30,44 +46,62 @@ 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-296752
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.10 Addressed Issues
|
||||
```
|
||||
|
||||
The PA-1410 firewalls experience a spike in the management plane CPU utilization when the monitor-dp process attempts to retrieve the power cycle count from the NVMe drive’s SMART data. This condition leads to repeated reboots of the device, requiring a hard reset for recovery.
|
||||
|
||||
## PAN-295803
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues, PAN-OS 11.2.7-h10 Addressed Issues and PAN-OS 11.2.10-h3 Addressed Issues
|
||||
```
|
||||
|
||||
A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 Addressed Issues
|
||||
```
|
||||
|
||||
Upgrading to an affected release causes the firewall to reboot multiple times if the config contains an EDL (External Dynamic List) that doesn't have an associated certificate profile.
|
||||
|
||||
## 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.2.11 Addressed Issues and PAN-OS 11.2.7-h3 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.2.7-h1 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
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h3 Addressed Issues.
|
||||
```
|
||||
|
||||
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-291716
|
||||
@@ -76,10 +110,34 @@ The system logs repeatedly displayed the alert `Clearing snmpd.log due to log ov
|
||||
|
||||
## PAN-291661
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.10 Addressed Issues
|
||||
```
|
||||
|
||||
Upon upgrade, the ElasticSearch health status intermittently transitions to the Red status for sometime, and then auto-recovers back to Green. During the Red status periods, the cluster logs are unavailable. This occurs due to disk write operations being excessively slow, failing to meet the minimum time threshold required to save the cluster state.
|
||||
|
||||
## PAN-291288
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 Addressed Issuesand PAN-OS 11.2.7-h3 Addressed Issues
|
||||
```
|
||||
|
||||
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-290449
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 Addressed Issuesand PAN-OS 11.2.7-h3 Addressed Issues
|
||||
```
|
||||
|
||||
The scheduled vulnerability reports that are configured to be sent via email with multiple attachments send the first attached report only. The remaining attachments are dropped.
|
||||
|
||||
## PAN-290088
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h1 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
|
||||
@@ -90,13 +148,13 @@ 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-288525
|
||||
|
||||
When the Enterprise DLP data filtering profile is configured with a Block action and is used in conjunction with Advanced Threat Prevention, which is configured with an action of reset-both, reset-server, reset-client, or drop for the HTTP Command and Control detector, Dropbox file uploads that exceed the maximum configured file size action will fail.
|
||||
When the Enterprise DLP data filtering profile is configured with a **Block** action and is used in conjunction with Advanced Threat Prevention, which is configured with an action of **reset-both**, **reset-server**, **reset-client**, or **drop** for the **HTTP Command and Control detector**, Dropbox file uploads that exceed the maximum configured file size action will fail.
|
||||
|
||||
Workaround: Configure the Advanced Threat Prevention Inline Cloud analysis (ObjectsSecurity ProfilesAnti-Spyware) action for the HTTP Command and Control detector to alert.
|
||||
**Workaround:** Configure the Advanced Threat Prevention Inline Cloud analysis (**Objects** > **Security Profiles** > **Anti-Spyware**) action for the HTTP Command and Control detector to **alert**.
|
||||
|
||||
## PAN-287803
|
||||
|
||||
@@ -104,51 +162,53 @@ After upgrading to PAN-OS 11.1.6-h4, users might be unable to access some URLs d
|
||||
|
||||
To address this issue, use one of the following workarounds:
|
||||
|
||||
Configure the Adjust TCP MSS option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
|
||||
Configure the Adjust TCP MSS option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
|
||||
Disable the accumulation proxy using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||
|
||||
Disable the accumulation proxy using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-286848
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7 Addressed Issues
|
||||
```
|
||||
|
||||
ECMP incorrectly balances sessions across links based on the configured metric, which leads to an imbalance in traffic distribution and results in traffic assignment shifting disproportionately to routes with lower metrics.
|
||||
|
||||
## PAN-286306
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays Unknown instead of 25GBase-SR.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 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.2.7-h3 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
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7 Addressed Issues
|
||||
```
|
||||
|
||||
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-285061
|
||||
|
||||
@@ -160,13 +220,17 @@ File downloads for content encoded with zstd (Zstandard), such as specific conte
|
||||
|
||||
## PAN-284067
|
||||
|
||||
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 Addressed Issues
|
||||
```
|
||||
|
||||
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||
|
||||
## 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-282277
|
||||
|
||||
@@ -178,39 +242,44 @@ An interface unexpectedly moves out of Link Aggregation Control Protocol (LACP),
|
||||
|
||||
## PAN-279901
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h1 Addressed Issues
|
||||
```
|
||||
|
||||
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
|
||||
|
||||
## PAN-279415
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.8 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-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-277034
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h3 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.2.8 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-275047
|
||||
|
||||
@@ -222,15 +291,19 @@ After an upgrade, the firewall is unable to send logs to the Strata Logging Serv
|
||||
|
||||
## 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-260212
|
||||
|
||||
When viewing Applications (ObjectsApplications), child App-IDs may be listed under the incorrect container App-ID.
|
||||
When viewing **Applications** (**Objects** > **Applications**), child App-IDs may be listed under the incorrect container App-ID.
|
||||
|
||||
## PAN-259853
|
||||
|
||||
When the DHCP server is enabled for GlobalProtect, the commit error message is not properly displayed when Any is selected as the source interface in the service router configuration ( DeviceSetupServiceService Router Configuration).
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.7-h10 Addressed Issues
|
||||
```
|
||||
|
||||
When the DHCP server is enabled for GlobalProtect, the commit error message is not properly displayed when **Any** is selected as the source interface in the service router configuration ( **Device** > **Setup** > **Service** > **Service Router Configuration**).
|
||||
|
||||
## PAN-259423
|
||||
|
||||
@@ -240,13 +313,13 @@ When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on
|
||||
|
||||
TLSv1.3 hybridized Kyber support in the latest versions of Chrome and Edge browsers results in dropped Client Hello packets when SSL/TLS handshake inspection is enabled.
|
||||
|
||||
Workaround: Disable SSL/TLS handshake inspection.
|
||||
**Workaround:** Disable [SSL/TLS handshake inspection](https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-features/inspect-ssl-tls-handshakes).
|
||||
|
||||
## PAN-254108
|
||||
|
||||
when upgrading or downgrading a Panorama management server (PanoramaSoftware), managed device (PanoramaDevice DeploymentSoftware), or standalone firewall (DeviceSoftware), Base Releases and Preferred Releases settings are checked (enabled) by default and cause no PAN-OS software images to display.
|
||||
when upgrading or downgrading a Panorama management server (**Panorama** > **Software**), managed device (**Panorama** > **Device Deployment** > **Software**), or standalone firewall (**Device** > **Software**), **Base Releases** and **Preferred Releases** settings are checked (enabled) by default and cause no PAN-OS software images to display.
|
||||
|
||||
Workaround: Uncheck (disable) Base Releases or Preferred Releases to display either the available base PAN-OS or preferred PAN-OS releases available to download and install.
|
||||
**Workaround:** Uncheck (disable) **Base Releases** or **Preferred Releases** to display either the available base PAN-OS or preferred PAN-OS releases available to download and install.
|
||||
|
||||
## PAN-253963
|
||||
|
||||
@@ -254,9 +327,9 @@ The auto commit job may take longer than expected to complete when the Panorama
|
||||
|
||||
## PAN-252661
|
||||
|
||||
If you change the service route of gp-ip-mgmt in Device > Setup > Services > Service Features > gp-ip-mgmt and Commit, the change won’t take effect. gp-ip-mgmt continues to use the last committed service route.
|
||||
If you change the service route of gp-ip-mgmt in **Device > Setup > Services > Service Features > gp-ip-mgmt** and **Commit**, the change won’t take effect. gp-ip-mgmt continues to use the last committed service route.
|
||||
|
||||
Workaround: After you change the service route interface for gp-ip-mgmt, navigate to either a GlobalProtect portal or gateway, click OK to save the configuration, and Commit the changes. This commit will include the service route change.
|
||||
**Workaround:** After you change the service route interface for gp-ip-mgmt, navigate to either a GlobalProtect portal or gateway, click **OK**to save the configuration, and **Commit**the changes. This commit will include the service route change.
|
||||
|
||||
## PAN-250246
|
||||
|
||||
@@ -276,7 +349,7 @@ When Advanced Routing is enabled, IP multicast is not supported. An upcoming ver
|
||||
|
||||
## PAN-241994
|
||||
|
||||
The VMX hardware version was upgraded from vmx-10 to vmx-15 on ESXi and NSX-T. Support for vmx-15 is supported on ESXi 6.7 U2 and onwards. Palo Alto Networks recommends that you upgrade your ESXi version if it is less than 6.7 U2. For more information, see the compatibility matrix.
|
||||
The VMX hardware version was upgraded from vmx-10 to vmx-15 on ESXi and NSX-T. Support for vmx-15 is supported on ESXi 6.7 U2 and onwards. Palo Alto Networks recommends that you upgrade your ESXi version if it is less than 6.7 U2. For more information, see the [compatibility matrix](https://kb.vmware.com/s/article/2007240).
|
||||
|
||||
## PAN-239612
|
||||
|
||||
@@ -286,21 +359,22 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
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-236649
|
||||
|
||||
If you change the configuration of a firewall acting as a PPPoEv4 or PPPoEv6 client, old routes from the Forwarding Information Base (FIB) and route table for an inherited configuration with dynamic-identifier or client remain visible. Old routes also remain visible for an inherited interface when you execute the CLI command, show interface all.
|
||||
If you change the configuration of a firewall acting as a PPPoEv4 or PPPoEv6 client, old routes from the Forwarding Information Base (FIB) and route table for an inherited configuration with dynamic-identifier or client remain visible. Old routes also remain visible for an inherited interface when you execute the CLI command, `show interface all`.
|
||||
|
||||
Workaround: Unconfigure and configure the Inherited Interface.
|
||||
**Workaround:** Unconfigure and configure the Inherited Interface.
|
||||
|
||||
## PAN-234015
|
||||
|
||||
@@ -308,55 +382,28 @@ The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## 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-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 +415,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
|
||||
|
||||
@@ -384,19 +431,19 @@ When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the
|
||||
|
||||
## 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-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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user