>
    PAN-OS 10.2.6 Known Issues
    Focus
    Download PDF
    Focus
    1. Home
    2. PAN-OS
    3. PAN-OS 10.2.6 Known and Addressed Issues
    4. PAN-OS 10.2.6 Known Issues
    Download PDF

    PAN-OS 10.2.6 Known Issues

    Table of Contents

    PAN-OS 10.2.6 Known Issues

    PAN-OSĀ® 10.2.6 known issues
    The following list includes only outstanding known issues specific to PAN-OSĀ® 10.2.6. 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
    WF500-5854
    The WildFire analysis report on the firewall log viewer (MonitoringWildFire Submissions) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
    Workaround: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the Detailed Log View.
    WF500-5843
    In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
    WF500-5840
    The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
    WF500-5823
    The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
    WF500-5781
    The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
    WF500-5754
    In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
    Workaround: Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
    WF500-5632
    The number of registered WildFire appliances reported in Panorama (PanoramaManaged WildFire AppliancesFirewalls ConnectedView) does not accurately reflect the current status of connected WildFire appliances.
    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-259769
    GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
    PAN-250062
    Device telemetry might fail at configured intervals due to bundle generation issues.
    PAN-244648
    (PA-5200 Series firewalls only) After a factory reset, the firewall may get stuck in maintenance mode and be unable to load the boot image. The firewall fails to enable FIPS-CC mode during this time.
    Workaround: The following workaround allows the firewall to boot in normal mode but does not apply to FIPS-CC mode. Attempting to enable FIPS-CC mode after using this workaround will cause the firewall to reboot and re-enter maintenace mode.
    1. Enter maintenance mode.
    2. Select Disk ImageAdvanced Options.
    3. Select Bootstrap with the options panos-10.2.8, maint, and maint.
    4. Select Bootstrap with the options panos-10.2.8, sysroot0, and panos.
    5. Select Bootstrap with the option sysroot0.
    6. Select Reboot.
    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.
    1. Log in to the Panorama web interface on the active HA peer.
    2. Select Commit and Commit to Panorama the SD-WAN configuration changes on the active HA peer.
      On the passive HA peer, select PanoramaManaged DevicesSummary and observe that the managed devices are now out-of-sync.
    3. Log in to the primary HA peer Panorama CLI and trigger a manual synchronization between the active and secondary HA peers.
      request high-availability sync-to-remote running-config
    4. Log back in to the active HA peer Panorama web interface and select CommitPush to Devices and Push.
    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-234929
    This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
    The tabs in the ACC, such as Network Activity, Threat Activity, and Blocked Activity, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
    PAN-228515
    The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (MonitorLogs) and the Log Collector health status (PanoramaManaged CollectorsStatus) to display as degraded.
    PAN-228273
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the show log-collector-es-cluster health command displays the status is red. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
    PAN-227344
    On the Panorama management server, PDF Summary Reports (MonitorPDF ReportsManage PDF Summary) display no data and are blank when predefined reports are included in the summary report.
    PAN-225337
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
    1. Create a Shared and vsys-specific device group configuration object with an indentical name. For example, a Shared address object called SharedAO1 and a vsys-specific address object also called SharedAO1.
    2. Reference the Shared object in another Shared configuration. For example, reference the Shared address object (SharedAO1) in a Shared address group called SharedAG1.
    3. Use the Shared configuration object with the reference in a vsys-specific configuration. For example, reference the Shared address group (SharedAG1) in a vsys-specific policy rule.
    Workaround: Select PanoramaSetupManagement and edit the Panorama Settings to enable one of the following:
    • Shared Unused Address and Service Objects with Devicesā€”This options pushes all Shared objects, along with device group specific objects, to managed firewalls.
      This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
    • Objects defined in ancestors will take higher precedenceā€”This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the Shared objects take precedence over the vsys-specific object.
      This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the Shared SharedAO1 object was 10.1.1.1 and the device group specific SharedAO1 was 10.2.2.2, the 10.1.1.1 IP address takes precedence.
    Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the Shared objects in your configuration.
    PAN-223365
    The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (PanoramaManaged Collector is degraded.
    Workaround: Log in to the Log Collector CLI and restart ElasticSearch.
    admindebug elasticsearch es-restart all
    PAN-227368
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    The GlobalProtect app cannot connect to a portal or gateway and GlobalProtect Clientless VPN users cannot access applications if authentication takes longer than 20 seconds.
    Workaround: Increase the TCP handshake timeout to the maximum value of 60 seconds.
    PAN-226768
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in Connecting stage after authentication and the GlobalProtect log displays the error message, User is not in allow list. This happens when the app is restarted or when the app tries to reconnect after disconnection.
    PAN-223677
    (PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls) By enabling Lockless QoS feature, a slight degradation in App-ID and Threat performance is expected.
    PAN-223488
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    		Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
    PAN-223457
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
    PAN-222586
    On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (DeviceLog Settings) are not displayed and cannot be configured.
    PAN-222418
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
    PAN-222253
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    On the Panorama management server, policy rulebase reordering when you View Rulebase by Groups (Policy<policy-rulebase>) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
    PAN-221775
    A Malformed Request error is displayed when you Test Connection for an email server profile (DeviceServer ProfilesEmail) using SMTP over TLS and the Password includes an ampersand (&).
    PAN-221857
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: Username from SAML SSO response is different from the input..
    PAN-221126
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    Email server profiles (DeviceServer ProfilesEmail and PanoramaServer ProfilesEmail) to forward logs as email notifications are not forwarded in a readable format.
    Workaround: Use a Custom Log Format to forward logs as email notifications in a readable format.
    PAN-221015
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    On M-600 appliances in Panorama or Log Collector mode, the es-1 and es-2 ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector ES health status (PanoramaManaged CollectorsHealth Status) to be degraded.
    Workaround: Log in to the Panorama or Log Collector CLI experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
    admin>debug elasticsearch es-restart optional all
    PAN-220180
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    Configured botnet reports (MonitorBotnet) are not generated.
    PAN-219644
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    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-218521
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
    PAN-217307
    This issue is now resolved. See PAN-OS 10.2.11 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-215082
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    M-300 and M-700 appliances may generate erroneous system logs (MonitorLogsSystem) to alert that the M-Series appliance memory usage limits are reached.
    PAN-213746
    On the Panorama management server, the Hostkey displayed as undefined undefined if you override an SSH Service Profile (DeviceCertificate ManagementSSH Service Profile) Hostkey configured in a Template from the Template Stack.
    PAN-213119
    PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (MonitorBlock IP):
    show -> dis-block-table is unexpected
    PAN-212889
    On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (MonitorApp ScopeThreat Monitor) and ACC. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
    PAN-212533
    Modifying the Administrator Type for an existing administrator (DeviceAdministrators or PanoramaAdministrators) from Superuser to a Role-Based custom admin, or vice versa, does not modify the access privileges of the administrator.
    PAN-211531
    		On the Panorama management server, admins can still perform a selective push to managed firewalls when Push All Changes and Push for Other Admins are disabled in the admin role profile (PanoramaAdmin Roles).
    PAN-209288
    Certificates are not successfully generated using SCEP (DeviceCertificate ManagementSCEP).
    PAN-208622
    A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (ObjectsDLPData Filtering Profiles with the Action set to Block to a Security policy rule (PoliciesSecurity).
    PAN-204689
    Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
    • Allow user to disconnect GlobalProtect AppAllow with Passcode
    • Allow user to Disable GlobalProtect AppAllow with Passcode
    • Allow User to Uninstall GlobalProtect AppAllow with Password
    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-196504
    		License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
    PAN-196146
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
    PAN-194996
    When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
    Workaround: Retry the operation.
    PAN-194519
    (PA-5450 firewall only) Trying to configure a custom payload format under DeviceServer ProfilesHTTP yields a Javascript error.
    PAN-194515
    (PA-5450 firewall only) The Panorama web interface does not display any predefined template stack variables in the dropdown menu under DeviceSetupLog InterfaceIP Address.
    Workaround: Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
    PAN-194424
    (PA-5450 firewall only) Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
    Workaround: Restart the log receiver service by running the following CLI command: 
    debug software restart process log-receiver
    PAN-194202
    (PA-5450 firewall only) If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
    PAN-193004
    This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
    The Panorama management server fails to delete old IP Tag data. This causes the /opt/pancfg partition to reach maximum capacity which impacts Panorama performance.
    PAN-190727
    (PA-5450 firewall only) Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administratorā€™s Guide.
    PAN-189111
    After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
    PAN-189076
    On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
    Workaround: Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
    PAN-188358
    After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
    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-187643
    If you enable SCTP security using a Panorama template when SCTP INIT Flood Protection is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the SCTP INIT option is not available in the Zone Protection profile.
    Workaround: Log out of the firewall and log in again to make the SCIT INIT option available on the web interface.
    PAN-187612
    On the Panorama management server, not all data profiles (ObjectsDLP Data Filtering Profiles) are displayed after you:
    • Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
    • Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
    Workaround: Log in to the Panorama CLI and reset the DLP plugin.
    admin > request plugins dlp reset
    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-187370
    On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
    Workaround: Do not use a logical router instance with no interfaces bound to it.
    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-186282
    On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
    Workaround: Reboot the Panorama HA pair.
    PAN-185286
    This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
    (PA-5400 Series firewalls only) On the Panorama management server, the device health resources (PanoramaManaged DevicesHealth) do not populate.
    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-181823
    On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
    PAN-180661
    On the Panorama management server, pushing an unsupported Minimum Password Complexity (DeviceSetupManagement) to a managed firewall erroneously displays commit time out as the reason the commit failed.
    PAN-180104
    When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
    Workaround: Reboot the worker nodes before upgrading to PAN-OS 10.2.
    PAN-178194
    A user interface issue in PAN-OS renders the contents of the Inline ML tab in the URL Filtering Profile inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a License required for URL filtering to function is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
    Workaround: Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
    • Define URL exceptions for specific web sitesā€”
      admin# set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
    • Configuration settings for each inline ML modelā€”
      admin# set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
    PAN-177455
    PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
    PAN-175915
    When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
    PAN-174982
    In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
    PAN-172274
    When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall ā€” this is a display anomaly, not a licensing issue, and does not affect access to the services.
    Workaround: Issue the following command to retrieve and update the licenses: license request fetch.
    PAN-171938
    No results are displayed when you Show Application Filter for a Security policy rule (PoliciesSecurityApplicationValueShow Application Filter).
    PAN-164885
    This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
    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.

    © 2024 Palo Alto Networks, Inc. All rights reserved.