Onboarding a Cluster for Active-Active High-Availability Deployment

An active-active high-availability cluster must have a minimum of two nodes and a maximum of four nodes.
Create a cluster for active-active high-availability as follows:
  1. Log in to the RUCKUS One web user interface with your credentials.
  2. Create the Venue for adding the device. Refer to Adding a Venue for more information.
  3. Create the tunnel profile. Refer to Creating a Tunnel Profile for more information.
    Note: Ensure you configure the following setting in the Tunnel Profile.
    • Tunnel Idle Timeout: Range: 5 through 10080 minutes, 1 through 7 days, or 1 week.
    • Tunnel Keep Alive Interval: Range: 1 through 5 seconds.
    • Tunnel Keep Alive Retries: Range: 3 through 10 retries.
  4. On the RUCKUS One navigation bar, click RUCKUS Edge.
    This displays the RUCKUS Edge page.
  5. In the RUCKUS Edge page, click Add and select Cluster. This displays the Add Cluster page.

    Add Cluster

  6. In the Add Cluster page, enter the following details:
    • Venue: Click the drop-down arrow to select a site for the new cluster.
    • Cluster Name: Enter a meaningful name for the cluster profile.
    • Description: Enter a purposeful statement for the device.
    • High-Availability Mode: Select the Active-Active option.

      All RUCKUS Edges collaborate to balance the load, boosting both redundancy and performance. If one RUCKUS Edge fails, the others seamlessly take over its tasks.

  7. In the RUCKUS Edges section, define a minimum of two Edge devices as two nodes are required to establish a complete cluster. You can add a maximum of four nodes per cluster. Enter the RUCKUS Edge Name and Serial Number of the first Edge device in the available fields. To add more Edges to the cluster, click the Add another SmartEdge option and enter the RUCKUS Edge Name and Serial Number.
    • RUCKUS Edge Name: Enter a meaningful name for the nodes.
    • Serial Number: Enter the serial number of the Edge device. You can obtain the serial number by logging in to the Edge CLI or by looking at the label on the physical Edge device.
    • Model: After the serial number is entered, the model's name is displayed automatically.
    To delete a Edge device, click on the Delete icon adjacent to the RUCKUS Edge entry.

    Adding a Four-Node Cluster

    Note: The one-time-password (OTP) is automatically sent to your email address or through the SMS for verification when you add a virtual Edge node (each Edge added as part of the Add Cluster receives an OTP for verification). The password expires in 10 minutes, and you must complete the authentication process before the OTP expires; otherwise, you have to request a new OTP.
  8. Click Add.
    This displays the newly added Cluster and Nodes in the SmartEdge screen.

    Node Status

    Note: After the nodes are added to the venue and onboarded, the Node Status is Needs port config.
  9. Select the cluster and Run Cluster & SmartEdge configuration wizard.

    Configuring Cluster

    The Cluster & SmartEdge Configuration page is displayed.

    Cluster Configuration Page

  10. Select LAG, Port, HA Settings and click Next.
    The LAG Settings page is displayed.
  11. Select every node in the cluster and configure.
    Once the configuration matches on all the Edge devices in the cluster, the status of the cluster turns green.

    Device Configuration Match

  12. Click Next and configure Port Settings.

    Port Settings

  13. Click HA Settings, the HA Settings page is displayed.
  14. Select the Load Distribution required from the following drop-down options:
    • Random distribution: All the APs have different random list for Edge IPs.
    • Per AP group distribution: All the APs in same AP group will have the same random list of Edge IPs of the active-active cluster.

    High Availability Settings

  15. Click Next.
    The configuration Summary page is displayed.

    Configuration Summary

  16. Click Apply & Finish.
    When the configuration settings are applied to all the Edge devices in the cluster, the HA Status for each node displays Active.

    High Availability Status