Add PAN-OS 11.2 known issues
This commit is contained in:
@@ -0,0 +1,509 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 11.2.4
|
||||
---
|
||||
|
||||
## PAN-308507
|
||||
|
||||
Strata Logging Service (SLS) log-forwarding streams intermittently show as inactive. When checking the status of log-forwarding connections, one or more streams are reported as inactive. Restarting the log-receiver process temporarily resolves the issue, but the streams become inactive again after approximately 1-2 hours. This intermittent inactivity results in log loss.
|
||||
|
||||
## 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 may result in incomplete or inconsistent configurations across virtual systems.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-301801
|
||||
|
||||
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
|
||||
|
||||
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-297775
|
||||
|
||||
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||
|
||||
Workaround: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
```caveat
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
D3_v2/DS3_v2 to D8ds_v5
|
||||
|
||||
D4_v2/DS4_v2 to D8ds_v5
|
||||
|
||||
D5_v2/DS5_v2 to D16ds_v5
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||
|
||||
## PAN-296752
|
||||
|
||||
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
|
||||
|
||||
A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.
|
||||
|
||||
## 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.
|
||||
|
||||
## PAN-292344
|
||||
|
||||
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-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-291716
|
||||
|
||||
(PA-460 firewalls only) The firewall experiences an out-of-memory (OOM) condition and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||
|
||||
## PAN-291661
|
||||
|
||||
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-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-287803
|
||||
|
||||
After upgrading to PAN-OS 11.1.6-h4, users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||
|
||||
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.
|
||||
|
||||
## PAN-286848
|
||||
|
||||
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.
|
||||
|
||||
## 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-286231
|
||||
|
||||
When performing a partial Commit and Push on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||
|
||||
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 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.
|
||||
|
||||
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.
|
||||
|
||||
## 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-285590
|
||||
|
||||
VM-Series firewalls deployed behind an AWS GWLB might experience 100% dataplane CPU utilization when an Anti-Spyware profile is applied to traffic.
|
||||
|
||||
## 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.
|
||||
|
||||
## PAN-283467
|
||||
|
||||
```caveat
|
||||
PA-3400 Series firewalls only
|
||||
```
|
||||
|
||||
The firewall might unexpectedly reboot and enter maintenance mode due to a ctd-agent out-of-memory (OOM) condition when undergoing advanced services load testing with a high volume of IoT EAL log forwarding.
|
||||
|
||||
Workaround: Limit the number of EAL logs generated by the firewall using the following CLI command: debug iot eal key-value EAL_PENDING_BYTES=1000.
|
||||
|
||||
## 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-282277
|
||||
|
||||
```caveat
|
||||
PA-3260 firewalls only
|
||||
```
|
||||
|
||||
An interface unexpectedly moves out of Link Aggregation Control Protocol (LACP), which causes an out-of-memory (OOM) condition on the *logrcvr* process, resulting in the interface going down and then automatically coming back up without intervention.
|
||||
|
||||
## PAN-282236
|
||||
|
||||
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented. IPv6 SSL sessions may not be established if the client hello arrives in multiple segments.
|
||||
|
||||
## 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-280471
|
||||
|
||||
When applying filters or searching for logs in the PanoramaMonitorLogssection, you might experience slow performance.
|
||||
|
||||
## 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
|
||||
|
||||
## 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-279604
|
||||
|
||||
The scheduled SaaS application usage reports are incorrectly generated and only the login page appears instead of the intended report content.
|
||||
|
||||
## 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-278322
|
||||
|
||||
VM-Series firewalls deployed behind an AWS GWLB might display an incorrect or empty Source User field in traffic logs and session details.
|
||||
|
||||
## 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.
|
||||
|
||||
## PAN-277034
|
||||
|
||||
WildFire reports might not fully display or be downloadable because some static resources fail to load.
|
||||
|
||||
## PAN-275905
|
||||
|
||||
A high volume of incoming logs to a Collector Group can significantly increase CPU usage on the Elasticsearch and Management Server, potentially causing process instability or crashes.
|
||||
|
||||
## 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-275077
|
||||
|
||||
DNS Security intermittently logs malicious domain URLs as alert instead of taking a sinkhole action, even when configured to sinkhole malicious DNS domains.
|
||||
|
||||
## PAN-275047
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls only
|
||||
```
|
||||
|
||||
After an upgrade, the firewall is unable to send logs to the Strata Logging Service (SLS) when using a specific proxy server, and the SSL connection status displays as failed when attempting to forward logs through the web proxy.
|
||||
|
||||
## PAN-274314
|
||||
|
||||
```caveat
|
||||
PA-1400 Series firewalls, PA-3400 Series firewalls, and PA-5400 Series firewalls only
|
||||
```
|
||||
|
||||
When the pan_task process restarts, control plane packets are dropped, which can impact LACP and pings to host interfaces.
|
||||
|
||||
## PAN-274146
|
||||
|
||||
VM-Series firewalls deployed behind an AWS GWLB might crash and reboot unexpectedly if tunnel sessions are moving through the firewall.
|
||||
|
||||
## PAN-272085
|
||||
|
||||
When DoH is enabled for DNS Security, multiple DoH transactions in a single HTTP/1 connection might unexpectedly cause the firewall to crash and reboot.
|
||||
|
||||
Workaround: Manually disable DoH support for DNS Security using the set deviceconfig setting dns-over-https enable no CLI command. Alternatively, you can remove the DNS Security configuration used to handle DoH traffic.
|
||||
|
||||
## PAN-271913
|
||||
|
||||
Firewalls in HA configurations were experiencing consistent memory leaks on the active firewall, leading unexpected failovers while using Cloud Identity Engine (CIE).
|
||||
|
||||
## PAN-270549
|
||||
|
||||
Some TLS connections are not handled correctly leading to an instability in the dataplane of PAN-OS.
|
||||
|
||||
## PAN-270224
|
||||
|
||||
When querying for logs in the Monitor tab in Panorama, some forwarded logs might be missing from the results.
|
||||
|
||||
## PAN-269106
|
||||
|
||||
When using a cloud-based ML detection engine (MICA), the wifclient might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||
|
||||
Workaround: Disable CRL using the following CLI command:debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False
|
||||
|
||||
## PAN-269027
|
||||
|
||||
External dynamic lists cause the commit time on the firewall to be higher than expected.
|
||||
|
||||
## PAN-268705
|
||||
|
||||
The firewall intermittently fails to process FTP traffic.
|
||||
|
||||
Workaround: Configure an application override policy rule for FTP applications.
|
||||
|
||||
## PAN-268229
|
||||
|
||||
If you configure an IPSec tunnel, when traffic from the tunnel egresses the firewall on an ECMP route, the firewall stops responding.
|
||||
|
||||
Workaround: Disable ECMP for the virtual router or logical router to avoid this issue.
|
||||
|
||||
## PAN-268127
|
||||
|
||||
Tagging a firewall in Panorama produces an error, TypeError: Cannot read properties of undefined (reading 'serial'), and does not tag as expected.
|
||||
|
||||
## PAN-266900
|
||||
|
||||
In Panorama, the OK button does not work when trying to install configurations to a managed firewall from the Managed DevicesSummaryInstall, even after selecting the update type and file from the dropdown and choosing the firewall.
|
||||
|
||||
## PAN-263987
|
||||
|
||||
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-263973
|
||||
|
||||
After upgrading, the log collectors might experience a low incoming logging rate.
|
||||
|
||||
## PAN-263208
|
||||
|
||||
```caveat
|
||||
PA-5440 and PA-5445 firewalls only
|
||||
```
|
||||
|
||||
High system load can cause the firewall to generate interrupts and trigger dataplane crashes.
|
||||
|
||||
## 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-260212
|
||||
|
||||
When viewing Applications (ObjectsApplications), child App-IDs may be listed under the incorrect container App-ID.
|
||||
|
||||
## PAN-260015
|
||||
|
||||
When Inline Cloud Analysis features are enabled, an issue related to loopback data handling might cause the firewall to unexpectedly reboot.
|
||||
|
||||
Workaround: Disable any Inline Cloud Analysis features on the firewall (e.g. Advanced Threat Prevention Inline Cloud Analysis, WildFire Inline Cloud Analysis, App-ID Cloud Engine, etc) on the firewall.
|
||||
|
||||
## 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).
|
||||
|
||||
## PAN-259423
|
||||
|
||||
When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on the GlobalProtect gateway, the gpsvc gets stuck during renewal and after HA failover.
|
||||
|
||||
## PAN-258680
|
||||
|
||||
When you remove Security profile groups from a Security policy rule via the CLI and then do a partial commit, the Security policy rule is deleted.
|
||||
|
||||
Workaround: Perform one of the following:
|
||||
|
||||
Perform a full commit.Remove the profile setting group manually in the UI by changing the Profile Group to None, and then, perform a partial commit.
|
||||
|
||||
Perform a full commit.
|
||||
|
||||
Remove the profile setting group manually in the UI by changing the Profile Group to None, and then, perform a partial commit.
|
||||
|
||||
## PAN-258570
|
||||
|
||||
The varrcvr process might progressively use more memory resulting in unexpected reboots when WildFire file forwarding is handling PE files.
|
||||
|
||||
## PAN-257267
|
||||
|
||||
```caveat
|
||||
VM-Series firewalls only
|
||||
```
|
||||
|
||||
A warning message stating that the configuration size exceeded the maximum recommended configuration size, was observed during commit completion and critical system log in the VM-Series firewall.
|
||||
|
||||
## PAN-254901
|
||||
|
||||
If the GlobalProtect license is not installed or is invalid on the device, GlobalProtect user-to-IP address mapping is unexpectedly removed, despite the fact that the tunnel for a specific user is active and traffic is successfully passing through it. Due to the user-to-IP mapping being removed, the traffic matches the wrong policy.
|
||||
|
||||
## 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.
|
||||
|
||||
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
|
||||
|
||||
The auto commit job may take longer than expected to complete when the Panorama management server is in Panorama or Log Collector mode.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
|
||||
## PAN-248836
|
||||
|
||||
The Advanced DNS Security trial license and trial license information cannot be activated and viewed, respectively, on a managed firewall (with expired or active status) from Panorama. These tasks can only be performed on the firewall.
|
||||
|
||||
## PAN-239612
|
||||
|
||||
When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCPv4 relay agent functions successfully, but DHCPv6 relay agent doesn't work.
|
||||
|
||||
## 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.
|
||||
|
||||
Workaround: Unconfigure and configure the Inherited Interface.
|
||||
|
||||
## 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-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-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