What could NOT be a reason for synchronization issues in a Management HA environment?
What could NOT be a reason for synchronization issues in a Management HA environment?
Configuring unique IP addresses per Management Server would not impact the CA Certificate and therefore would not cause synchronization issues. On the other hand, network connectivity failures between servers, servers being in collision mode, and mismatched products on the servers are all valid reasons for synchronization issues in a Management HA environment.
B, C and D definetly ARE reason for synchronization issues...I'll go with A and I think the trick here is that you configure a UNIQUE ip PER management, meaning that the IPs are different
A NOT D: https://support.checkpoint.com/results/sk/sk39345 General restrictions for Primary and Secondary Security Management servers: - The SmartEvent Software Blade can only be enabled on the active server in Management High Availability environment - Must have identical Check Point versions and identical hotfixes installed. To see the build number, run cpinfo -y FW1 - Must have identical products installed (i.e, Management HA is not supported between a Standalone machine and machine that runs only Security Management server)
- Must have identical products installed (i.e, Management HA is not supported between a Standalone machine and machine that runs only Security Management server) This is literally answer D.
This IS a reason for synchronization issues... the questions is NOT a reason for synchronization issues
A is correct. It won't matter if they have unique IP addresses. The other answers would cause issues.
A is the one that not is a reason.
NOT, answer A
Selected Answer: A
Sync issues: • Hardware clocks do not match, even with adjustments for different time zones • The products installed on the servers do not match; one device is a Standalone Server while the other is only a Security Management Server • The same upgrade path was not followed; the primary management server was upgraded while the secondary server was clean installed directly to the new version • There is a network connectivity failure between the servers • Servers are in Collision Mode. Two servers, both in active state cannot be synchronized either automatically or manually