Revise PAN-OS 11.2 known issues
This commit is contained in:
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,874 @@
|
||||
<table class="table colsep rowsep table-striped">
|
||||
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||
|
||||
<colgroup>
|
||||
<col style="width: 34%" />
|
||||
<col style="width: 66%" />
|
||||
</colgroup>
|
||||
<thead class="thead">
|
||||
<tr class="row rowsep">
|
||||
<th class="entry">
|
||||
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||
</th>
|
||||
<th class="entry">
|
||||
<div class="p"><b class="ph b">Description</b></div>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
||||
<tbody class="tbody">
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">WF500-6271</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
A WildFire cluster node that has been configured with an IPv6
|
||||
management port might not display the signature status when using the
|
||||
following CLI:
|
||||
<span class="ph codeph"
|
||||
>show wildfire global signature-status sha256 equal
|
||||
<SHA_256_Value></span
|
||||
>
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Gracefully restart the affected
|
||||
Wildfire cluster nodes.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">WF500-6259</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When a WildFire cluster node configured as a server or worker node is
|
||||
rebooted, issuing the CLI command,
|
||||
<span class="ph codeph">global sample-status</span> does not update
|
||||
the samples processed list on the active controller and non-server
|
||||
worker nodes.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Gracefully restart the affected
|
||||
WildFire active controller and passive controller in the cluster.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">WF500-6270</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
The WildFire cluster server and worker nodes might disconnect from the
|
||||
Wildfire cluster management network, resulting in a notifier process
|
||||
exit on WildFire cluster controllers.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Gracefully restart the WildFire
|
||||
cluster node where the process exit occurred.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">WF500-6222</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When WildFire secure cluster communication is enabled using a custom
|
||||
DNS, the cluster formation might fail due to cluster management
|
||||
communication issues.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Do not configure a custom DNS when
|
||||
WildFire secure cluster communication is enabled.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">WF500-6176</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When Panorama is used to manage a WildFire cluster, switchover
|
||||
functionality for active and passive controller roles is not
|
||||
available.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-308564</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation
|
||||
for an interface but have the
|
||||
<span class="ph uicontrol">Don't Fragment (DF)</span> bit set. This
|
||||
results in unexpected packet drops. This affects client to server
|
||||
sessions when using SD-WAN for NGFW.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Allow fragmenting packets with DF bit
|
||||
set (<span class="ph userinput"
|
||||
>debug dataplane set ip4-ignore-df yes</span
|
||||
>).
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-308507</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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 <span class="ph codeph">log-receiver</span> process temporarily
|
||||
resolves the issue, but the streams become inactive again after
|
||||
approximately 1-2 hours. This intermittent inactivity results in log
|
||||
loss.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-295645</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When a WildFire cluster is configured centrally using Panorama, it
|
||||
initiates a series of processes, including a software install and
|
||||
reboot, in an order that will leave the resulting WildFire cluster in
|
||||
an unusable state.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-288525</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When the Enterprise DLP data filtering profile is configured with a
|
||||
<span class="ph uicontrol">Block</span> action and is used in
|
||||
conjunction with Advanced Threat Prevention, which is configured with
|
||||
an action of <span class="ph uicontrol">reset-both</span>,
|
||||
<span class="ph uicontrol">reset-server</span>,
|
||||
<span class="ph uicontrol">reset-client</span>, or
|
||||
<span class="ph uicontrol">drop</span> for the
|
||||
<span class="ph uicontrol">HTTP Command and Control detector</span>,
|
||||
Dropbox file uploads that exceed the maximum configured file size
|
||||
action will fail.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Configure the Advanced Threat
|
||||
Prevention Inline Cloud analysis (<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Objects</span
|
||||
><span class="ph uicontrol">Security Profiles</span
|
||||
><span class="ph uicontrol">Anti-Spyware</span></span
|
||||
>) action for the HTTP Command and Control detector to
|
||||
<span class="ph uicontrol">alert</span>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-285061</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When Enterprise DLP is enabled, file uploads might unexpectedly fail
|
||||
when 100 continue response is received from the server during file
|
||||
uploads.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-284700</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
File downloads for content encoded with zstd (Zstandard), such as
|
||||
specific content from box.com, fail when using Enterprise DLP because
|
||||
zstd decompression is not supported in PAN-OS.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-283429</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When you use custom certificates for the connection between Panorama
|
||||
and a log collector, the automated renewal for the predefined
|
||||
ElasticSearch certificates gets disrupted.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround</b>: 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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-260851</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
From the NGFW or Panorama CLI, you can override the existing
|
||||
application tag even if Disable Override is enabled for the
|
||||
application (<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Objects</span
|
||||
><span class="ph uicontrol">Applications</span></span
|
||||
>) tag.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-260212</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When viewing <span class="ph uicontrol">Applications</span> (<span
|
||||
class="ph menucascade"
|
||||
><span class="ph uicontrol">Objects</span
|
||||
><span class="ph uicontrol">Applications</span></span
|
||||
>), child App-IDs may be listed under the incorrect container App-ID.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-259853</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When the DHCP server is enabled for GlobalProtect, the commit error
|
||||
message is not properly displayed when
|
||||
<span class="ph uicontrol">Any</span> is selected as the source
|
||||
interface in the service router configuration (
|
||||
<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Device</span
|
||||
><span class="ph uicontrol">Setup</span
|
||||
><span class="ph uicontrol">Service</span
|
||||
><span class="ph uicontrol"></span
|
||||
><span class="ph uicontrol"
|
||||
>Service Router Configuration</span
|
||||
></span
|
||||
>).
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-259423</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-254236</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Disable
|
||||
<a
|
||||
class="xref"
|
||||
href="https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-features/inspect-ssl-tls-handshakes"
|
||||
title=""
|
||||
data-scope="external"
|
||||
data-format="html"
|
||||
data-type=""
|
||||
target="_blank"
|
||||
>SSL/TLS handshake inspection</a
|
||||
>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-254108</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
when upgrading or downgrading a Panorama management server (<span
|
||||
class="ph menucascade"
|
||||
><span class="ph uicontrol">Panorama</span
|
||||
><span class="ph uicontrol">Software</span></span
|
||||
>), managed device (<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Panorama</span
|
||||
><span class="ph uicontrol">Device Deployment</span
|
||||
><span class="ph uicontrol">Software</span></span
|
||||
>), or standalone firewall (<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Device</span
|
||||
><span class="ph uicontrol">Software</span></span
|
||||
>), <span class="ph uicontrol">Base Releases</span> and
|
||||
<span class="ph uicontrol">Preferred Releases</span> settings are
|
||||
checked (enabled) by default and cause no PAN-OS software images to
|
||||
display.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Uncheck (disable)
|
||||
<span class="ph uicontrol">Base Releases</span> or
|
||||
<span class="ph uicontrol">Preferred Releases</span> to display either
|
||||
the available base PAN-OS or preferred PAN-OS releases available to
|
||||
download and install.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-253963</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
The auto commit job may take longer than expected to complete when the
|
||||
Panorama management server is in Panorama or Log Collector mode.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-252661</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
If you change the service route of gp-ip-mgmt in
|
||||
<b class="ph b"
|
||||
>Device > Setup > Services > Service Features >
|
||||
gp-ip-mgmt</b
|
||||
>
|
||||
and <b class="ph b">Commit</b>, the change won’t take effect.
|
||||
gp-ip-mgmt continues to use the last committed service route.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> After you change the service route
|
||||
interface for gp-ip-mgmt, navigate to either a GlobalProtect portal or
|
||||
gateway, click <b class="ph b">OK </b>to save the configuration, and
|
||||
<b class="ph b">Commit </b>the changes. This commit will include the
|
||||
service route change.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-250246</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
Panorama and the firewall display inconsistent IP addresses for
|
||||
dynamic address group members after manually syncing.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-250062</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
Device telemetry might fail at configured intervals due to bundle
|
||||
generation issues.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-248836</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-247728</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
When Advanced Routing is enabled, IP multicast is not supported. An
|
||||
upcoming version will provide support for this feature. Customers who
|
||||
have multicast configured or who plan to deploy multicast routing
|
||||
should not upgrade to 11.2.0. Additionally, when Advanced Routing is
|
||||
enabled, the BGP dampening configuration isn't applied to any peers or
|
||||
peer group; the configuration is preserved but has no effect on BGP.
|
||||
Customers can use BGP even if they have applied a Dampening profile to
|
||||
a specific set of peers. The issue doesn't affect any other BGP
|
||||
features.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-241994</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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
|
||||
<a
|
||||
class="xref"
|
||||
href="https://kb.vmware.com/s/article/2007240"
|
||||
title=""
|
||||
data-scope="external"
|
||||
data-format="html"
|
||||
data-type=""
|
||||
target="_blank"
|
||||
rel="nofollow"
|
||||
>compatibility matrix</a
|
||||
>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-239612</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-237106</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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:
|
||||
</div>
|
||||
<ul id="panos-known-issues-11.2.11_ul-t2x_dxs_wgc" class="ul">
|
||||
<li class="li">
|
||||
<span class="ph systemoutput"
|
||||
>db-serialno can be at most 40 characters</span
|
||||
>
|
||||
</li>
|
||||
<li class="li">
|
||||
<span class="ph systemoutput">db-serialno is invalid</span>
|
||||
</li>
|
||||
</ul>
|
||||
<b class="ph b">Workaround:</b>
|
||||
<div class="p">
|
||||
To resolve this issue, use the following CLI commands with the LSVPN
|
||||
satellite serial number to manually delete or revoke the affected
|
||||
certificates:
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Delete certificate information</b>:<span
|
||||
class="ph userinput"
|
||||
>delete sslmgr-store certificate-info portal name
|
||||
<var class="keyword varname"><name></var> serialno
|
||||
<var class="keyword varname"><satellite_serial></var></span
|
||||
>
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Revoke satellite certificates</b>:<span
|
||||
class="ph userinput"
|
||||
>delete sslmgr-store satellite-info-revoke-certificate portal
|
||||
<var class="keyword varname"><name></var> serialno
|
||||
<var class="keyword varname"
|
||||
><list_of_satellite_serials></var
|
||||
></span
|
||||
>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-236649</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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,
|
||||
<span class="ph userinput">show interface all</span>.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Unconfigure and configure the
|
||||
Inherited Interface.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-234015</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-207442</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
For M-700 appliances in an active/passive high availability (<span
|
||||
class="ph menucascade"
|
||||
><span class="ph uicontrol">Panorama</span
|
||||
><span class="ph uicontrol">High Availability</span></span
|
||||
>) configuration, the
|
||||
<span class="ph systemoutput">active-primary</span> HA peer
|
||||
configuration sync to the
|
||||
<span class="ph systemoutput">secondary-passive</span> HA peer may
|
||||
fail. When the config sync fails, the job Results is
|
||||
<span class="ph systemoutput">Successful</span>
|
||||
(<span class="ph uicontrol">Tasks</span>), however the sync status on
|
||||
the <span class="ph uicontrol">Dashboard</span> displays as
|
||||
<span class="ph systemoutput">Out of Sync</span> for both HA peers.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround</b>: Perform a local commit on the
|
||||
<span class="ph systemoutput">active-primary</span> HA peer and then
|
||||
synchronize the HA configuration.
|
||||
</div>
|
||||
<ol id="panos-known-issues-11.2.11_ol_aqy_kbp_qxb" class="ol">
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
<a
|
||||
class="xref"
|
||||
href="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"
|
||||
title=""
|
||||
data-scope="external"
|
||||
data-format="html"
|
||||
data-type=""
|
||||
target="_blank"
|
||||
>Log in to the Panorama web interface</a
|
||||
>
|
||||
of the <span class="ph systemoutput">active-primary</span> HA
|
||||
peer.
|
||||
</div>
|
||||
</li>
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
Select <span class="ph uicontrol">Commit</span> and
|
||||
<span class="ph uicontrol">Commit to Panorama</span>.
|
||||
</div>
|
||||
</li>
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
In the <span class="ph systemoutput">active-primary</span> HA peer
|
||||
<span class="ph uicontrol">Dashboard</span>, click
|
||||
<span class="ph uicontrol">Sync to Peer</span> in the High
|
||||
Availability widget.
|
||||
</div>
|
||||
</li>
|
||||
</ol>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-206909</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
The Dedicated Log Collector is unable to reconnect to the Panorama
|
||||
management server if the <span class="ph systemoutput">configd</span>
|
||||
process crashes. This results in the Dedicated Log Collector losing
|
||||
connectivity to Panorama despite the managed collector connection
|
||||
<span class="ph systemoutput">Status</span> (<span
|
||||
class="ph menucascade"
|
||||
><span class="ph uicontrol">Panorama</span
|
||||
><span class="ph uicontrol">Managed Collector</span></span
|
||||
>) displaying <span class="ph systemoutput">connected</span> and the
|
||||
managed colletor <span class="ph systemoutput">Health</span> status
|
||||
displaying as healthy.
|
||||
</div>
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Restart the
|
||||
<span class="ph systemoutput">mgmtsrvr</span> process on the Dedicated
|
||||
Log Collector.
|
||||
</div>
|
||||
<ol id="panos-known-issues-11.2.11_ol_pdy_4bm_lvb" class="ol">
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
<a
|
||||
class="xref"
|
||||
href="https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli"
|
||||
title=""
|
||||
data-scope="external"
|
||||
data-format="html"
|
||||
data-type=""
|
||||
target="_blank"
|
||||
>Log in to the Dedicated Log Collector CLI</a
|
||||
>.
|
||||
</div>
|
||||
</li>
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
Confirm the Dedicated Log Collector is disconnected from Panorama.
|
||||
</div>
|
||||
<!-- FM Dita Overlay for Code -->
|
||||
<div class="code-wrap">
|
||||
<pre
|
||||
class="pre codeblock"
|
||||
data-label="PRE CODEBLOCK"
|
||||
><div style="display: inline;"><span class="ph systemoutput hljs">admin></span><span class="ph userinput hljs sql"> <span class="hljs-keyword">show</span> panorama-<span class="hljs-keyword">status</span></span></div></pre>
|
||||
<div class="p">
|
||||
Verify the <span class="ph systemoutput">Connected</span> status
|
||||
is <span class="ph systemoutput">no</span>.
|
||||
</div>
|
||||
</div>
|
||||
</li>
|
||||
<li class="li">
|
||||
<div class="p">
|
||||
Restart the <span class="ph systemoutput">mgmtsrvr</span> process.
|
||||
</div>
|
||||
<!-- FM Dita Overlay for Code -->
|
||||
<div class="code-wrap">
|
||||
<pre
|
||||
class="pre codeblock"
|
||||
data-label="PRE CODEBLOCK"
|
||||
><div style="display: inline;"><span class="ph systemoutput hljs">admin></span><span class="ph userinput hljs nginx"> <span class="hljs-attribute">debug</span> software restart process management-server</span></div></pre>
|
||||
</div>
|
||||
</li>
|
||||
</ol>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-197588</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-197419</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
(<tt class="ph tt">PA-1400 Series firewalls only</tt>) In
|
||||
<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Network</span
|
||||
><span class="ph uicontrol">Interface</span
|
||||
><span class="ph uicontrol">Ethernet</span></span
|
||||
>, the power over Ethernet (PoE) ports do not display a
|
||||
<span class="ph uicontrol">Tag</span> value.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-196758</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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
|
||||
<span class="ph uicontrol">Preview Changes</span> (<span
|
||||
class="ph menucascade"
|
||||
><span class="ph uicontrol">Commit</span
|
||||
><span class="ph uicontrol">Push to Devices</span
|
||||
><span class="ph uicontrol">Edit Selections</span></span
|
||||
>
|
||||
or
|
||||
<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Commit</span
|
||||
><span class="ph uicontrol">Commit and Push</span
|
||||
><span class="ph uicontrol">Edit Selections</span></span
|
||||
>).
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-195968</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
(<tt class="ph tt">PA-1400 Series firewalls only</tt>) 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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-187685</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
On the Panorama management server, the Template Status displays no
|
||||
synchronization status (<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Panorama</span
|
||||
><span class="ph uicontrol">Managed Devices</span
|
||||
><span class="ph uicontrol">Summary</span></span
|
||||
>) after a bootstrapped firewall is successfully added to Panorama.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> After the bootstrapped firewall is
|
||||
successfully added to Panorama,
|
||||
<a
|
||||
class="xref"
|
||||
href="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"
|
||||
title=""
|
||||
data-scope="external"
|
||||
data-format="html"
|
||||
data-type=""
|
||||
target="_blank"
|
||||
>log in to the Panorama web interface</a
|
||||
>
|
||||
and select
|
||||
<span class="ph menucascade"
|
||||
><span class="ph uicontrol">Commit</span
|
||||
><span class="ph uicontrol">Push to Devices</span></span
|
||||
>.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-187407</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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
|
||||
<span class="ph uicontrol"
|
||||
>Hold client request for category lookup </span
|
||||
>and the action set to
|
||||
<span class="ph uicontrol">Reset-Both</span> and the URL cache has
|
||||
been cleared, the first request for inline cloud analysis will be
|
||||
bypassed.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-184406</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
Using the CLI to add a RAID disk pair to an M-700 appliance causes the
|
||||
dmdb process to crash.
|
||||
</div>
|
||||
<div class="p">
|
||||
<b class="ph b">Workaround:</b> Contact customer support to stop the
|
||||
dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-183404</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
Static IP addresses are not recognized when "and" operators are used
|
||||
with IP CIDR range.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="row rowsep">
|
||||
<td class="entry">
|
||||
<div class="p"><b class="ph b">PAN-181933</b></div>
|
||||
</td>
|
||||
<td class="entry relcol">
|
||||
<div class="p">
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -10,69 +10,112 @@ 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-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-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-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.7-h3 Addressed Issuesand PAN-OS 11.2.8 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
|
||||
|
||||
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-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-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,7 +123,7 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-279415
|
||||
|
||||
@@ -92,15 +135,27 @@ The system MAC address of the aggregate interface is the same on both the active
|
||||
|
||||
## 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-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.2.5 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-262287
|
||||
|
||||
@@ -108,14 +163,18 @@ 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
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-257615
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The Panorama web interface intermittently displays logs or fails to display logs completely.
|
||||
|
||||
## PAN-257045
|
||||
@@ -124,11 +183,11 @@ The firewall using the Advanced Routing Engine loses PIM Hello messages after a
|
||||
|
||||
## PAN-256780
|
||||
|
||||
The firewall using the Advanced Routing Engine has inconsistent formatting of multicast output from the CLI command: show ip igmp sources json.
|
||||
The firewall using the Advanced Routing Engine has inconsistent formatting of multicast output from the CLI command: `show ip igmp sources json`.
|
||||
|
||||
## PAN-256343
|
||||
|
||||
When the firewall is using the Advanced Routing Engine and OSPFv3 is configured, the interface and area information fails to appear in the CLI or the user interface. Additionally, you shouldn't use the CLI command show advanced-routing ospf interface because it disrupts traffic.
|
||||
When the firewall is using the Advanced Routing Engine and OSPFv3 is configured, the interface and area information fails to appear in the CLI or the user interface. Additionally, you shouldn't use the CLI command `show advanced-routing ospf interface` because it disrupts traffic.
|
||||
|
||||
## PAN-254305
|
||||
|
||||
@@ -136,9 +195,13 @@ DHCP request is not sent when the service route is configured.
|
||||
|
||||
## PAN-254236
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.1 Addressed Issues.
|
||||
```
|
||||
|
||||
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-254143
|
||||
|
||||
@@ -146,9 +209,9 @@ A firewall that uses the Advanced Routing Engine fails to add a local route to t
|
||||
|
||||
## 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
|
||||
|
||||
@@ -158,6 +221,16 @@ The auto commit job may take longer than expected to complete when the Panorama
|
||||
|
||||
A firewall using the Advanced Routing Engine fails to come up and fails to display OSPFv3 neighbor information.
|
||||
|
||||
## PAN-252661
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.1 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## PAN-250062
|
||||
|
||||
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||
@@ -176,15 +249,19 @@ The firewall using the Advanced Routing Engine doesn't properly display the inte
|
||||
|
||||
## PAN-247728
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.1 Addressed Issues
|
||||
```
|
||||
|
||||
When Advanced Routing is enabled, IP multicast is not supported. An upcoming version will provide support for this feature. Customers who have multicast configured or who plan to deploy multicast routing should not upgrade to 11.2.0. Additionally, when Advanced Routing is enabled, the BGP dampening configuration isn't applied to any peers or peer group; the configuration is preserved but has no effect on BGP. Customers can use BGP even if they have applied a Dampening profile to a specific set of peers. The issue doesn't affect any other BGP features.
|
||||
|
||||
## PAN-247221
|
||||
|
||||
The firewall using the Advanced Routing Engine fails to display output for the CLI command: show advanced-routing bgp peer received-routes.
|
||||
The firewall using the Advanced Routing Engine fails to display output for the CLI command: `show advanced-routing bgp peer received-routes`.
|
||||
|
||||
## PAN-241536
|
||||
|
||||
On the Panorama management server, a user with an Admin Role is unable to modify or add filters to profiles under PanoramaNetworkRoutingRouting ProfilesFilters, despite having the necessary read and write privileges.
|
||||
On the Panorama management server, a user with an Admin Role is unable to modify or add filters to profiles under **Panorama** > **Network** > **Routing** > **Routing Profiles** > **Filters**, despite having the necessary read and write privileges.
|
||||
|
||||
## PAN-239612
|
||||
|
||||
@@ -192,43 +269,24 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -240,11 +298,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
|
||||
|
||||
@@ -256,19 +314,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
|
||||
|
||||
@@ -280,4 +338,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.2.1 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.
|
||||
|
||||
@@ -10,69 +10,112 @@ 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-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-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-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-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-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.7-h3 Addressed Issuesand PAN-OS 11.2.8 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
|
||||
|
||||
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-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-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,7 +123,7 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-279746
|
||||
|
||||
@@ -92,15 +135,27 @@ Service routes configured for a data plane interface might incorrectly route tra
|
||||
|
||||
## 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-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.2.5 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-262287
|
||||
|
||||
@@ -108,15 +163,19 @@ 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-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-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## PAN-259423
|
||||
|
||||
@@ -124,13 +183,17 @@ When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on
|
||||
|
||||
## PAN-257615
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The Panorama web interface intermittently displays logs or fails to display logs completely.
|
||||
|
||||
## 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
|
||||
|
||||
@@ -150,43 +213,24 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -198,11 +242,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
|
||||
|
||||
@@ -214,19 +258,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
|
||||
|
||||
|
||||
@@ -8,64 +8,106 @@ version: 11.2.10
|
||||
|
||||
A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value>
|
||||
|
||||
Workaround: Gracefully restart the affected Wildfire cluster nodes.
|
||||
**Workaround:** Gracefully restart the affected Wildfire cluster nodes.
|
||||
|
||||
## WF500-6259
|
||||
|
||||
When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes.
|
||||
|
||||
Workaround: Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
**Workaround:** Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
|
||||
## WF500-6270
|
||||
|
||||
The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers.
|
||||
|
||||
Workaround: Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
**Workaround:** Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
|
||||
## WF500-6222
|
||||
|
||||
When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues.
|
||||
|
||||
Workaround: Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
**Workaround:** Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
|
||||
## WF500-6176
|
||||
|
||||
When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
|
||||
|
||||
## PAN-308564
|
||||
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||
|
||||
**Workaround:** Allow fragmenting packets with DF bit set (`debug dataplane set ip4-ignore-df yes`).
|
||||
|
||||
## PAN-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-308418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
When Advanced DNS Security is enabled and experiences unusually high loads, DNS traffic sessions may be impacted, resulting in DNS resolution failures. Traffic logs for these sessions show an end-reason of resources-unavailable.
|
||||
|
||||
Workaround: Disable Advanced DNS Security telemetry (DeviceSetupContent-IDAdvanced DNS Security and uncheck Telemetry Enable).
|
||||
**Workaround:** Disable Advanced DNS Security telemetry (**Device** > **Setup** > **Content-ID** > **Advanced DNS Security** and uncheck **Telemetry Enable**).
|
||||
|
||||
## 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-304576
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.
|
||||
|
||||
Workaround: Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.
|
||||
**Workaround:** Disable HTTP/2 server push using the `set deviceconfig setting http2 server-push no` CLI command.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-302927
|
||||
|
||||
After an upgrade, the Push to Devices window fails to populate the list of devices automatically. If you manually select devices by clicking Edit Selections, the OK button becomes unresponsive and fails to save or close the selection window. Additionally, clicking Cancel might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
After an upgrade, the **Push to Devices** window fails to populate the list of devices automatically. If you manually select devices by clicking **Edit Selections**, the **OK** button becomes unresponsive and fails to save or close the selection window. Additionally, clicking **Cancel** might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
|
||||
## PAN-301801
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.10-h2 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-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.10-h2 Addressed Issues.
|
||||
```
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## 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-295645
|
||||
@@ -74,13 +116,17 @@ When a WildFire cluster is configured centrally using Panorama, it initiates a s
|
||||
|
||||
## 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
|
||||
```
|
||||
|
||||
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-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-285061
|
||||
|
||||
@@ -94,7 +140,7 @@ File downloads for content encoded with zstd (Zstandard), such as specific conte
|
||||
|
||||
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-278688
|
||||
|
||||
@@ -104,7 +150,7 @@ PA-7500, PA-5500, and PA-3500 firewalls only
|
||||
|
||||
When DNS Security packet capture is enabled and a domain name has a length of 62 characters, the DNS Security threat log entry is not generated. On the affected platforms, this condition can also trigger a pan_task crash due to shared memory corruption.
|
||||
|
||||
Workaround: Disable DNS Security packet capture in anti-spyware profiles (ObjectsSecurity ProfilesAnti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.
|
||||
**Workaround:** Disable DNS Security packet capture in anti-spyware profiles (**Objects** > **Security Profiles** > **Anti-Spyware**) and in the **DNS Policies** tab, set **Packet Capture** to **disable**.
|
||||
|
||||
## PAN-273158
|
||||
|
||||
@@ -116,15 +162,15 @@ Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-
|
||||
|
||||
## 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).
|
||||
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
|
||||
|
||||
@@ -134,13 +180,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
|
||||
|
||||
@@ -148,9 +194,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
|
||||
|
||||
@@ -170,7 +216,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
|
||||
|
||||
@@ -180,21 +226,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
|
||||
|
||||
@@ -202,55 +249,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
|
||||
|
||||
@@ -262,11 +282,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
|
||||
|
||||
@@ -278,19 +298,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
|
||||
|
||||
|
||||
@@ -0,0 +1,227 @@
|
||||
---
|
||||
type: Known
|
||||
product: PAN-OS
|
||||
version: 11.2.11
|
||||
---
|
||||
|
||||
## WF500-6271
|
||||
|
||||
A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value>
|
||||
|
||||
**Workaround:** Gracefully restart the affected Wildfire cluster nodes.
|
||||
|
||||
## WF500-6259
|
||||
|
||||
When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes.
|
||||
|
||||
**Workaround:** Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
|
||||
## WF500-6270
|
||||
|
||||
The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers.
|
||||
|
||||
**Workaround:** Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
|
||||
## WF500-6222
|
||||
|
||||
When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues.
|
||||
|
||||
**Workaround:** Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
|
||||
## WF500-6176
|
||||
|
||||
When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
|
||||
|
||||
## PAN-308564
|
||||
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||
|
||||
**Workaround:** Allow fragmenting packets with DF bit set (`debug dataplane set ip4-ignore-df yes`).
|
||||
|
||||
## PAN-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-295645
|
||||
|
||||
When a WildFire cluster is configured centrally using Panorama, it initiates a series of processes, including a software install and reboot, in an order that will leave the resulting WildFire cluster in an unusable state.
|
||||
|
||||
## 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.
|
||||
|
||||
**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-285061
|
||||
|
||||
When Enterprise DLP is enabled, file uploads might unexpectedly fail when 100 continue response is received from the server during file uploads.
|
||||
|
||||
## PAN-284700
|
||||
|
||||
File downloads for content encoded with zstd (Zstandard), such as specific content from box.com, fail when using Enterprise DLP because zstd decompression is not supported in PAN-OS.
|
||||
|
||||
## 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-260851
|
||||
|
||||
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** (**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 ( **Device** > **Setup** > **Service** > **Service 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-254236
|
||||
|
||||
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](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 (**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.
|
||||
|
||||
## 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-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.
|
||||
|
||||
**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
|
||||
|
||||
Panorama and the firewall display inconsistent IP addresses for dynamic address group members after manually syncing.
|
||||
|
||||
## 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-247728
|
||||
|
||||
When Advanced Routing is enabled, IP multicast is not supported. An upcoming version will provide support for this feature. Customers who have multicast configured or who plan to deploy multicast routing should not upgrade to 11.2.0. Additionally, when Advanced Routing is enabled, the BGP dampening configuration isn't applied to any peers or peer group; the configuration is preserved but has no effect on BGP. Customers can use BGP even if they have applied a Dampening profile to a specific set of peers. The issue doesn't affect any other BGP features.
|
||||
|
||||
## 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](https://kb.vmware.com/s/article/2007240).
|
||||
|
||||
## 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-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`
|
||||
|
||||
**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>`
|
||||
|
||||
**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`.
|
||||
|
||||
**Workaround:** Unconfigure and configure the Inherited Interface.
|
||||
|
||||
## PAN-234015
|
||||
|
||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||
|
||||
## PAN-207442
|
||||
|
||||
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.
|
||||
|
||||
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` (**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.
|
||||
|
||||
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
|
||||
|
||||
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 **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** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit 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 (**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](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.
|
||||
|
||||
## 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.
|
||||
@@ -10,36 +10,84 @@ 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-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-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-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-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-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.7-h3 Addressed Issuesand PAN-OS 11.2.8 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
|
||||
|
||||
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.
|
||||
@@ -50,33 +98,28 @@ When SSL Inbound Inspection is enabled and the firewall receives fragmented Clie
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -84,7 +127,7 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-279746
|
||||
|
||||
@@ -96,21 +139,33 @@ Service routes configured for a data plane interface might incorrectly route tra
|
||||
|
||||
## 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-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.2.5 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-263226
|
||||
|
||||
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||
|
||||
Workaround: Disable Client Hello accumulation using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||
|
||||
## PAN-262287
|
||||
|
||||
@@ -118,19 +173,23 @@ 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-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-259769
|
||||
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||
|
||||
## 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
|
||||
|
||||
@@ -138,13 +197,17 @@ When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on
|
||||
|
||||
## PAN-257615
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.3 Addressed Issues.
|
||||
```
|
||||
|
||||
The Panorama web interface intermittently displays logs or fails to display logs completely.
|
||||
|
||||
## 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
|
||||
|
||||
@@ -164,43 +227,24 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -212,11 +256,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
|
||||
|
||||
@@ -228,19 +272,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
|
||||
|
||||
|
||||
@@ -10,36 +10,84 @@ 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-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-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-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-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-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
|
||||
|
||||
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.
|
||||
@@ -50,33 +98,28 @@ When SSL Inbound Inspection is enabled and the firewall receives fragmented Clie
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -84,7 +127,7 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-279746
|
||||
|
||||
@@ -96,27 +139,43 @@ Service routes configured for a data plane interface might incorrectly route tra
|
||||
|
||||
## 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-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.2.5 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-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
|
||||
|
||||
@@ -124,9 +183,9 @@ When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on
|
||||
|
||||
## 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
|
||||
|
||||
@@ -146,43 +205,24 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -194,11 +234,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
|
||||
|
||||
@@ -210,19 +250,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
|
||||
|
||||
|
||||
@@ -10,25 +10,41 @@ 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-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.
|
||||
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
@@ -36,40 +52,54 @@ Workaround: Change the vsys display name so that it doesn't reference an existin
|
||||
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-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-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-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
|
||||
@@ -78,8 +108,28 @@ 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
|
||||
|
||||
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.
|
||||
@@ -92,7 +142,7 @@ 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-287803
|
||||
|
||||
@@ -100,57 +150,63 @@ 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.4-h10 Addressed Issues
|
||||
```
|
||||
|
||||
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||
|
||||
## PAN-286255
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 11.2.4-h6 This issue is now resolved. See PAN-OS 11.2.4-h7 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
**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.
|
||||
```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-285590
|
||||
|
||||
@@ -158,7 +214,11 @@ VM-Series firewalls deployed behind an AWS GWLB might experience 100% dataplane
|
||||
|
||||
## 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-283467
|
||||
|
||||
@@ -168,13 +228,13 @@ 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.
|
||||
**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.
|
||||
**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
|
||||
|
||||
@@ -186,6 +246,10 @@ An interface unexpectedly moves out of Link Aggregation Control Protocol (LACP),
|
||||
|
||||
## PAN-282236
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h5 only)
|
||||
```
|
||||
|
||||
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
|
||||
@@ -194,38 +258,43 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-279901
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h6 through PAN-OS 11.2.4-h9) This issue is now resolved. See PAN-OS 11.2.4-h11 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-279746
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h1 through PAN-OS 11.2.4-h5)
|
||||
```
|
||||
|
||||
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
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 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-279604
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h4 only)
|
||||
```
|
||||
|
||||
The scheduled SaaS application usage reports are incorrectly generated and only the login page appears instead of the intended report content.
|
||||
|
||||
## PAN-279415
|
||||
@@ -238,27 +307,43 @@ VM-Series firewalls deployed behind an AWS GWLB might display an incorrect or em
|
||||
|
||||
## 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-275905
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h4 only)
|
||||
```
|
||||
|
||||
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.
|
||||
```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-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.2.5 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-275077
|
||||
|
||||
DNS Security intermittently logs malicious domain URLs as alert instead of taking a sinkhole action, even when configured to sinkhole malicious DNS domains.
|
||||
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
|
||||
|
||||
@@ -282,12 +367,20 @@ VM-Series firewalls deployed behind an AWS GWLB might crash and reboot unexpecte
|
||||
|
||||
## PAN-272085
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h4 only) This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
**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
|
||||
|
||||
```caveat
|
||||
(PAN-OS 11.2.4-h9 only) This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
Firewalls in HA configurations were experiencing consistent memory leaks on the active firewall, leading unexpected failovers while using Cloud Identity Engine (CIE).
|
||||
|
||||
## PAN-270549
|
||||
@@ -296,37 +389,57 @@ Some TLS connections are not handled correctly leading to an instability in the
|
||||
|
||||
## PAN-270224
|
||||
|
||||
When querying for logs in the Monitor tab in Panorama, some forwarded logs might be missing from the results.
|
||||
```caveat
|
||||
PAN-OS 11.2.4-h4 only This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
```caveat
|
||||
PAN-OS 11.2.4-h4 only This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
Workaround: Disable CRL using the following CLI command:debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False
|
||||
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
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
**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.
|
||||
**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.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
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.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install**, even after selecting the update type and file from the dropdown and choosing the firewall.
|
||||
|
||||
## PAN-263987
|
||||
|
||||
@@ -334,6 +447,10 @@ When a NAT traversal (NAT-T or UDP encapsulation) IPSec tunnel is terminated on
|
||||
|
||||
## PAN-263973
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.4-h9 Addressed Issues and PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
After upgrading, the log collectors might experience a low incoming logging rate.
|
||||
|
||||
## PAN-263208
|
||||
@@ -346,25 +463,37 @@ High system load can cause the firewall to generate interrupts and trigger datap
|
||||
|
||||
## PAN-261429
|
||||
|
||||
The command show auth radius-require-msg-authentic might return no output.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
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-260015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
**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).
|
||||
```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
|
||||
|
||||
@@ -372,18 +501,23 @@ When the GlobalProtect DHCP feature is enabled with two primary DHCP servers on
|
||||
|
||||
## PAN-258680
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
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:
|
||||
**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.
|
||||
- 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
|
||||
|
||||
```caveat
|
||||
This issue affects PAN-OS 11.2.4-h4. This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues.
|
||||
```
|
||||
|
||||
The varrcvr process might progressively use more memory resulting in unexpected reboots when WildFire file forwarding is handling PE files.
|
||||
|
||||
## PAN-257267
|
||||
@@ -396,13 +530,17 @@ A warning message stating that the configuration size exceeded the maximum recom
|
||||
|
||||
## PAN-254901
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.5 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
@@ -422,43 +560,24 @@ When the firewall is running PAN-OS 11.2.0 and Advanced Routing is enabled, DHCP
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -470,11 +589,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
|
||||
|
||||
@@ -486,19 +605,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
|
||||
|
||||
|
||||
@@ -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,36 +46,46 @@ 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-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-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
|
||||
@@ -68,8 +94,28 @@ 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
|
||||
|
||||
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.
|
||||
@@ -82,7 +128,7 @@ 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-287803
|
||||
|
||||
@@ -90,47 +136,45 @@ 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-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-285587
|
||||
|
||||
@@ -138,7 +182,11 @@ Bootstrapping the VM-Series firewall on OpenStack with user-data does not functi
|
||||
|
||||
## 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-283467
|
||||
|
||||
@@ -148,13 +196,13 @@ 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.
|
||||
**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.
|
||||
**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
|
||||
|
||||
@@ -170,27 +218,20 @@ When exporting and importing the CSV file, the hash values of pre-shared key (PS
|
||||
|
||||
## 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-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-279746
|
||||
|
||||
@@ -198,23 +239,39 @@ An SSL/TLS Client Hello may not be transmitted out of the firewall if the Client
|
||||
|
||||
## PAN-279621
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 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.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
|
||||
|
||||
@@ -238,25 +295,37 @@ Firewalls in HA configurations were experiencing consistent memory leaks on the
|
||||
|
||||
## PAN-261429
|
||||
|
||||
The command show auth radius-require-msg-authentic might return no output.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
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-260015
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.6 Addressed Issues
|
||||
```
|
||||
|
||||
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.
|
||||
**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).
|
||||
```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
|
||||
|
||||
@@ -266,13 +335,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
|
||||
|
||||
@@ -280,9 +349,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
|
||||
|
||||
@@ -302,7 +371,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
|
||||
|
||||
@@ -312,21 +381,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
|
||||
|
||||
@@ -334,55 +404,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
|
||||
|
||||
@@ -394,11 +437,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
|
||||
|
||||
@@ -410,19 +453,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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -4,43 +4,81 @@ product: PAN-OS
|
||||
version: 11.2.7
|
||||
---
|
||||
|
||||
## PAN-308564
|
||||
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||
|
||||
**Workaround:** Allow fragmenting packets with DF bit set (`debug dataplane set ip4-ignore-df yes`).
|
||||
|
||||
## PAN-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-308418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
When Advanced DNS Security is enabled and experiences unusually high loads, DNS traffic sessions may be impacted, resulting in DNS resolution failures. Traffic logs for these sessions show an end-reason of resources-unavailable.
|
||||
|
||||
Workaround: Disable Advanced DNS Security telemetry (DeviceSetupContent-IDAdvanced DNS Security and uncheck Telemetry Enable).
|
||||
**Workaround:** Disable Advanced DNS Security telemetry (**Device** > **Setup** > **Content-ID** > **Advanced DNS Security** and uncheck **Telemetry Enable**).
|
||||
|
||||
## 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-304576
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.
|
||||
|
||||
Workaround: Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.
|
||||
**Workaround:** Disable HTTP/2 server push using the `set deviceconfig setting http2 server-push no` CLI command.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
```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 and PAN-OS 11.2.7-h8 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-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.
|
||||
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||
|
||||
## PAN-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.7-h8 Addressed Issues.
|
||||
```
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
@@ -48,44 +86,62 @@ A firewall may become unresponsive after an upgrade due to the fsck command scan
|
||||
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-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-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-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
|
||||
@@ -94,8 +150,28 @@ 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
|
||||
|
||||
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.
|
||||
@@ -108,13 +184,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
|
||||
|
||||
@@ -122,41 +198,35 @@ 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-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-285061
|
||||
|
||||
@@ -168,13 +238,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
|
||||
|
||||
@@ -186,26 +260,23 @@ 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-278688
|
||||
@@ -216,15 +287,23 @@ PA-7500, PA-5500, and PA-3500 firewalls only
|
||||
|
||||
When DNS Security packet capture is enabled and a domain name has a length of 62 characters, the DNS Security threat log entry is not generated. On the affected platforms, this condition can also trigger a pan_task crash due to shared memory corruption.
|
||||
|
||||
Workaround: Disable DNS Security packet capture in anti-spyware profiles (ObjectsSecurity ProfilesAnti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.
|
||||
**Workaround:** Disable DNS Security packet capture in anti-spyware profiles (**Objects** > **Security Profiles** > **Anti-Spyware**) and in the **DNS Policies** tab, set **Packet Capture** to **disable**.
|
||||
|
||||
## 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-273158
|
||||
|
||||
@@ -236,15 +315,19 @@ Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-
|
||||
|
||||
## 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
|
||||
|
||||
@@ -254,13 +337,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
|
||||
|
||||
@@ -268,9 +351,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
|
||||
|
||||
@@ -290,7 +373,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
|
||||
|
||||
@@ -300,21 +383,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
|
||||
|
||||
@@ -322,55 +406,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
|
||||
|
||||
@@ -382,11 +439,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
|
||||
|
||||
@@ -398,19 +455,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
|
||||
|
||||
|
||||
@@ -8,69 +8,107 @@ version: 11.2.8
|
||||
|
||||
A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value>
|
||||
|
||||
Workaround: Gracefully restart the affected Wildfire cluster nodes.
|
||||
**Workaround:** Gracefully restart the affected Wildfire cluster nodes.
|
||||
|
||||
## WF500-6259
|
||||
|
||||
When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes.
|
||||
|
||||
Workaround: Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
**Workaround:** Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
|
||||
## WF500-6270
|
||||
|
||||
The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers.
|
||||
|
||||
Workaround: Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
**Workaround:** Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
|
||||
## WF500-6222
|
||||
|
||||
When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues.
|
||||
|
||||
Workaround: Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
**Workaround:** Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
|
||||
## WF500-6176
|
||||
|
||||
When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
|
||||
|
||||
## PAN-308564
|
||||
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||
|
||||
**Workaround:** Allow fragmenting packets with DF bit set (`debug dataplane set ip4-ignore-df yes`).
|
||||
|
||||
## PAN-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-308418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
When Advanced DNS Security is enabled and experiences unusually high loads, DNS traffic sessions may be impacted, resulting in DNS resolution failures. Traffic logs for these sessions show an end-reason of resources-unavailable.
|
||||
|
||||
Workaround: Disable Advanced DNS Security telemetry (DeviceSetupContent-IDAdvanced DNS Security and uncheck Telemetry Enable).
|
||||
**Workaround:** Disable Advanced DNS Security telemetry (**Device** > **Setup** > **Content-ID** > **Advanced DNS Security** and uncheck **Telemetry Enable**).
|
||||
|
||||
## 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-304576
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.
|
||||
|
||||
Workaround: Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.
|
||||
**Workaround:** Disable HTTP/2 server push using the `set deviceconfig setting http2 server-push no` CLI command.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-302927
|
||||
|
||||
After an upgrade, the Push to Devices window fails to populate the list of devices automatically. If you manually select devices by clicking Edit Selections, the OK button becomes unresponsive and fails to save or close the selection window. Additionally, clicking Cancel might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
After an upgrade, the **Push to Devices** window fails to populate the list of devices automatically. If you manually select devices by clicking **Edit Selections**, the **OK** button becomes unresponsive and fails to save or close the selection window. Additionally, clicking **Cancel** might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
|
||||
## 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.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-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.10-h2 Addressed Issues.
|
||||
```
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
@@ -78,28 +116,30 @@ A firewall may become unresponsive after an upgrade due to the fsck command scan
|
||||
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 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-295645
|
||||
@@ -108,7 +148,11 @@ When a WildFire cluster is configured centrally using Panorama, it initiates a s
|
||||
|
||||
## 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
|
||||
```
|
||||
|
||||
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-291716
|
||||
|
||||
@@ -116,13 +160,17 @@ On the Panorama Config Audit page, some commit versions might display incorrect
|
||||
|
||||
## 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-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
|
||||
|
||||
@@ -130,13 +178,8 @@ 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-285061
|
||||
|
||||
@@ -150,7 +193,7 @@ File downloads for content encoded with zstd (Zstandard), such as specific conte
|
||||
|
||||
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-278688
|
||||
|
||||
@@ -160,7 +203,7 @@ PA-7500, PA-5500, and PA-3500 firewalls only
|
||||
|
||||
When DNS Security packet capture is enabled and a domain name has a length of 62 characters, the DNS Security threat log entry is not generated. On the affected platforms, this condition can also trigger a pan_task crash due to shared memory corruption.
|
||||
|
||||
Workaround: Disable DNS Security packet capture in anti-spyware profiles (ObjectsSecurity ProfilesAnti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.
|
||||
**Workaround:** Disable DNS Security packet capture in anti-spyware profiles (**Objects** > **Security Profiles** > **Anti-Spyware**) and in the **DNS Policies** tab, set **Packet Capture** to **disable**.
|
||||
|
||||
## PAN-273158
|
||||
|
||||
@@ -172,15 +215,15 @@ Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-
|
||||
|
||||
## 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).
|
||||
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
|
||||
|
||||
@@ -190,13 +233,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
|
||||
|
||||
@@ -204,9 +247,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
|
||||
|
||||
@@ -226,7 +269,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
|
||||
|
||||
@@ -236,21 +279,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
|
||||
|
||||
@@ -258,55 +302,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
|
||||
|
||||
@@ -318,11 +335,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
|
||||
|
||||
@@ -334,19 +351,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
|
||||
|
||||
|
||||
@@ -8,65 +8,99 @@ version: 11.2.9
|
||||
|
||||
A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value>
|
||||
|
||||
Workaround: Gracefully restart the affected Wildfire cluster nodes.
|
||||
**Workaround:** Gracefully restart the affected Wildfire cluster nodes.
|
||||
|
||||
## WF500-6259
|
||||
|
||||
When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes.
|
||||
|
||||
Workaround: Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
**Workaround:** Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
|
||||
## WF500-6270
|
||||
|
||||
The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers.
|
||||
|
||||
Workaround: Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
**Workaround:** Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
|
||||
## WF500-6222
|
||||
|
||||
When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues.
|
||||
|
||||
Workaround: Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
**Workaround:** Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
|
||||
## WF500-6176
|
||||
|
||||
When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
|
||||
|
||||
## PAN-308564
|
||||
|
||||
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||
|
||||
**Workaround:** Allow fragmenting packets with DF bit set (`debug dataplane set ip4-ignore-df yes`).
|
||||
|
||||
## PAN-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-308418
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
When Advanced DNS Security is enabled and experiences unusually high loads, DNS traffic sessions may be impacted, resulting in DNS resolution failures. Traffic logs for these sessions show an end-reason of resources-unavailable.
|
||||
|
||||
Workaround: Disable Advanced DNS Security telemetry (DeviceSetupContent-IDAdvanced DNS Security and uncheck Telemetry Enable).
|
||||
**Workaround:** Disable Advanced DNS Security telemetry (**Device** > **Setup** > **Content-ID** > **Advanced DNS Security** and uncheck **Telemetry Enable**).
|
||||
|
||||
## 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-304576
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.
|
||||
|
||||
Workaround: Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.
|
||||
**Workaround:** Disable HTTP/2 server push using the `set deviceconfig setting http2 server-push no` CLI command.
|
||||
|
||||
## PAN-303959
|
||||
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||
|
||||
## PAN-302927
|
||||
|
||||
After an upgrade, the Push to Devices window fails to populate the list of devices automatically. If you manually select devices by clicking Edit Selections, the OK button becomes unresponsive and fails to save or close the selection window. Additionally, clicking Cancel might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues
|
||||
```
|
||||
|
||||
After an upgrade, the **Push to Devices** window fails to populate the list of devices automatically. If you manually select devices by clicking **Edit Selections**, the **OK** button becomes unresponsive and fails to save or close the selection window. Additionally, clicking **Cancel** might incorrectly show the device list as empty while retaining the selections in the background.
|
||||
|
||||
## 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-297610
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
```caveat
|
||||
This issue is now resolved. See PAN-OS 11.2.11 Addressed Issues and PAN-OS 11.2.10-h2 Addressed Issues.
|
||||
```
|
||||
|
||||
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||
|
||||
## PAN-297295
|
||||
|
||||
@@ -74,28 +108,30 @@ A firewall may become unresponsive after an upgrade due to the fsck command scan
|
||||
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-295645
|
||||
@@ -104,17 +140,25 @@ When a WildFire cluster is configured centrally using Panorama, it initiates a s
|
||||
|
||||
## 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
|
||||
```
|
||||
|
||||
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-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-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-285061
|
||||
|
||||
@@ -128,7 +172,7 @@ File downloads for content encoded with zstd (Zstandard), such as specific conte
|
||||
|
||||
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-278688
|
||||
|
||||
@@ -138,7 +182,7 @@ PA-7500, PA-5500, and PA-3500 firewalls only
|
||||
|
||||
When DNS Security packet capture is enabled and a domain name has a length of 62 characters, the DNS Security threat log entry is not generated. On the affected platforms, this condition can also trigger a pan_task crash due to shared memory corruption.
|
||||
|
||||
Workaround: Disable DNS Security packet capture in anti-spyware profiles (ObjectsSecurity ProfilesAnti-Spyware) and in the DNS Policies tab, set Packet Capture to disable.
|
||||
**Workaround:** Disable DNS Security packet capture in anti-spyware profiles (**Objects** > **Security Profiles** > **Anti-Spyware**) and in the **DNS Policies** tab, set **Packet Capture** to **disable**.
|
||||
|
||||
## PAN-273158
|
||||
|
||||
@@ -150,15 +194,15 @@ Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-
|
||||
|
||||
## 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).
|
||||
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
|
||||
|
||||
@@ -168,13 +212,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
|
||||
|
||||
@@ -182,9 +226,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
|
||||
|
||||
@@ -204,7 +248,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
|
||||
|
||||
@@ -214,21 +258,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
|
||||
|
||||
@@ -236,55 +281,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
|
||||
|
||||
@@ -296,11 +314,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
|
||||
|
||||
@@ -312,19 +330,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