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

# sk180184 - ClusterXL mode does not change to "Primary Up" when setting the cluster object to "Switch to higher priority Cluster Member" on cluster member recovery

| Property | Value |
|----------|-------|
| Solution ID | sk180184 |
| Date Created | 2022-11-03 |
| Last Modified | 2022-11-22 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * When you install the policy on the cluster after setting the cluster object with "Switch to higher priority Cluster Member", the cluster remains in "Active Up" mode.

* The */var/log/messages* show:

  *Cluster policy installation completed successfully without negotiation*
* The checkbox "For gateway clusters, if installation on a cluster member fails, do not install on that cluster" is not checked as the policy installation mode.

## Cause

The policy is installed separately on each cluster member. A mismatch occurs in the cluster modes because the policy is installed on one member before it is installed on the other member. An automatic mechanism corrects it to the previous mode, so the cluster continues to run.

<br />

## 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