- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hello Team,
Does anyone know if it is possible to have a ClusterXL Sync network on different subnets?
Example:
The two ClusterXL members will be in two different locations connected by EVPN or MPLS and the Sync Network will be routed rather than being a direct connection between them.
SK43984 states that "Cluster networks must meet the requirements for latency (less than 30 millisec) and packet loss (less than ~2-3%)."
The most interesting entry can be found in ClusterXL Administration Guide R80.20 p.54:
Synchronizing Clusters on a Wide Area Network
Organizations sometimes need to locate Cluster Members in geographical locations that are distant from each other. A typical example is a replicated Data Center, whose locations are widely separated for disaster recovery purposes. In such a configuration, it is clearly impractical to use a cross cable for the synchronization network.
The synchronization network can be spread over remote sites, which makes it easier to deploy geographically distributed clustering. There are two limitations to this capability:
1. The synchronization network must guarantee no more than 100ms latency and no more than 5% packet loss.
2. The synchronization network may only include Layer 2 networking devices - switches and hubs. No Layer 3 routers are allowed on the synchronization network, because routers drop Cluster Control Protocol (CCP) packets.
You can monitor and troubleshoot geographically distributed clusters using the command line interface.
The most interesting entry can be found in ClusterXL Administration Guide R80.20 p.54:
Synchronizing Clusters on a Wide Area Network
Organizations sometimes need to locate Cluster Members in geographical locations that are distant from each other. A typical example is a replicated Data Center, whose locations are widely separated for disaster recovery purposes. In such a configuration, it is clearly impractical to use a cross cable for the synchronization network.
The synchronization network can be spread over remote sites, which makes it easier to deploy geographically distributed clustering. There are two limitations to this capability:
1. The synchronization network must guarantee no more than 100ms latency and no more than 5% packet loss.
2. The synchronization network may only include Layer 2 networking devices - switches and hubs. No Layer 3 routers are allowed on the synchronization network, because routers drop Cluster Control Protocol (CCP) packets.
You can monitor and troubleshoot geographically distributed clusters using the command line interface.
Hello Günther,
Thanks for your swift response. The SK refers to the Cluster IPs on different subnets rather than Sync network. In the sk32073 example the Sync network is actually on the same subnet.
My question is specifically about the Sync networks being on different subnets with a router between them.
Sorry, i have corrected my answer!
Great! Given you a thumbs up for this. Very helpful.
Glad about that 😉
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 9 | |
| 8 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY