Add 8.1 addressed issues
This commit is contained in:
@@ -4,6 +4,34 @@ product: PAN-OS
|
||||
version: 11.2.10
|
||||
---
|
||||
|
||||
## WF500-6271
|
||||
|
||||
A WildFire cluster node that has been configured with an IPv6 management port might not display the signature status when using the following CLI: show wildfire global signature-status sha256 equal <SHA_256_Value>
|
||||
|
||||
Workaround: Gracefully restart the affected Wildfire cluster nodes.
|
||||
|
||||
## WF500-6259
|
||||
|
||||
When a WildFire cluster node configured as a server or worker node is rebooted, issuing the CLI command, global sample-status does not update the samples processed list on the active controller and non-server worker nodes.
|
||||
|
||||
Workaround: Gracefully restart the affected WildFire active controller and passive controller in the cluster.
|
||||
|
||||
## WF500-6270
|
||||
|
||||
The WildFire cluster server and worker nodes might disconnect from the Wildfire cluster management network, resulting in a notifier process exit on WildFire cluster controllers.
|
||||
|
||||
Workaround: Gracefully restart the WildFire cluster node where the process exit occurred.
|
||||
|
||||
## WF500-6222
|
||||
|
||||
When WildFire secure cluster communication is enabled using a custom DNS, the cluster formation might fail due to cluster management communication issues.
|
||||
|
||||
Workaround: Do not configure a custom DNS when WildFire secure cluster communication is enabled.
|
||||
|
||||
## WF500-6176
|
||||
|
||||
When Panorama is used to manage a WildFire cluster, switchover functionality for active and passive controller roles is not available.
|
||||
|
||||
## PAN-308507
|
||||
|
||||
Strata Logging Service (SLS) log-forwarding streams intermittently show as inactive. When checking the status of log-forwarding connections, one or more streams are reported as inactive. Restarting the log-receiver process temporarily resolves the issue, but the streams become inactive again after approximately 1-2 hours. This intermittent inactivity results in log loss.
|
||||
|
||||
Reference in New Issue
Block a user