PAN-OS 11.1.0 Known Issues
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
-
- Cloud Management of NGFWs
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1 & Later
- PAN-OS 9.1 (EoL)
-
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1 & Later
-
-
- Cloud Management and AIOps for NGFW
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1
- PAN-OS 11.2
- PAN-OS 8.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 9.1 (EoL)
PAN-OS 11.1.0 Known Issues
What is the list of known issues for PAN-OS 11.1.0?
The following list includes only outstanding known issues specific to PAN-OS® 11.1.0.
This list includes issues specific to Panorama™, GlobalProtect™, VM-Series plugins, and
WildFire®, as well as known issues that apply more generally or that are not identified
by an issue ID.
Issue ID | Description |
---|---|
PAN-262556
|
The ElasticSearch cluster health status might continue to remain
yellow for an extended period after upgrading to PAN-OS 11.1.0.
|
PAN-262287
|
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.
|
PAN-257615
This issue is now resolved. See PAN-OS 11.1.2-h9 Addressed Issues.
|
The Panorama web interface intermittently displays logs or fails to
display logs completely.
|
PAN-259769
This issue is now resolved. See PAN-OS 11.1.5 Addressed Issues.
|
GlobalProtect portal is not accessible via a web browser and the app
displays the error
ERR_EMPTY_RESPONSE.
|
PAN-250062
This issue is now resolved. See PAN-OS 11.1.4-h4 Addressed Issues.
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
PAN-243951
|
On the Panorama management sever in an active/passive High
Availability (HA) configuration, managed devices (PanoramaManaged DevicesSummary) display as out-of-sync
on the passive HA peer when configuration changes are made to the
SD-WAN (PanoramaSD-WAN) configuration on the active HA peer.
Workaround: Manually synchronize the Panorama HA peers.
|
PAN-242910
|
On the Panorama management server, Panorama administrators (PanoramaAdministrators) that are assigned a custom Panorama admin role (PanoramaAdmin Roles) with Push All Changes enabled
are unable to push configuration changes to managed firewalls when
Managed Devices and Push For
Other Admins are disabled.
|
PAN-242561
|
GlobalProtect tunnel might disconnect shortly after being established
when SSL is used as a transport protocol.
Workaround: Disable Internet Protocol version 6 (TCP/IPv6) on
the PANGP Virtual Network Adapter.
|
PAN-241041
|
On the Panorama management server exporting template or template
stack variables (PanoramaTemplates) in CSV format results in an empty CSV file.
|
PAN-234408
|
Enterprise DLP cannot detect and block non-file based traffic for
ChatGPT from traffic forwarded to the DLP cloud service from an
NGFW.
|
PAN-234015
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
PAN-228491
|
On the AWS environment, the session failover takes up to 4
minutes.
|
PAN-225337
|
On the Panorama management server, the configuration push to a
multi-vsys firewall fails if you:
Workaround: Select PanoramaSetupManagement and edit the Panorama Settings to enable one of the
following:
Alternatively, you can remove the duplicate address objects from the
device group configuration to allow only the
Shared objects in your configuration.
|
PAN-224502
|
The autocommit time of the VM-Series firewall running PAN-OS 11.1.0
might take longer than expected.
|
PAN-220577
|
With firewalls in AWS environment that are licensed with VM capacity
and secure web proxy licenses, it is observed that the enablement of
the web-proxy config fails.
Workaround: Reboot the firewall after the web proxy license is
applied.
|
PAN-220180
|
Configured botnet reports (MonitorBotnet) are not generated.
|
PAN-219644
|
Firewalls forwarding logs to a syslog server over TLS (ObjectsLog Forwarding) use the default Palo Alto Networks certificate
instead of the custom certificate configured on the firewall.
|
PAN-217307
This issue is now resolved. See PAN-OS 11.1.3 Addressed Issues.
|
The following Security policy rule (PoliciesSecurity) filters return no results:
log-start eq no
log-end eq no
log-end eq yes
|
PAN-208794
|
In firewalls with transparent proxy, it is observed that a reboot is
necessary to view the transit sessions.
Workaround: Edit the virtual router settings with any minor
change and commit again. Any changes to the network/interfaces or
network/virtual routers usually fixes this issue.
Alternatively, you may try rebooting the firewall. This issue
disappears following reboot after the
swg is setup and configured.
|
PAN-207733
|
When a DHCPv6 client is configured on HA Active/Passive firewalls, if
the DHCPv6 server goes down, after the lease time expires, the
DHCPv6 client should enter SOLICIT state on both the Active and
Passive firewalls. Instead, the client is stuck in BOUND state with
an IPv6 address having lease time 0 on the Passive firewall.
|
PAN-207611
|
When a DHCPv6 client is configured on HA Active/Passive firewalls,
the Passive firewall sometimes crashes.
|
PAN-207442
|
For M-700 appliances in an active/passive high availability (PanoramaHigh Availability) configuration, the
active-primary HA peer
configuration sync to the
secondary-passive HA peer may fail.
When the config sync fails, the job Results is
Successful
(Tasks), however the sync status on the
Dashboard displays as Out
of Sync for both HA peers.
Workaround: Perform a local commit on the
active-primary HA peer and then
synchronize the HA configuration.
|
PAN-207040
|
If you disable Advanced Routing, remove logical routers, and
downgrade from PAN-OS 11.0.0 to a PAN-OS 10.2.x or 10.1.x release,
subsequent commits fail and SD-WAN devices on Panorama have no
Virtual Router name.
|
PAN-206913
|
When a DHCPv6 client is configured on HA Active/Passive firewalls,
releasing the IPv6 address from the client (using Release in the UI
or using the request dhcp client ipv6 release
all CLI command) releases the IPv6 address from
the Active firewall, but not the Passive firewall.
|
PAN-206909
|
The Dedicated Log Collector is unable to reconnect to the Panorama
management server if the configd
process crashes. This results in the Dedicated Log Collector losing
connectivity to Panorama despite the managed collector connection
Status (PanoramaManaged Collector) displaying connected
and the managed colletor Health status
displaying as healthy.
This results in the local Panorama config and system logs not being
forwarded to the Dedicated Log Collector. Firewall log forwarding to
the disconnected Dedicated Log Collector is not impacted.
Workaround: Restart the mgmtsrvr
process on the Dedicated Log Collector.
|
PAN-204689
|
Upon upgrade to PAN-OS 11.0.1, the following GlobalProtect settings
do not work:
|
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
|
(PA-1400 Series firewalls only) In NetworkInterfaceEthernet, the power over Ethernet (PoE) ports do not display a
Tag value.
|
PAN-196758
|
On the Panorama management server, pushing a configuration change to
firewalls leveraging SD-WAN erroneously show the auto-provisioned
BGP configurations for SD-WAN as being edited or deleted despite no
edits or deletions being made when you Preview
Changes (CommitPush to DevicesEdit Selections or CommitCommit and PushEdit Selections).
|
PAN-195968
|
(PA-1400 Series firewalls only) When using the CLI to
configure power over Ethernet (PoE) on a non-PoE port, the CLI
prints an error depending on whether an interface type was selected
on the non-PoE port or not. If an interface type, such as tap, Layer
2, or virtual wire, was selected before PoE was configured, the
error message will not include the interface name (eg. ethernet1/4).
If an interface type was not selected before PoE was configured, the
error message will include the interface name.
|
PAN-194978
|
(PA-1400 Series firewalls only) In NetworkInterfaceEthernet, hovering the mouse over a power over Ethernet (PoE)
Link State icon does not display link
speed and link duplex details.
|
PAN-187685
|
On the Panorama management server, the Template Status displays no
synchronization status (PanoramaManaged DevicesSummary) after a bootstrapped firewall is successfully added
to Panorama.
Workaround: After the bootstrapped firewall is successfully
added to Panorama, log in to the Panorama web
interface and select CommitPush to Devices.
|
PAN-187407
|
The configured Advanced Threat Prevention inline cloud analysis
action for a given model might not be honored under the following
condition: If the firewall is set to Hold client request
for category lookup and the action set to
Reset-Both and the URL cache has been
cleared, the first request for inline cloud analysis will be
bypassed.
|
PAN-186283
|
Templates appear out-of-sync on Panorama after successfully deploying
the CFT stack using the Panorama plugin for AWS.
Workaround: Use CommitPush to Devices to synchronize the templates.
|
PAN-184708
|
Scheduled report emails (MonitorPDF ReportsEmail Scheduler) are not emailed if:
Workaround: To receive a scheduled report email for all other
PDF report types:
|
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.
|
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.
|