Remove dates from issue filenames
This commit is contained in:
@@ -0,0 +1,363 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 11.1.5
|
||||
---
|
||||
|
||||
## PAN-304756
|
||||
|
||||
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
|
||||
|
||||
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-292202
|
||||
|
||||
The system logs repeatedly displayed the alert `Clearing snmpd.log due to log overflow` due to the SNMP counters rolling over. This is a benign message and does not impact device functionality.
|
||||
|
||||
## 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
|
||||
|
||||
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
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
## PAN-288097
|
||||
|
||||
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||
|
||||
## PAN-287871
|
||||
|
||||
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-287056
|
||||
|
||||
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-286496
|
||||
|
||||
```caveat
|
||||
NGFW Clusters
|
||||
```
|
||||
|
||||
URL-continue and override continue selections will function like a general URL-block action.
|
||||
|
||||
## PAN-286255
|
||||
|
||||
When a firewall receives an unexpected termination request for certain SSL sessions, NGFW dataplane might experience a slow buffer resource leak.
|
||||
|
||||
Workaround: Disable accumulation proxy on the NGFW.
|
||||
|
||||
## 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.
|
||||
|
||||
## 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.
|
||||
|
||||
## PAN-281885
|
||||
|
||||
When exporting and importing the CSV file, the hash values of pre-shared key (PSK) variables set at template and template stack levels inconsistently change, resulting in both variables displaying the same hash value.
|
||||
|
||||
## PAN-280532
|
||||
|
||||
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:
|
||||
|
||||
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.
|
||||
|
||||
## PAN-279746
|
||||
|
||||
An SSL/TLS Client Hello may not be transmitted out of the firewall if the Client Hello arrives in multiple TCP segments and the traffic is not subject to SSL decryption (for example, SMTP over SSL).
|
||||
|
||||
## PAN-279621
|
||||
|
||||
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
|
||||
|
||||
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
|
||||
|
||||
The system MAC address of the aggregate interface is the same on both the active and the passive devices, causing some packets to be sent incorrectly to the passive device. This is causing the AE interface on the active firewall to not come up.
|
||||
|
||||
## PAN-277417
|
||||
|
||||
Memory leak issues can occur during the parsing of server certificates used for SSL Inbound Inspection, preventing the firewall from completing inspection.
|
||||
|
||||
## PAN-277034
|
||||
|
||||
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.
|
||||
|
||||
## 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'),
|
||||
|
||||
## PAN-269193
|
||||
|
||||
When multiple application are configured for GlobalProtect Clientless VPN, users are directed to the first application instead of the portal page with a list of application.
|
||||
|
||||
## PAN-262556
|
||||
|
||||
The ElasticSearch cluster health status might continue to remain yellow for an extended period after upgrading to PAN-OS 11.1
|
||||
|
||||
## PAN-261429
|
||||
|
||||
The command show auth radius-require-msg-authentic might return no output.
|
||||
|
||||
## PAN-260851
|
||||
|
||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (ObjectsApplications) tag.
|
||||
|
||||
## PAN-254240
|
||||
|
||||
In the event of an HSCI flap on an NGFW cluster node, traffic reconvergence takes three to four seconds.
|
||||
|
||||
## PAN-253963
|
||||
|
||||
The auto commit job may take longer than expected to complete when the Panorama management server is in Panorama or Log Collector mode.
|
||||
|
||||
## PAN-252358
|
||||
|
||||
```caveat
|
||||
PA-7500 Series firewalls only
|
||||
```
|
||||
|
||||
In the event of a corosync restart, an NGFW cluster node goes to failed state.
|
||||
|
||||
## PAN-251551
|
||||
|
||||
```caveat
|
||||
PA-7500 Series firewalls only
|
||||
```
|
||||
|
||||
When an NGFW cluster agent crashes and doesn't recover, leader election will take approximately 45 seconds to begin and traffic failover will occur during that time.
|
||||
|
||||
## PAN-250903
|
||||
|
||||
```caveat
|
||||
PA-7500 Series firewalls only
|
||||
```
|
||||
|
||||
In a congestion scenario on an HSCI port of an NGFW cluster node, the QoS priorities of cross node traffic streams might be reversed if you're using the default QoS profile with class1 to class8 set as high to low.
|
||||
|
||||
## PAN-247974
|
||||
|
||||
```caveat
|
||||
PA-7500 Series firewalls only
|
||||
```
|
||||
|
||||
LACP flap is expected during a device failover in an NGFW cluster due to an L2 ctrld restart on the new leader node.
|
||||
|
||||
## PAN-240529
|
||||
|
||||
```caveat
|
||||
PA-7500 Series firewalls only
|
||||
```
|
||||
|
||||
Cloud application information is missing from traffic logs on NGFW cluster nodes.
|
||||
|
||||
## PAN-237106
|
||||
|
||||
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 is invalid
|
||||
|
||||
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>
|
||||
|
||||
Revoke satellite certificates:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-224502
|
||||
|
||||
The autocommit time of the VM-Series firewall running PAN-OS 11.1.0 might take longer than expected.
|
||||
|
||||
## PAN-220180
|
||||
|
||||
Configured botnet reports (MonitorBotnet) are not generated.
|
||||
|
||||
## PAN-207733
|
||||
|
||||
When a DHCPv6 client is configured on HA Active/Passive firewalls, if the DHCPv6 server goes down, after the lease time expires, the DHCPv6 client should enter SOLICIT state on both the Active and Passive firewalls. Instead, the client is stuck in BOUND state with an IPv6 address having lease time 0 on the Passive firewall.
|
||||
|
||||
## PAN-207611
|
||||
|
||||
When a DHCPv6 client is configured on HA Active/Passive firewalls, the Passive firewall sometimes crashes.
|
||||
|
||||
## PAN-207442
|
||||
|
||||
For M-700 appliances in an active/passive high availability (PanoramaHigh Availability) configuration, the active-primary HA peer configuration sync to the secondary-passive HA peer may fail. When the config sync fails, the job Results is Successful (Tasks), however the sync status on the Dashboard displays as Out of Sync for both HA peers.
|
||||
|
||||
Workaround: Perform a local commit on the active-primary HA peer and then synchronize the HA configuration.
|
||||
|
||||
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.
|
||||
|
||||
## PAN-207040
|
||||
|
||||
If you disable Advanced Routing, remove logical routers, and downgrade from PAN-OS 11.0.0 to a PAN-OS 10.2.x or 10.1.x release, subsequent commits fail and SD-WAN devices on Panorama have no Virtual Router name.
|
||||
|
||||
## PAN-206909
|
||||
|
||||
The Dedicated Log Collector is unable to reconnect to the Panorama management server if the configd process crashes. This results in the Dedicated Log Collector losing connectivity to Panorama despite the managed collector connection Status (PanoramaManaged Collector) displaying connected and the managed colletor Health status displaying as healthy.
|
||||
|
||||
This results in the local Panorama config and system logs not being forwarded to the Dedicated Log Collector. Firewall log forwarding to the disconnected Dedicated Log Collector is not impacted.
|
||||
|
||||
Workaround: Restart the mgmtsrvr process on the Dedicated Log Collector.
|
||||
|
||||
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
|
||||
|
||||
## PAN-197588
|
||||
|
||||
The PAN-OS ACC (Application Command Center) does not display a widget detailing statistics and data associated with vulnerability exploits that have been detected using inline cloud analysis.
|
||||
|
||||
## PAN-197419
|
||||
|
||||
```caveat
|
||||
PA-1400 Series firewalls only
|
||||
```
|
||||
|
||||
In NetworkInterfaceEthernet, the power over Ethernet (PoE) ports do not display a Tag value.
|
||||
|
||||
## PAN-196758
|
||||
|
||||
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you Preview Changes (CommitPush to DevicesEdit Selections or CommitCommit and PushEdit Selections).
|
||||
|
||||
## PAN-195968
|
||||
|
||||
```caveat
|
||||
PA-1400 Series firewalls only
|
||||
```
|
||||
|
||||
When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the CLI prints an error depending on whether an interface type was selected on the non-PoE port or not. If an interface type, such as tap, Layer 2, or virtual wire, was selected before PoE was configured, the error message will not include the interface name (eg. ethernet1/4). If an interface type was not selected before PoE was configured, the error message will include the interface name.
|
||||
|
||||
## PAN-194978
|
||||
|
||||
```caveat
|
||||
PA-1400 Series firewalls only
|
||||
```
|
||||
|
||||
In NetworkInterfaceEthernet, hovering the mouse over a power over Ethernet (PoE) Link State icon does not display link speed and link duplex details.
|
||||
|
||||
## PAN-187685
|
||||
|
||||
On the Panorama management server, the Template Status displays no synchronization status (PanoramaManaged DevicesSummary) after a bootstrapped firewall is successfully added to Panorama.
|
||||
|
||||
Workaround: After the bootstrapped firewall is successfully added to Panorama, log in to the Panorama web interface and select CommitPush to Devices.
|
||||
|
||||
## PAN-187407
|
||||
|
||||
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to Hold client request for category lookup and the action set to Reset-Both and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||
|
||||
## PAN-186283
|
||||
|
||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||
|
||||
Workaround: Use CommitPush to Devices to synchronize the templates.
|
||||
|
||||
## PAN-184708
|
||||
|
||||
```caveat
|
||||
Panorama managed firewalls
|
||||
```
|
||||
|
||||
Scheduled report emails (MonitorPDF ReportsEmail Scheduler) are not emailed if:
|
||||
|
||||
A scheduled report email contains a Report Group (MonitorPDF ReportsReport Group) which includes a SaaS Application Usage report.
|
||||
|
||||
A scheduled report contains only a SaaS Application Usage Report.
|
||||
|
||||
Workaround: To receive a scheduled report email for all other PDF report types:
|
||||
|
||||
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
|
||||
|
||||
## PAN-184406
|
||||
|
||||
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||
|
||||
Workaround: Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||
|
||||
## PAN-183404
|
||||
|
||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||
|
||||
## PAN-181933
|
||||
|
||||
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||
Reference in New Issue
Block a user