> Source: [sk174423](https://support.checkpoint.com/results/sk/sk174423) # sk174423 - Configuring CoreXL Firewall instances on Spark Firewall | Property | Value | |----------|-------| | Solution ID | sk174423 | | Date Created | 2021-07-11 | | Last Modified | 2026-01-28 | | Technical Level | General | | Products | Spark Firewall (Locally Managed) | | Versions | R82.00.X, R81.10.X | | Platform | 1575R, 1500, 1900, 2000, 1600, 1800, 1595R, 2500, 15x5 | ## Solution CoreXL ------ CoreXL is a performance-enhancing technology for Security Gateways on multi-core platforms. CoreXL makes it possible for the CPU cores to perform multiple tasks concurrently. This enhances the Security Gateway performance. On a Security Gateway with CoreXL enabled, the Firewall kernel is replicated multiple times. Each replicated copy of the Firewall kernel, or CoreXL Firewall instance, runs on one CPU core. These CoreXL Firewall instances handle traffic concurrently, and each CoreXL Firewall instance is a complete and independent Firewall inspection kernel. When CoreXL is enabled, all the Firewall kernel instances in the Security Gateway process traffic through the same interfaces and apply the same security policy. Number of CoreXL Firewall instances ----------------------------------- **Note** - Make sure you activated your license or the core count might be incorrect. See [sk172912](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk172912). The table below shows the CoreXL configuration on Quantum Spark Appliances - the default and the maximum number of CoreXL Firewall instances for different states of IPv6: |------------------------------------|---------------------------|--------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------| | Model of a Quantum Spark Appliance | Total number of CPU cores | Default number of IPv4 instances when IPv6 is disabled | Default number of IPv4 instances when IPv6 is enabled | Default number of IPv6 instances when IPv6 is enabled | Maximum^\*^ number of IPv6 instances when IPv6 is enabled | | 1535 | 3 | 3 | 2 | 2 | 2 | | 1530 | 3 | 3 | 2 | 2 | 2 | | 1555 | 4 | 4 (3)\*\* | 2 | 2 | 2 | | 1550 | 4 | 4 | 2 | 2 | 2 | | 1575 | 3 | 3 | 2 | 2 | 2 | | 1570 | 3 | 3 | 2 | 2 | 2 | | 1595 | 4 | 4 (3)\*\* | 2 | 2 | 2 | | 1590 | 4 | 4 | 2 | 2 | 2 | | 1570R | 4 | 4 | 2 | 2 | 2 | | 1600 | 12 | 10 (8)\*\* | 10 (8)\*\* | 2 | 10 (8)\*\* | | 1800 | 12 | 10 (8)\*\* | 10 (8)\*\* | 2 | 10 (8)\*\* | | 1900 | 18 | 15 | 15 | 2 | 15 | | 2000 | 24 | 20 | 20 | 2 | 20 | | 1575R | 4 | 3 | 2 | 2 | 2 | | 1595R | 4 | 3 | 2 | 2 | 2 | | 2530 | 3 | 3 | 2 | 2 | 2 | | 2550 | 4 | 3 | 2 | 2 | 2 | | 2560 | 5 | 4 | 4 | 2 | 4 | | 2570 | 6 | 5 | 5 | 2 | 5 | | 2580 | 8 | 7 | 7 | 2 | 7 | | 2590 | 8 | 7 | 7 | 2 | 7 | **\*** The number of IPv6 CoreXL Firewall instances cannot exceed the number of IPv4 CoreXL Firewall instances. \*\* Generally, R81.10.X and R82.00.X have the same CoreXL split for Spark Pro models. For appliances whose default split changed between these two versions, the new number of instances is present in (red). IPv4 CoreXL Firewall instances ------------------------------ **To view the current number of IPv4 CoreXl Firewall instances, run:** `fw ctl multik stat` **To change the number of IPv4 CoreXL Firewall instances:** 1. Run this command in the Expert mode: `FW_BOOT_DIR=/opt/fw1/boot fwboot corexl enable <`*Number of IPv4 Instances*`>` 2. Reboot the appliance. IPv6 CoreXL Firewall instances ------------------------------ **To view the current number of IPv6 CoreXl Firewall instances, run:** `fw6 ctl multik stat` **To change the number of IPv6 CoreXL Firewall instances:** 1. Run this command in the Expert mode: `FW_BOOT_DIR=/opt/fw1/boot fwboot bootconf set_kern6num <`*Number of IPv6 Instances*`>` 2. Reboot the appliance. **Note** - If you see a "No such file or directory" error, create the file */opt/fw1/boot/boot.conf* manually and fill its values based on the model line in the above table. *KERN_INSTANCE_NUM* should set to *Default number of IPv4 instances when IPv6 is disabled COREXL_INSTALLED* should be set to 1 *KERN6_INSTANCE_NUM* should be set to 2 For example, for Spark 1800: `# cat /opt/fw1/boot/boot.conf` `KERN_INSTANCE_NUM 10` `COREXL_INSTALLED 1` `KERN6_INSTANCE_NUM 2` --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content