A ClusterXL configuration is limited to ___ members.
A.
There is no limit.
B.
16
C.
6
D.
2
Get 50% Discount on All Your Purchases
at PrepAway.com - Latest Exam Questions
This is ONE TIME OFFER
50%
Maximum number of nodes in cluserxl is 5.
There no right answer here. Most closest is C tho
0
0
I agree, see sk81300. Maximum supported ClusterXL members is 5, maximum recommended for full state synchronization is 4.
0
0
it is limited to 16 – 25/02/15
ClusterXL Advanced Technical Refernce Guide.pdf page 12
0
0
Looks like it is 16.
See SK93306, top of page 13.
0
0
SK81300 says 8 is the actual maximum, the recommended maximum though is 4, so none of the answers are correct. Man, what a terrible question.
0
0
I agree with Dave. You can find it in sk81300
0
0
Is true. Also, there is two anwers, 8 for CLuster XL and 5 for third party devices…. none of these option shows.
0
0
Critical Device(a.k.a. Problem Notification, Pnote) – Special software device on each cluster member through which the critical aspects for cluster operation are monitored.
When the critical monitored component on a cluster member fails to report its state on time, or when its state is reported as problematic, the state of that member is immediately changed to ‘Down’The complete list of the configured critical devices (pnotes) is printed by the ‘cphaprob -ia list’ command.
Restrictions:
* Total number of critical devices (pnotes)on cluster member is limited to 16.
* Name of any critical device(pnote) on cluster member is limited to 16 characters
I think 16 is the limitation for pnote (problem notification) => Special software device on each cluster member
0
0
Thanks Dave you right it is limited to 8.
0
0
I agree with diman10.
CP_R77_ClusterXL_AdminGuide, page 70. ClusterXL Error Messages
FW-1: fwha_pnote_register: too many registering members, cannot register
The critical device (also known as Problem Notification, or pnote) mechanism can only store up to 16 different devices. An attempt to configure the 17th device (either by editing the cphaprob.conf file or by using the cphaprob -d … register command) will result in this message.
0
0
I believe the answer to be 16. My only source is a lecture I attended last month where I actually took notes. I believe this is a R77 (and coming R80) maximum.
“Cluster Mode
Load Sharing Multicast – min 3 cluster nodes
Load Sharing Unicast
High Availability Mode (most used)
Legacy Mode – not used
Cluster XL – has one active device with at least one standby (up to 15 standby devices).”
0
0
C. 6 is the closest. 16 devices mentioned on the SK are fwd, filters.. etc.
Member refers to security gateway
0
0
Since when we should start choosing the closest answer? I can choose D because we need at least two. Limited how, minimum or maximum?
Here are my notes (judge as you wish):
The following are the maximum numbers of supported members in a cluster:
• Up to 8 cluster members are supported in ClusterXL (in Load Sharing mode, configuring more than 4 members significantly decreases cluster performance due to amount of Delta Sync).
• Up to 5 cluster members are supported 3rd party cluster (in Crossbeam chassis, configuring more than 4 members (APMs) significantly decreases cluster performance due to amount of Delta Sync).
If state synchronization is used in the cluster, then the recommended maximum number of nodes is 4 regardless of the clustering mode used.
Restrictions:
– Total number of critical devices (pnotes) on cluster member is limited to 16.
– Name of any critical device (pnote) on cluster member is limited to 16 characters.
0
0
Hello Catalin,
I have seen from your comments that you have passed this exam (156-315.77)…can you please share some information regarding questions that you didn’t find here…you have mentioned IPS and Threat Prevention…
BR
0
0
Hi, Catalin and “cpconfig”,
Can you share any good information, I am trying to write my exam after 10 days. send me mdf_86 at Hotmail.com.
0
0
8 is the right answer, in the exam appear that option.
0
0
C. 6
0
0
answer is C. 6 because the right answer is “up to 8 members” 6 is the closest i guess…
link: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk81300
0
0