What is the best description of the Cluster Synchronization Timeout (min)?
What is the best description of the Cluster Synchronization Timeout (min)?
The Cluster Synchronization Timeout (min) refers to the maximum time that the local firewall waits before transitioning to an Active state when synchronization within the cluster is being hindered by another member. This definition captures the core function of this timeout setting, ensuring high availability by allowing sufficient time for the cluster members to fully synchronize before the local firewall becomes active.
This question was on the exam.. Nov 2023
Definitely B Cluster Synchronization Timeout (min) —Maximum number of minutes that the local firewall waits before going to Active state when another cluster member (for example, in unknown state) is preventing the cluster from fully synchronizing (range is 0 to 30; default is 0).https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-web-interface-help/device/device-high-availability/ha-general-settings
Correct answer is B https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-web-interface-help/device/device-high-availability/ha-general-settings
B is correct
Cluster Synchronization Timeout (min) —Maximum number of minutes that the local firewall waits before going to Active state when another cluster member (for example, in unknown state) is preventing the cluster from fully synchronizing (range is 0 to 30; default is 0).
C (Optional) Change the HA4 Keep-alive Threshold (ms) to specify the timeframe within which the firewall must receive keepalives from a cluster member to know that the cluster member is functional; range is 5,000 to 60,000; default is 10,000. https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-admin/high-availability/configure-ha-clustering
The direct quote from this linked article is, "Change Cluster Synchronization Timeout (min), which is the maximum number of minutes that the local firewall waits before going to Active state when another cluster member (for example, in unknown state) is preventing the cluster from fully synchronizing; range is 0 to 30; default is 0." This makes the answer B the correct response.
similar to #277