PAN-OS 11.1.7 Addressed Issues
Focus
Focus

PAN-OS 11.1.7 Addressed Issues

Table of Contents

PAN-OS 11.1.7 Addressed Issues

PAN-OS® 11.1.7 addressed issues.
PAN-OS 11.1.7 is limited to PA-7500 firewalls only in our Customer Support Portal.
Issue ID
Description
PAN-273245
(Firewalls in HA configurations only) Fixed an issue where upgrading an HA firewall pair from PAN-OS 10.2.11-h1 to PAN-OS 11.1.5 caused the firewalls to enter a nonfunctional loop due to repeated HA path monitoring failures.
PAN-272849
Fixed an issue where log forwarding to a UDP syslog server stopped when an unreachable TCP syslog server was configured and applied.
PAN-272538
Fixed an issue where the configd process stopped responding during a commit-all validation when there were uncommitted changes and share-unused-objects-with-devices was set to off.
PAN-272006
Fixed an issue where the firewall did not trigger a kernel core dump as a large core when the CPLD (Complex Programmable Logic Device) sent a Non-Maskable Interrupt (NMI) to the CPU.
PAN-271926
Fixed an issue where TLS 1.3 decryption failed with a bad record MAC error when the firewall was configured to decrypt and inspect TLS traffic.
PAN-271912
Fixed an issue on Panorama where the configd process stopped responding when filtering in the configuration audit window after upgrading to PAN-OS 11.1.3.
PAN-271314
Fixed an issue where pushing changes to a prefix list used for BGP from Panorama affected OSPF routes.
PAN-270607
(Firewalls in active/passive HA configurations only) Fixed an issue where OSPF failed to establish after a failover from the active firewall to the passive firewall.
PAN-270471
(Firewalls in active/active configurations only) Fixed an issue where the firewall did not detect configuration changes when only the interface of an IKE gateway was changed, which caused IPSec tunnels to not come up after migrating the IKE gateway IP address from a subinterface to a physical interface.
PAN-269956
Fixed an issue where the all_pktproc process stopped responding, which caused internal path monitor failures.
PAN-269731
Fixed an issue where Panorama did not display logs from firewalls after upgrading to PAN-OS 10.2.11 on devices due to Elasticsearch (ES) getting restarted continuously.
PAN-269337
Fixed an issue where the cluster compatibility timer was limited to 300 to 3600 seconds.
PAN-268465
Fixed an issue with firewalls in active/passive HA configurations where the total user count in the registered users was different between the active and passive firewall.
PAN-267781
Fixed an issue where Panorama did not display the Source Dynamic Address Group.
PAN-267097
Fixed an issue where the replay database size increased significantly due to local and special configurations not being purged after commits.
PAN-265219
(VM-Series firewalls only) Fixed an issue where GRE traffic did not work properly.
PAN-265179
Fixed an issue where a kernel race condition caused the firewall to reboot with a kernel panic.
PAN-262946
Fixed an issue on the firewall where logging in via the CLI or web interface did not work due to increased memory usage.
PAN-262043
Fixed an issue where Voice over WiFi (VoWiFi) stopped working after switching from a PA-5200 Series firewall to a PA-7500 Series firewall in NGFW clustering mode with NATT IPSec Passthrough and NAT policy enabled. To use this fix, enter the CLI command show tunnel-acceleration, disable tunnel acceleration, and reboot the PA-7500 Series firewall.
PAN-260235
Fixed an issue where the firewall sent Threat logs and URL logs to an external syslog server without Security profile settings when Enhanced Application Logging was enabled.
PAN-259078
Fixed an issue where WildFire Analysis reports were not generated and the following error message was displayed: Error 500: Internal Server Error.
PAN-258149
Fixed an issue where the firewall dropped the SYN-ACK when using the TCP Fast Open option.
PAN-246699
Fixed an issue on Panorama where Rule Usage and Apps Seen under Security policy rules stopped incrementing.
PAN-212889
Fixed an issue on Panorama where different threat names were used when querying a threat under Threat Monitor (Monitor > App Scope) and the ACC. This resulted in the ACC displaying no data after clicking a threat name in Threat Monitor and filtering it in the global filters.