What is mandatory for ClusterXL to work properly?
What is mandatory for ClusterXL to work properly?
For ClusterXL to work properly, the number of CPU cores must be the same on all participating cluster nodes. This ensures the proper load balancing and synchronization among the nodes in the cluster. If the cluster nodes have a different number of cores, it can lead to unexpected behavior, including one member being active while the other is stuck in a 'Ready' state, and it may never join the cluster properly until the number of cores is matched on both cluster members. Therefore, option A is correct.
Correct answer is A
I think no. If need add cluster having more core than the original one, CP is going to adjust the New Cluster CP to the same core count as the original one using. Actually, there is another question asking for this also.
I agree. B doesn't make sense, as Magic MACs must be identical for all members of a cluster.
(Agree with vhick that it's answer A.)
Answer is A as mentioned here : Therefore, in order to avoid unexpected behavior, ClusterXL is supported only between machines with identical CPU characteristics https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_ClusterXL_AdminGuide/html_frameset.htm?topic=documents/R80.30/WebAdminGuides/EN/CP_R80.30_ClusterXL_AdminGuide/211307
A - All Cluster Members must run on identically configured hardware platforms.
The Magic MAC number must be the same and identicall in all Cluster nodes A is the correct Answer
Tricky question: If unique = different (I do not think that unique = identical), B is not the correct answer because Magic MAC number (or cluster ID) should be the same for each cluster node (member), otherwise, each node runs as a member of a different cluster into the same network segment. A is correct because, if cluster nodes (members) have different number of cores configured, one member will be active, an the other member gets stuck into "Ready" state ando never joins the cluster properly until number of cores get paired on both cluster members.
Number of CoreXLClosed Firewall instances on all Cluster Members must be the same https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_ClusterXL_AdminGuide/Topics-CXLG/ClusterXL-Requirements-and-Compatibility.htm
The magic number must be uniq per Cluster, but the same between the according notes!
It’s absolutely NOT B as like some of you already pointed out, Magic MAC can NOT be different on different modules in the same cluster. It does though need to be unique/different on modules of DIFFERENT CLUSTERS within the same network!!!
For A: Cores is not the same as corexl instances, you can have different cores but must to configure same instances
Correct answer is A fot too
A should be the answer
A is the answer
Magic MAC must be unique or identical per cluster node, that is correct. Good answer is B
Do you know the difference between unique and identical, dude?