Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

ClusterXL Sync Network on different subnets

Jump to solution

Hello Team,

Does anyone know if it is possible to have a ClusterXL Sync network on different subnets?

 

Example:

  • FW01 Sync     - 192.168.10.1 /30   - DataCentre A
  • FW02 Sync      - 10.0.0.1/30           - DataCentre B

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%)."

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Sapphire

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.

View solution in original post

5 Replies
Highlighted
Sapphire

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.

View solution in original post

Highlighted

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.

0 Kudos
Highlighted
Sapphire

Sorry, i have corrected my answer!

0 Kudos
Highlighted

Great! Given you a thumbs up for this. Very helpful.

0 Kudos
Highlighted
Sapphire

Glad about that 😉

0 Kudos