State Synchronization is enabled on both members in a cluster, and the Security Policy is successfully installed. No protocols or services have been unselected for “selective sync”. The following is the fwtab t connections s output from both members:

Is State Synchronization working properly between the two members?

A.
Members A and B are synchronized, because ID for both members is identical in the connections table

B.
The connectionstable output is incomplete. You must run the cphaprob state command, to determine if members A and B are synchronized

C.
Members A and B are not synchronized, because #PEAK for both members is not close in the connections table

D.
Members A and B are synchronized, because #SLlNKS are identical in the connections table

E.
Members A and B are not synchronized, because #VALS in the connections table are not close

Explanation:

Debugging State Synchronization
To monitor the synchronization mechanism on ClusterXL or thirdparty OPSEC certified clustering products, run the following commands on a cluster member.
FW TAB T CONNECTIONS S
One quick test to verify if State Synchronization is working properly is by running the fw tab t connections s command from cluster members. If the #VALS numbers are very close between cluster members, cluster members are synchronizing properly.

Here is a sample output of fw tab t connections s:

HOST NAME ID #VALS #PEAK #SLINKS
localhost connections 8158 4 22 4
If the #VALS numbers are very close between cluster members, it is safe to say State Synchronization is working properly.
The key line is “If the #VALS numbers are very close between cluster members, it is safe to say State Synchronization is working properly.”

Reference.
http://www.checkpoint.com/services/education/training/samples/ClusterXL_Sample_Chapter.pdf