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

This section describes configuring a cluster for high availability without a LAG interface in RUCKUS Edge.
You can choose to configure a cluster without a LAG when the cluster for HA ensure redundancy and failover capabilities including link failures.

Configure a multi-node RUCKUS Edge cluster without a LAG as follows:

  1. Log in to the RUCKUS One web user interface with your credentials.
  2. On the RUCKUS One navigation bar, click Gaeway > RUCKUS Edge.
    This displays the RUCKUS Edge page.
  3. Select the checkbox adjacent to the RUCKUS Edge cluster name. 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 device with the two options.
    • LAG, Port, and HA 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

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: To configure a cluster without a LAG interface, click Next.
  2. Port General Settings: Configure the port general settings for all RUCKUS Edge devices.
    • Description: Enter a meaningful description for the port settings.
    • Port Type: Select a port type from the drop-down menu. Because a LAG is not configured, it is necessary to configure at least one port to function as a LAN port or core port in order to form a cluster. To configure one port as core port, follow these steps:
      1. In the sub-tab for one RUCKUS Edge device (node), select the Port1 sub-tab and enter the description.
      2. In the Port Type drop-down menu, select LAN and select the checkbox Use this port as Core Port. By default, the Port Enabled option is enabled.
      3. Remain in the same device (node) sub-tab, then select the Port2 sub-tab and enter the description.
      4. In the Port Type drop-down menu, select Cluster. By default, the Port Enabled option is enabled.

        Configuring Ports Without a LAG - Port1

        Configuring Ports Without a LAG - Port2

      5. Repeat steps through to configure ports for the other RUCKUS Edge devices (nodes) in the cluster, then click Next.
      Note: Use this port as Core Port is utilized for the SD-LAN service, the core port on this RUCKUS Edge establishes tunnels for directing data traffic effectively.
    • IP Settings: Configure the IP settings for the cluster ports:
      • IP Assignment: Select DHCP or Static/Manual. If static/manual IP is selected, then enter the IP Address, Subnet Mask and Gateway of the port.
        Note: The Gateway field is available only when the Port Type is set to LAN.
  3. After port settings have been configured for all nodes in the cluster, click Next. The HA Settings page is displayed.

    HA Settings

  4. (Optional) Toggle the RUCKUS Edge Fallback option off to disable the feature.
    Note: For DMZ tunnelling, Fallback schedule configuration for DC cluster need to be configured under DMZ cluster HA setting.
  5. 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.
  6. 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

  7. Click Next.
    The configuration Summary page is displayed, reflecting configuration settings for the cluster.
  8. View and verify the configuration details and click Apply & Continue to 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.

    Summary of the Cluster Configuration without a LAG

    Note: After the nodes are configured, 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.

    Nodes Status is Operational

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 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 RUCKUS 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 want to serve as the cluster interface to the other RUCKUS 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.