> Source: [sk106409](https://support.checkpoint.com/results/sk/sk106409)

# sk106409 - SIM Affinity and CoreXL FW Instances might be using the same CPU cores

| Property | Value |
|----------|-------|
| Solution ID | sk106409 |
| Date Created | 2015-06-09 |
| Last Modified | 2022-08-13 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Outputs of "*fw ctl affinity -l -r -v -a*" command and "sim affinity -l" command show that SIM Affinity and CoreXL are using the same CPU cores (despite the correct initial configuration).

* Output of "*cat /proc/cpuinfo*" command shows that the processor numbers are not running from 0 to maximal CPU core in sequence.

  For example:
  * Processor with Physical ID 1 gets CPU core IDs from 0 to 3
  * Processor with Physical ID 0 gets CPU core IDs from 4 to 7

  Example outputs of "*$FWDIR/boot/fwboot cpuid*" command:
  * After 1st reboot: *7 6 5 4 3 2 1 0*
  * After 2nd reboot: *3 2 1 0 7 6 5 4*

## Solution

[Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue.   
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.   
For faster resolution and verification please collect [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) files from the Security Management and Security Gateways involved in the case.

**Code was improved:** SIM Affinity, instead of saving the IDs of logical CPU cores, will save the IDs of physical CPU cores in the *$PPKDIR/boot/modules/sim_aff.conf* file:

* Each time SIM Affinity writes to the *sim_aff.conf* file, it will translate the CPU core IDs from logical to physical
* Each time SIM Affinity reads from the *sim_aff.conf* file, it will translate the CPU core IDs from physical to logical

**Notes:**

* Initializing of the translation array is performed using the */tmp/sim_cpuids.tmp* file (the location in the line of each logical CPU core represents the equivalent physical CPU core).
* SIM Affinity to logical CPU cores might change after installing this hotfix and rebooting (this is done to maintain consistency with the physical CPU cores).

**Hotfix installation instructions:**

1. Hotfix has to be installed on **Security Gateway / *each* cluster member** .   

2. Transfer the hotfix package to the machine (into some directory, e.g., */some_path_to_fix/* ).   

3. Unpack the hotfix package:

   ```
   [Expert@HostName]# cd /some_path_to_fix/
   [Expert@HostName]# tar -zxvf sim_HOTFIX_NAME.tgz
   ```

4. Install the hotfix:

   ```
   [Expert@HostName]# ./sim_HOTFIX_NAME
   ```

   **Note:** The script will stop all of Check Point services (*cpstop* ) - read the output on the screen.   

5. Reboot the machine.

---

# 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