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

# sk163714 - Graceful failover with CoreXL mismatch after a CoreXL license upgrade

| Property | Value |
|----------|-------|
| Solution ID | sk163714 |
| Date Created | 2019-11-23 |
| Last Modified | 2021-05-21 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * `cphaprob stat` shows 'Active / Down' on one member and 'Ready' on the other member after attaching a new license to one of the cluster members, followed by a reboot.
* Error: "Ready state reason: another member was detected with a lower number of CoreXL instances".
* Running `fw ctl affinity -l -v -a` on both members shows a different number of CPUs listed at the bottom (e.g. "The current license only permits using CPU 0").

## Cause

For clustering to correctly synchronize the connection table to the secondary member, the gateways should have the same number of cores. After attaching a new license with a different number of cores, rebooting the device will automatically adjust the number of cores used by the appliance.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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