Check_Point
156-115.80 · Question #114
You run the command fw tab -t connections -s on both members in the cluster. Both members report differing values for "vals" and "peaks". Which may NOT be a reason for this difference?
The correct answer is D. Standby member does not synchronize until a failover is needed. Explanation/Reference:
Troubleshooting and Optimization
Question
You run the command fw tab -t connections -s on both members in the cluster. Both members report differing values for "vals" and "peaks". Which may NOT be a reason for this difference?
Options
- ASynchronization is not working between the two members
- BSGMs in a 61k environment only sync selective parts of the connections table.
- CHeavily used short-lived services have had synchronization disabled for performance improvement.
- DStandby member does not synchronize until a failover is needed.
How the community answered
(46 responses)- A2% (1)
- B13% (6)
- C7% (3)
- D78% (36)
Explanation
Explanation/Reference:
Topics
#connection table synchronization#fw tab#cluster sync#SGM
Community Discussion
No community discussion yet for this question.