When you upgrade a PA-450R, PA-450R-5G, PA-410R, or PA-410R-5G firewall to PAN-OS 12.2.2 from an earlier release with Fail-to-Wire enabled, subsequent manual commits fail with the following validation error: network -> interface -> fail-open is invalid. This occurs because PAN-OS 12.2.2 introduced a configuration schema change for the Fail-to-Wire feature that is not automatically migrated during upgrade. Fail-to-Wire also does not function correctly after the upgrade.

Workaround:Remove and re-add the Fail-to-Wire configuration.

On 5G firewalls, Zero Touch Provisioning (ZTP) over cellular does not complete when the cellular carrier MTU is 1428. During ZTP, the firewall does not correctly account for cellular tunnel header overhead when negotiating the TCP maximum segment size (MSS). The firewall advertises an MSS value that is too large for the 1428 MTU cellular link, causing the certificate server's response packets to exceed the link MTU. The certificate fetch does not complete, and the firewall does not finish provisioning.

This issue occurs when using a cellular connection with a carrier-negotiated MTU of 1428, which is the standard MTU for cellular wireless. ZTP process will succeed when carrier provided Network MTU is greater than or equal to 1500.

On HA pairs running PAN-OS 12.2.2, the useridd process may exhaust its ID manager (type 17) when the passive firewall accumulates more than 1,000,000 user entries. When this occurs, useridd consumes 100% CPU and becomes unresponsive, causing commits to fail with the error Management server failed to send phase 1 to client useridd or to stall at 0%.

On firewalls with cellular interfaces configured with parent and sub-interfaces, APN authentication fails on sub-interfaces when the PDP type is set to both (IPv4 and IPv6). Data sessions on the parent interface establish successfully for both IPv4 and IPv6, but sub-interfaces fail to bring up their data sessions when using PAP or CHAP authentication with PDP type both.

Workaround: Set the PDP type to IPv4 only on sub-interfaces.

(PA-5450, PA-5500, and PA-7500 firewalls with PAN-OS Shield enabled) When connecting to GlobalProtect Portal or Gateway, users receive a `Portal unreachable` error. GlobalProtect connections are frequently unsuccessful, though they may connect successfully after multiple attempts.

Workaround: Change the session distribution policy to Round-robin.

On PA-54R-POE (BH/Eagle) firewalls, the PAN-S-SFP-100BASE-FX transceiver on fiber interfaces does not link up when the interface link speed is explicitly set to 100 Mbps. The interface links up correctly when the link speed is set to auto.

Workaround: Set the interface link speed to auto.

Running the CLI command debug dataplane packet-path-test counter on PAN-OS 12.2.2 returns a server error instead of counter output.

Within GCP NSI environments, egress traffic logs fail to accurately reflect the designated NAT IP addresses.

If Azure hotplug events occur, the firewall may experience a crash and data interfaces may transition to an unknown state, leading to traffic disruption.

In PA-VM deployed on GCP instances, gVNIC interfaces appear inactive after enabling jumbo frames.

When firewalls are configured in a cluster operating in default mode, IP-Tag, User-Tag, and IP-Port mappings registered on the leader node do not synchronize to the follower node. On the follower node, commands such as `show object registered-ip all` and `show object registered-user all` display no registered entries for these data types, even though they are present on the leader. This prevents Dynamic Address Group (DAG) and Dynamic User Group (DUG) based security policies, which rely on these mappings, from functioning correctly on the follower node. As a result, traffic routed through the follower node does not match these policies, leading to an inconsistent security posture across the cluster.

Workaround: Configure the firewall cluster to operate in ICD mode. This enables the correct synchronization of IP-Tag, User-Tag, and IP-Port mappings between the leader and follower nodes.

On PA-54R-POE (BH) firewalls, SCP export and import of cellular firmware files fail from the CLI. Running request cellular firmware scp-export or request cellular firmware scp-import returns a server error.

When scheduling cellular firmware downloads on Panorama (Device Deployment > Cellular Firmware > Schedule), the Files and Devices fields are not populated in the UI for PA-54R-POE-5G (BH/Eagle) devices. As a result, scheduled Download Only and Download and Install operations for cellular firmware cannot be configured through Panorama.

Within GCP NSI environments, the Prisma® AIRS license activates geneve parsing as a default setting, permitting intraVPC traffic flow regardless of NSI status. You cannot disable this feature through CLI.

When you configure ML7-CUID in a multi-vsys environment on PAN-OS 12.2.2, data upload only supports the hub vsys configuration. When a publisher is configured on a non-hub vsys, data from that vsys is not uploaded to the cloud. All vsys must share the same segment configuration for data upload to function correctly in this release.

Workaround: Configure the publisher on the hub vsys and ensure all vsys use the same segment configuration.

(PA-5450 Firewalls only) Basic authentication for web proxy is not supported in 12.2.2.

When a Hyperscale Security Fabric (HSF) cluster uses an offline license, the system allows the removal of configuration and uninstallation of the Security Fabric License (SFL) plugin. If the SFL plugin is uninstalled under these conditions, subsequent undeploy operations do not complete successfully.

Workaround: To allow the undeploy operation to complete, reinstall the Security Fabric License (SFL) plugin.

After downgrading a PA-520 firewall from PAN-OS 12.2.0 to 12.1.5 or later 12.1.x releases, auto-commit repeatedly fails after the downgrade completes, leaving the firewall unable to apply its configuration automatically.

The `useridd` process restarts when you attempt to dump the Host Information Profile (HIP) database using the `debug user-id dump hip-profile-database` command. This occurs while the firewall is actively processing HIP reports, such as logouts or updates. The command initially hangs and times out before the `useridd` process restarts.

(PA-5500 Series firewalls in cluster configurations only) When a firewall node is removed from a PA-5500 Series cluster, after the cluster commit and reboot, the node starts in standalone mode with a default virtual wire (vwire) configuration loaded. This default configuration is missing zone assignments for ports eth1/1 and eth1/2, which causes commit operations to fail. Even if zones are manually assigned to these ports, subsequent commit attempts fail with a "no UUId for rule1" error.

Workaround: Manually assign zone configurations to ports eth1/1 (for example, untrust) and eth1/2 (for example, trust), then open and close security policy rule1 without making changes, and commit. Alternatively, delete the default rule and the default virtual wire Ethernet interfaces, then commit.

(Firewalls in active/passive high availability (HA) configurations only) When you synchronize the running configuration with an HA peer, particularly during script runs involving different topology builds, the synchronization process fails with an error indicating that the running configuration could not be synchronized with the HA peer.

If a node is stuck with a "session clearing fault," reboot the node to restore it to an online state after all other fault conditions are removed.

If a node is stuck with a "session clearing fault," reboot the node to restore it to an online state after all other fault conditions are removed.

Subscriber Identity and Equipment Identity values are missing from URL filtering and Data Filtering logs for GTP mobility traffic.

On firewalls with 5G cellular interfaces, the default auto MTU value of 1428 bytes causes IP fragmentation errors and out-of-order packets, resulting in degraded throughput performance on cellular connections.

Workaround: Manually set the cellular interface MTU to 1500 bytes instead of using the auto MTU default.

Panorama cannot display Threat log entries (Monitor > Logs > Threat) when the managed log collector is running a lower PAN-OS release than Panorama.

Workaround: Upgrade the log collectors to the same version as Panorama.

(NGFW Cluster) In an NGFW cluster, pings to the HSCI-B link may fail even when the link indicates it is up. If the HSCI-A link is brought down or unplugged, the cluster node transitions to a failed state, avoiding split brain because both HSCI links are down.

Workaround: Reboot the cluster node to resolve the HSCI-B ping issue.

When a client sends a Client Hello with TLS 1.3 or TLS 1.2 using only the p-192 elliptic curve and some non-perfect forward secrecy (PFS) ciphers, the firewall discards the Client Hello. The firewall should allow the connection to proceed using TLS 1.2, maintaining backward compatibility with previous releases.

When configuring a PIM6 neighbor filter, you must include both the primary and secondary IPv6 addresses of each neighbor in the prefix list. Filtering on the primary address alone is not sufficient because PIM6 Hello messages (Option 5) advertise both addresses to peers. A filter that allows only the primary address will prevent neighbor adjacency from forming.

After you change the system mode on an M-700 appliance from Panorama mode to PAN-DB private cloud mode, the snmpd process fails to work.

When a Panorama appliance running PAN-OS 12.1.2 or later manages firewalls running earlier PAN-OS versions, and an NTP server configuration template includes SHA256 or SHA512 as the authentication mechanism, pushing the template to firewalls running PAN-OS versions earlier than 12.1.2 causes the commit operation to fail.

Workaround: Create two separate templates: one for firewalls running PAN-OS 12.1.2 or later (which can include SHA256/SHA512 authentication) and another for firewalls running earlier PAN-OS versions (which should use SHA1, MD5, or Autokey). Push the appropriate template to the corresponding devices from Panorama.

In any 15-second interval, if connectivity (CI or management) on a GW-Node (not P-Node) changes more than once, with each change occurring on a different node and affecting a different link, the cluster loses its leader, all routing protocols fail, and traffic is blackholed if route changes occur in the network.

Workaround: Reboot nodes that are in a FAILED state or suspend and unsuspend any online GW-Node (not P-Node).

When high-speed logging is enabled on a PA-5560 firewall, the expected warning message does not appear on the web interface. This prevents you from being notified that logs can only be viewed from Panorama.

PAN-OS 12.1.2 and later 12.1 releases support a load-balanced DNS configuration for an address object. If two address objects share the same FQDN but one has load-balanced DNS enabled and the other has it disabled, the policy match for removed IP addresses does not work as expected.

Workaround: Enable or disable load-balanced DNS consistently for any FQDN used with multiple address objects.

In PAN-OS 12.1.2 and later and PAN-OS 12.2.2 and later releases, PAN-OS can obtain resolved IP addresses from a load-balanced DNS server and use them in a policy match. However, this functionality does not work as intended when the DNS cache reuse flag is enabled. When the DNS cache reuse flag is enabled, the DNS resolution works as if the load-balanced DNS flag (for an address object) is disabled.

When an existing template overrides the SD-WAN configuration followed by a commit and push from Panorama to the firewall, the following error occurs: BGP is invalid. AS number does not fit in 2 byte AS format. This issue occurs because different AS formats are present on Panorama and the firewall (the firewall configuration is generated by the SD-WAN plugin). In hub-and-spoke topology, both the hub and branch firewall must have the same AS format. In full mesh topology, all firewalls must have the same AS format.

In Software Firewall Licensed HSF environments, serial numbers linked to stale entries can be manually released for reuse. This procedure allows for the recovery of Software Firewall License credits when virtual instances are deleted without being formally decommissioned. For optimal resource management, it is recommended to utilize Orchestration plugin workflows for VM operations rather than manual intervention.