Revise PAN-OS 12.1 issues
This commit is contained in:
@@ -16,10 +16,18 @@ Fixed an issue where a newly bootstrapped firewall required a management server
|
||||
|
||||
Fixed an issue on PAN-OS 12.1 releases where intermittent traffic drops occurred over IPSec VPN tunnels to third-party firewalls during the IPSec rekey due to the firewall failing to inform the peer to delete the old SA after moving to the new one.
|
||||
|
||||
## PAN-313216
|
||||
|
||||
Fixed an issue where firewalls with Prisma Access incorrectly displayed some traffic as unsanctioned in traffic logs for cloud applications that were tagged as sanctioned.
|
||||
|
||||
## PAN-311512
|
||||
|
||||
Fixed an issue where HIP (Host Information Profile) reports were blocked on GlobalProtect when **Authentication Cookie Usage Restrictions** was enabled and the Prisma Access Agent protocol was in use. This occurred because the system failed to correctly process HIP messages that were relayed via IPSec tunnels with a Virtual IP as the source, leading to their rejection.
|
||||
|
||||
## PAN-311412
|
||||
|
||||
Fixed an issue where the show advanced-routing resource CLI command failed to execute successfully when invoked through the XML API and returned an error message.
|
||||
|
||||
## PAN-311261
|
||||
|
||||
Fixed an issue where the firewall generated duplicate URL Filtering logs due to an error condition when the new XFF feature was enabled.
|
||||
@@ -40,6 +48,14 @@ Fixed an issue where IPv6 Routed HA did not function correctly when the HA1 (con
|
||||
|
||||
Fixed an issue where software packet buffers were completely utilized when performing a Data Loss Prevention longevity test.
|
||||
|
||||
## PAN-308507
|
||||
|
||||
```caveat
|
||||
Panorama managed firewalls only
|
||||
```
|
||||
|
||||
Fixed an issue where the firewall intermittently failed to maintain active log forwarding streams to Strata Logging Service (SLS) even when duplicate logging and enhanced application logging were enabled.
|
||||
|
||||
## PAN-308418
|
||||
|
||||
Fixed an issue where, when Advanced DNS Security was enabled and experienced unusually high loads, DNS resolution failures occurred with the error **resources-unavailable**.
|
||||
|
||||
Reference in New Issue
Block a user