Configuring a Cluster for Active-Active High Availability Deployment with a LAG Interface

This task describes configuring a multi-node, active-active high-availability RUCKUS Edge cluster, with a LAG interface, in RUCKUS One.
Prior to performing this procedure, you must have already added the Edge cluster (with HA mode as Active-Active) in RUCKUS One.
Configure a multi-node RUCKUS Edge cluster as follows:
  1. Log in to the RUCKUS One web user interface with your credentials.
  2. On the RUCKUS One navigation bar, click Gateway > RUCKUS Edge.
    This displays the RUCKUS Edge page.
  3. Select the checkbox adjacent to the RUCKUS Edge cluster. This highlights the Edit and Run Cluster & RUCKUS Edge configuration wizard options.
    Note: The Node Status is Need port config.

    Run Cluster and RUCKUS Edge Configuration Wizard

  4. Click the Run Cluster & RUCKUS Edge configuration wizard option.
    This displays the Cluster & RUCKUS Edge Configuration Wizard screen of the selected RUCKUS Edge cluster with the two options.
    • LAG, Port, & HA Settings
    • Sub-Interface Settings
    • Cluster Interface Settings
  5. Select the LAG, Port, & HA Settings checkbox and click Next to start the configuration.

    Cluster and RUCKUS Edge Configuration Wizard

  6. Proceed to section Configuring Link Aggregation Group (LAG), Port, and HA Settings for configuration details.

Configuring Link Aggregation Group (LAG), Port, and HA Settings

This section describes configuring LAG, Port, and HA Settings for a RUCKUS Edge cluster. The LAG, Port, & HA Settings wizard begins on the LAG Settings screen, displaying the tab page for the first node in the cluster.
  1. LAG Settings: Click the Add LAG option.

    Add LAG Settings

  2. On the Add LAG interactive sidebar, complete the fields and click Add.
    Note: Refer to Configuring Link Aggregation Group for descriptions of the fields in the Add LAG sidebar.
  3. Repeat and for all other remaining nodes. When the compatibility check successfully passes, click Next to proceed to the next page of the wizard.
    RUCKUS One performs a compatibility check of the configurations on each node. If a mismatch is detected, it displays a warning message labeled Mismatch. You can click on the See Details option to view the root cause and specifics of the mismatch to quickly identify the discrepancies.

    You can Edit or Delete the offending LAG by selecting the checkbox adjacent to the LAG. After the mismatches are resolved, the compatibility check result changes to Pass.

  4. Port General Settings: Configure the port general settings for all Edge devices.
    • Description: Enter a meaningful description for the port settings.
    • Port Type: Select a port type from the drop-down menu.
      Note: As you have configured LAG as a LAN port, for Port Type, select Cluster and enable the Port Enabled option.
    • IP Settings: Configure the IP settings for the cluster port:
      • IP Assignment: Select DHCP or Static/Manual. If static/manual IP is selected, then enter the IP Address and Subnet Mask of the port.
    • Select each of the other node tabs and configure the appropriate port for each node.

    RUCKUS Edge LAG, Port, and Virtual IP Settings: Port Settings

  5. After port settings have been configured for all nodes in the cluster, click Next. The HA Settings page is displayed.
  6. (Optional) Toggle the RUCKUS Edge Fallback option to enable the feature.
    Note: For DMZ tunnelling, Fallback schedule configuration for DC cluster need to be configured under DMZ cluster HA setting.
  7. Choose one the following Fallback Schedule option.
    • Daily: Sets the fallback schedule for the specified time each day.
    • Weekly: Sets the fallback schedule for the chosen day at the specified time.
    • By Interval: Sets the fallback schedule for the designated interval.
    Note: The scheduled fallback time will align with the local time zone of the venue, ensuring the fallback operations occur at the correct local time.
    Note: Fallback scheduled time is not automatically adjusted for Daylight Saving Time. Therefore, when exiting Daylight Saving Time, the RUCKUS Edge device will trigger fallback an hour earlier than the scheduled time and while entering Daylight Saving Time, it will trigger fallback an hour later.
  8. Select the Load Distribution required from the following drop-down options:
    • Random distribution: All the APs have a different random list for Edge IPs.
    • Per AP group distribution: All the APs in the same AP group will have the same random list of Edge IPs of the active-active cluster.

    High Availability Settings

  9. Click Next.
    The configuration Summary page is displayed, reflecting configuration settings for the cluster.
  10. View and verify the configuration details and click Apply & Continue proceed to the Cluster Interface Settings configuration, or click Apply & Finish to complete the LAG, Port, and HA Settings configuration without proceeding to the Cluster Interface Settings configuration.
    When the configuration settings are applied to all the Edge devices in the cluster, the Node Status changes from Needs Port Config to Operational, Cluster Status displays Ready #/# (reflecting how many nodes of the total number of nodes are Ready), and HA Status for each node is Active.
  11. Proceed to section Configuring Cluster Interface Settings for configuration details.

Configuring Cluster Interface Settings

The cluster interface is used as a communication channel between the RUCKUS Edge devices.
This section describes configuring Cluster Interface Settings.

After configuring the LAG, Port, and HA Settings and clicking Apply & Continue (as described in Configuring Link Aggregation Group (LAG), Port, and HA Settings), select the Cluster Interface checkbox and click Next. This displays Cluster Interface page containing a tab for each Edge device in the cluster.

  1. On the first device tab, configure these settings:
    • Set cluster interface on: Use the drop-down menu to select the port that you want to serve as the cluster interface to the other Edge devices.
    • Enter the IP Address and Subnet Mask address of cluster interface port.
  2. Repeat for all other nodes in the cluster.
  3. Click Apply & Finish.