Active-Active High Availability

The Active-Active High Availability (AA HA) feature ensures that if one node in a cluster fails, the other nodes continue to manage the requests, providing continuous service without interruption.

Feature Overview

This feature requires a minimum of two nodes and supports a maximum of four nodes in a cluster. The Active-Active HA mode is designed to provide both redundancy and scalability. In this mode, all cluster nodes can simultaneously manage tunnels from APs.

If the SD-LAN service is enabled on the Edge cluster in Active-Active HA mode, RUCKUS One will provide APs with a list of Edge VXLAN Tunnel Endpoint (VTEP) IP addresses. This list includes the IP address of each node in the cluster.

To distribute the load of AP tunnels across all nodes in the Active-Active HA mode cluster, two load distribution methods are supported.

  • Random distribution: Each AP randomizes the Edge VTEP IP address list using its serial number as a random seed. Each AP will then attempt to connect to the first Edge IP address in its randomized list, known as the Primary Edge. This approach directs the tunnels from APs to different nodes in the Active-Active HA cluster, effectively distributing the load.
  • Per AP-group distribution: Each AP randomizes the Edge VTEP IP address list using the identifier of its AP Group. In this method, all APs in the same AP Group will derive the same randomized IP list. As each AP will attempt to connect to the first Edge IP address in its randomized list, all APs in same AP Group will tunnel to same Edge node. As long as a wireless client roams across APs in the same AP Group, there will not be any MAC movement for that wireless client's MAC address in the Edge uplink port switch network.

In a High Availability configuration, if an AP is unable to connect to the first Edge IP address in its randomized list, it will attempt to connect to the next IP address in the list and continue this process until a connection is established. If it cannot connect to the last IP address in the list, it will try the first IP address again. The AP will continue this process until it successfully connects to an Edge device. The Edge to which the AP connects is referred to as the Active Edge.

When an AP is connected to a RUCKUS Edge node, it will continuously send periodic keepalive traffic to ensure the Edge device is reachable. If the keepalive message to the Active Edge fails, the AP will attempt to connect to the next Edge node in the list. This process is known as AP tunnel failover to the next Edge node.

Requirements

The Cluster Interface is crucial for enabling clustering in RUCKUS Edge. To configure it, a dedicated physical interface must be provided within the RUCKUS Edge. facilitates cluster formation, the exchange of cluster information, and node health maintenance. For each node in the dual-node cluster, this interface should be connected to the same Layer 2 network, separate from the LAN network.

Considerations

In RUCKUS Edge-deployed networks, all APs will have the IP addresses of all nodes in the active-active high availability cluster. Depending on the load distribution method, some APs will tunnel to node-1, while others will tunnel to node-2, and so on. Each AP will periodically send keepalive messages to the node it is tunneling to. In the event of a failure, the following scenario is established:

  • If a node does not respond to the keepalive messages, APs that were tunneling to that node will now tunnel to other nodes in the cluster.
  • After the failed node becomes operational and rejoins the cluster, the APs will resume tunneling to that node at a scheduled time.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

This feature requires the following prerequisites:

  • Install two to four RUCKUS Edge devices based on the scale and redundancy needs.
  • Use Edge nodes with comparable hardware capabilities to form a cluster.
  • Configure all nodes in the Active-Active HA cluster to have their LAN ports within the same subnet..
  • Create a venue and associate the RUCKUS Edge cluster.