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

# sk183434 - ElasticXL Cluster Members incorrectly change their state to "Down" when the Synchronization cable is disconnected

| Property | Value |
|----------|-------|
| Solution ID | sk183434 |
| Date Created | 2025-05-07 |
| Last Modified | 2026-05-07 |
| Technical Level | General |
| Products | Scalable Platforms |
| Versions | R82 |
| OS | Gaia |

## Symptoms

- * Scenario 1 - In the ElasticXL Cluster, if the state of the Synchronization interface changes (for example, when you administratively shut it down, or disconnect a cable from it) on the Pivot cluster member (an Active member with the lowest ID), then:

  1. The cluster state of the Pivot cluster member changes to "Down"
  2. The cluster state of all other cluster members remains "ACTIVE"
  3. The Pivot role moves to the cluster member with the next lowest ID

  Example output of the Gaia gClish command "`show cluster state`":

  ```
  
  ID         Unique Address  Assigned Load   State          Name
  
  1 (local)  192.0.2.1       0%              Down           EXL-s01-01
  2          192.0.2.2       50%             ACTIVE(P)      EXL-s01-02
  3          192.0.2.3       50%             ACTIVE         EXL-s01-03
  ```

* Scenario 2 - In the ElasticXL Cluster, if the state of the Synchronization interface changes on **one** of the **non**-Pivot cluster members, then:

  1. The cluster state of the Pivot cluster member remains "ACTIVE"
  2. The cluster state of **all** other cluster members changes to "Down"

  Example output of the Gaia gClish command "`show cluster state`":

  ```
  
  ID         Unique Address  Assigned Load   State          Name
  
  1 (local)  192.0.2.1       100%            ACTIVE(P)      EXL-s01-01
  2          192.0.2.2       0%              Down           EXL-s01-02
  3          192.0.2.3       0%              Down           EXL-s01-03
  ```

## Solution

### Scenario 1 - The state of the Synchronization interface changes on the Pivot cluster member

Check Point R\&D are working on the required fix.

At this time, this behavior is considered a known limitation, where the Pivot member will be the only member in "ACTIVE" state and all other members will be in "Down" state.

### Scenario 2 - The state of the Synchronization interface changes on one of the non-Pivot cluster members

This problem was fixed. The fix is included in:

* [Check Point R82.10](https://support.checkpoint.com/results/sk/sk183506)
* [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 36

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) 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 files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

---

# 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