How many cores can be used in a Cluster for Firewall-kernel on the new device?

You have a Gateway is running with 2 cores. You plan to add a second gateway to build a cluster and used a device with 4 cores. How many cores can be used in a Cluster for Firewall-kernel on the new device?
A. 3
B. 2
C. 1
D. 4

Download Printable PDF. VALID exam to help you PASS.

4 thoughts on “How many cores can be used in a Cluster for Firewall-kernel on the new device?

  1. A : New device has 4 cores. Core XL enable 3 core for kernel instance

    Default Configuration of CoreXL
    When you enable CoreXL, the number of kernel instances is based on the total number of CPU cores.

    Number of Cores

    Number of Kernel Instances

    1 1
    2 2
    4 3
    6-20 Number of cores, minus 2
    More than 20 Number of cores, minus 4 — but no more than 40

  2. This is one of those questions that tries to trick you. The correct answer should be B. Cores are either being used by CoreXL (Kernel) or SND (Interfaces). You can use two different servers with a different amount of cores without the additional cores being a complete waste. What’s required for CoreXL to work is that the number of CoreXL workers are equal between all cluster members.

    So you could have:

    Member1 = 2 cores
    Member2 = 4 cores
    Member3 = 6 cores

    No problem. But Member2 and Member3 would have to go into cpconfig –> (9) Check Point CoreXL and set their number of CoreXL workers to 2 to match Member1. When you only have 2 cores the distribution is always set to 2 works and 0 SND by default. In this scenario Member2 would have 2 cores left for SND, and Member3 would have 4 cores left for SND.

    The tricky part of this question is the wording. It specifically says “How many cores can be used in a Cluster for Firewall-kernel on the new device?” Firewall-kernel equals CoreXL workers which as to be the same amount between all members in the cluster.

Leave a Reply

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


The reCAPTCHA verification period has expired. Please reload the page.