Support Center > Search Results > SecureKnowledge Details
Policy installation fails after changing cluster member priority Technical Level
  • After switching priority to the second member using the "Switch to higher priority Cluster Member" option, policy installation fails on the "Active" member only with "Operation incomplete due to timeout" error message.

  • Policy check with command: "fw stat" shows that the policy is installed on both members.

  • After installing policy in the second time the issue is resolved.

Warning: In general and regardless of this issue, it's recommended to avoid changing cluster members' priorities unless absolutely necessary - especially in "Primary Up" mode.

Failover caused by the priority change has a potentially greater connectivity impact than any other type of failover.

Upon changing priority, the actual cluster member IDs change. The cluster then decides that it is no longer the owner of this connection and decides it needs to forward it to the active member for routing.

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