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

# sk184602 - High Availability failure on Spark Firewall Cluster 

| Property | Value |
|----------|-------|
| Solution ID | sk184602 |
| Date Created | 2026-01-28 |
| Last Modified | 2026-02-03 |
| Technical Level | General |
| Products | Spark Firewall (Locally Managed) |
| Versions | R82.00.X, R81.10.X |
| Platform | 1570R, 1575R, 1500, 1900, 2000, 1600, 1800, 1595R, 15x5 |

## Symptoms

- * Firewall cluster High Availability (HA) is down.

* The output for the '`cphaprob stat`' command shows, "*Cluster members report:
  Mismatch in the number of CoreXL FW instances has been detected*."

* '`fw ctl multik stat`' command shows the difference in the number of firewall instances across cluster members.

## Cause

An incorrect and inconsistent number of CoreXL firewall instances is configured on the cluster members. The \`*/opt/fw1/boot/boot.conf*\` file sometimes contains an incorrect value (for example, 20 instead of the expected 15 for 1900 appliances). As a result, the CoreXL instance count does not always match the hardware. This mismatch caused the cluster to detect a configuration inconsistency, resulting in High Availability failure.

## Solution

This problem was fixed. The fix is included starting from:

* [Check Point R81.10.17](https://support.checkpoint.com/results/sk/sk183153)

* [Check Point R82.00.10](https://support.checkpoint.com/results/sk/sk184357)

  Note - The fix was not merged into R82.00.05 and R82.00.05

If you choose not to upgrade, [contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for your version.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk138892) file from the Security Gateway / each Cluster Member involved in the case.

**Workaround:**

Follow the instructions in [sk174423](https://support.checkpoint.com/results/sk/sk174423) to manually set the CoreXL Instance Count on both cluster members.

---

# 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