Which may NOT be a reason for this difference?

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?

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?

A.
Synchronization is not working between the two members

B.
SGMs in a 61k environment only sync selective parts of the connections table.

C.
Heavily used short-lived services have had synchronization disabled for performance
improvement.

D.
Standby member does not synchronize until a failover is needed.

Explanation:



Leave a Reply 0

Your email address will not be published. Required fields are marked *