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

# sk169763 - Cluster member in OpenStack or Hyper-V does not work properly

| Property | Value |
|----------|-------|
| Solution ID | sk169763 |
| Date Created | 2020-09-30 |
| Last Modified | 2025-12-21 |
| Technical Level | Advanced |
| Products | Security Gateway, Cloud Firewall |
| Versions | R81.20, R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20 |
| Platform | OpenStack, KVM, Hyper-V |

## Symptoms

- * ClusterXL status on OpenStack or Hyper-V shows Active/Down or Active/Standby.

* Cluster interface ethX shows "Down" in ClusterXL status.

* CCP packets do not arrive to Cluster members.

## Cause

By default, ClusterXL is supposed to use Unicast for CCP (Cluster Control Protocol packets). If Unicast is not used in some Hypervisor environments, CCP packets do not arrive at the other Cluster member.

<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