Support Center > Search Results > SecureKnowledge Details
Change of Cluster Member priority when the kernel parameter 'fwha_freeze_state_machine_timeout' is enabled may cause network outage
Symptoms
  • ClusterXL is configured in New High Availability mode

  • User has enabled kernel parameter 'fwha_freeze_state_machine_timeout' per sk25971 / sk32488

  • User changes the Priority of the members (SmartDashboard - cluster object - Properties - Cluster Members - Increase/Decrease Priority) and installs the policy

  • During policy installation, fail-over occurs inside the cluster and traffic stops passing through the cluster

  • If the 'fwha_freeze_state_machine_timeout' is disabled (set to 0), then during policy installation, traffic keeps passing correctly through the cluster
Cause

When the user changes the priority of the members via SmartDashboard and then installs policy, the cluster configuration will be restarted on each member (transparently for traffic) and will be updated with the new Member Priorities.

By default, the kernel parameter 'fwha_freeze_state_machine_timeout' is disabled. Starting in R75.40VS and R76, by default this kernel parameter is enabled and its value is set to 30 seconds.

When the kernel parameter 'fwha_freeze_state_machine_timeout' is enabled (set to some value per either of these solutions - sk25971 / sk32488), the cluster configuration on members will not be updated correctly even though output of "cphaprob state" command shows that the Member IDs and their state have changed.


Solution
Note: To view this solution you need to Sign In .