Configuring RUCKUS Edge Cluster Ports and IP Settings

Configure LAG, general ports, sub-interfaces, and virtual IP settings for the Edge cluster according to the network needs.
Note: The Edge devices within the cluster must be in the Operational state to apply these configurations.
Complete the following steps to configure LAGs, general ports, sub-interfaces, and cluster virtual IP settings:
  1. From the RUCKUS One navigation bar, select Gateway > RUCKUS Edge.
    This displays a list of the RUCKUS Edge clusters and devices added to the RUCKUS One tenant account.
  2. Select the checkbox beside the cluster and click Run Cluster & RUCKUS Edge configuration wizard.
    This displays the Cluster & RUCKUS Edge Configuration Wizard page.
    Note: RUCKUS recommends using the Cluster & RUCKUS Edge configuration wizard to configure these settings.
  3. Select LAG, Port, Sub-Interface & Virtual IP Settings and click Next.
    The Cluster & RUCKUS Edge Configuration Wizard page is displayed.
  4. Within the wizard, configure the following:
    Alternatively, you can configure LAG and Ports using the following procedure for each RUCKUS Edge device in a cluster:
    1. From the RUCKUS One navigation bar, click on Gateway > RUCKUS Edge.

      This displays the RUCKUS Edge devices.

    2. Select an Edge cluster and click the icon to expand and view the associated devices.
    3. Click on the device name. This displays the Overview page.
    4. From the Overview page:
      • Click the Configure button on upper-right hand corner and click the Ports or LAGs sub-tab.
      • Click the Ports or LAGs tab and click Configure Port Settings or Configure LAG Settings, respectively.
    5. Proceed with Port General Settings or LAG Settings.

LAG Settings

Create and configure LAGs for all RUCKUS Edge devices in this cluster if needed, or click Next to skip:
  1. Click Add LAG to create a new LAG for the first node in the cluster.
    This displays the Add LAG sidebar.
  2. Enter the following details to add a LAG to the RUCKUS Edge device.
    Note: Adding ports with existing configuration to a LAG will prompt you with a warning message stating that the existing configuration will be deleted from the ports.
    • LAG Name: Select a name for the LAG from the drop-down list. The LAG name is a numeric value from 0 through 3. After the LAG is created, you cannot edit the LAG name.
    • Description: Enter a meaningful, short description about the LAG.
    • LAG Type: The default type is LACP (Dynamic) as RUCKUS Edge does not support static LAG.
    • Mode: Click the drop-down list and select the mode of the LAG. There are two modes:
      • Active: Always initiates Link Aggregation Control Protocol (LACP) and Protocol Data Unit (PDU) to the peer. This is the default mode for RUCKUS Edge LACP LAG.
      • Passive: Never initiates any LACP exchange on its own. It responds only after receiving LACP and PDU messages from the peer/partner device. Hence, both peers cannot be in passive mode. At least one of the peers should be configured in active mode.
    • Timeout: Time interval indicates how long the LACP should wait before declaring the partner as down. This interval also defines the rate at which LACP hello packets are exchanged among the peers. There are two types of timeout.
      • Long: The value of this timeout is 90 seconds. Hello packets are transmitted every 30 seconds. After 3 misses (3*30s = 90 seconds), the peer information is flushed and the LACP state is declared as down.
      • Short: The value of this timeout is 3 seconds. Hello packets are transmitted every 1 second. After 3 misses (3*1s = 3 seconds), the peer information is flushed. This is the default timeout for RUCKUS Edge LACP LAG.
    • Select LAG Members: A physical port associated with a LAG interface is a LAG member. To associate LAG members, select the ports to be members of this LAG. The Port Enabled option beside the respective port is enabled by default. Toggle the button to disable the port. Selecting Port1 enables Access port and Port2 enables Core port option. Select both ports Port1 and Port2 if Access and Core separation is not intended.
      Note: Access/Core separation is part of the SD-LAN feature. Refer Software Defined Local Area Network, for more information.
    • Port Type - Select the type of port from the drop-down list.
      Note: A maximum of two WAN interfaces are allowed.

    Port Type Configuration

    Port Type Use port as IP Settings
    WAN Not applicable: The WAN port type does not support access and core separation. Both roles are performed in the same port.
    • Choose IP Assignment
      • DHCP: Automatically provides IP address with the host IP address.
      • Static/Manual: Enter the following:
        • IP Address
        • Subnet Mask
        • Gateway
    • Click the Use NAT Service toggle to enable the option and enter the following NAT IP Addresses Range:
      • Start
      • End
    LAN Applicable to SD-LAN services only.

    Select the required checkboxes:

    • Core port
    • Access port

    Hover over the icon next to Access port and click See the compatibility requirements to check the Compatibility Requirement for Access/Core separation.

    • IP Address
    • Subnet Mask
    Cluster Not Applicable Choose IP Assignment
    • DHCP: Automatically provides IP address with the host IP address.
    • Static/Manual: Enter the following:
      • IP Address
      • Subnet Mask
  3. Click Add.
    The Add LAG sidebar closes and the newly added LAG appears in the LAG Settings list.
  4. Click the sub-tab for the second node in the cluster, then repeat and to add a LAG to the second node.
    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.

    LAG Nodes Compatibility Check with Mismatch

  5. Click Next.
    The Port General Settings page is displayed.

Port General Settings

Configure the port general settings for all RUCKUS Edge devices in this cluster. Any ports that have been added to a LAG in the previous section of this wizard will be grayed out in this section.
  1. Within each port sub-tab, configure the following details:
    • Description - Enter a short description to identify the port.
    • Port Type - Select the type of port from the drop-down list.
      Note: A maximum of two WAN interfaces are allowed.

    Port Type Configuration

    Port Type Use port as IP Settings
    WAN Not applicable: The WAN port type does not support access and core separation. WAN port type ports perform both roles at the same time and the following rules apply:
    • If any port is selected as WAN type, Access/Core separation options are not available to any port.
    • If either Port1 or Port2 are marked as Access port or Core port, WAN type is not available to any port.
    • Choose IP Assignment
      • DHCP: Automatically provides IP address with the host IP address.
      • Static/Manual: Enter the following:
        • IP Address
        • Subnet Mask
        • Gateway
    • Click the Use NAT Service toggle to enable the option and enter the following NAT IP Addresses Range:
      • Start
      • End
    LAN Applicable to SD-LAN services only. For more information refer to SD-LAN.

    Select the required checkboxes:

    • Core port
    • Access port
    Note: Only one port can be selected as Access and only one port can be selected as Core at a time, making these options unavailable to any other ports.

    Hover over the icon next to Access port and click See the compatibility requirements to check the Compatibility Requirement.

    • IP Address
    • Subnet Mask
    Cluster Not Applicable Choose IP Assignment
    • DHCP: Automatically provides IP address with the host IP address.
    • Static/Manual: Enter the following:
      • IP Address
      • Subnet Mask
    Note: Change the Port Type while configuring the other ports.
  2. Click Next.
    If configuring a single-node cluster, the Dual WAN Settings page is displayed. If configuring a two-node cluster, the Sub-interface Settings page is displayed.

Sub-interface Settings

Sub-interfaces aid the support of different VLANs/networks in the same port. To configure sub-interface settings for a RUCKUS Edge Cluster, perform the following steps.
Note: A Sub-interface cannot be configured correctly unless the underlying interface (Port Type) has been enabled in Port General Settings. Due to UI requirements, the underlying interface may require a placeholder IP Address and Subnet Mask configuration to satisfy mandatory input fields. This workaround is necessary even if the interface is not used for actual routing.
  1. From the Sub-interface Settings page, select the required port tab and click Add Sub-interface.
    The Add Sub-interface sidebar is displayed.

    Sub-interface Settings

  2. Configure the following details:
    • Port Type - Select the port type from the drop-down list.
    • IP Assignment Type - By default, the IP assignment type is DHCP, however, to manually configure the ports, select Static IP from the drop-down list and enter the IP Address and Subnet Mask.
    • Use port as: Select the required checkboxes. Options include Core port and Access port.

      Hover over the icon next to Access port and click See the compatibility requirements to check the Compatibility Requirement.

      If any port is selected as WAN, Access port, or Core port in the previous sections, these options will not be available to the sub-interfaces. For more information refer to Software Defined Local Area Network.

    • VLAN: Enter a VLAN ID. Allowed values are 1 through 4094.
  3. After entering all the details in the respective fields, click Add.
    The sub-interface settings are displayed on the screen.
  4. Repeat to configure other sub-interfaces.
    Note: In the scenario of a Personal Identity Network (PIN), each sub-interface should have static routes to reach the IP address of the loopback interface of the Distribution Switch from the RUCKUS Edge and if using an external DHCP server then another route to reach the external DHCP server.
  5. Click Next.
    The Dual WAN Settings page is displayed.

Dual WAN Settings

Note: The Dual WAN Settings wizard page applies only to single-node clusters.
Note: This section is available only when setting two WAN ports in the Port General Settings section.
In a dual-WAN configuration, one link is designated as active while the other serves as a backup. By default, the Dual-WAN Mode is set as Active / Backup mode and this setting cannot be changed. The WAN Links Management section lists the Port, Role, and the Link Health Monitoring options. The WAN link ports are listed and configured individually. The first port listed is assigned as Active role, and the next port is assigned the Backup role. To change the role of these ports, double-click the icon beside the required port, then drag and drop it to the desired order.
  1. Click the Link Health Monitoring toggle to enable or disable link health monitoring. If disabled, then link failover cannot occur if the link fails.
    Note: Enabling the togggle supports failover. It does not support load balancing.

    Dual WAN Settings

  2. Click the icon to configure the link health monitoring settings for the port. The Link Health Monitoring sidebar is displayed.
  3. Configure the following for both ports:
    • Protocol: The ICMP (Ping) option is selected by default.
    • Target IP Addresses: Click Add Target and enter the destination IP address. A maximum of three IP addresses can be added.
    • Failure Condition: Choose one of the following conditions:
      • All targets were unreachable: When all targets fail. This is a default option.
      • One or more of the targets were unreachable: When some, but not all, of the targets fail.
    • Check Interval: Enter the time interval, in seconds, for performing failover checks. Default value: 3 seconds.
    • Mark link as DOWN after: Enter the number of retries before confirming failure. Range: 2-10; default value: 3.
    • Mark link as UP after: Enter the number of retries before confirming link restoration. Range: 2-10; default value: 3.
  4. Click Save to apply the failover configuration.
  5. Click Next.
    The Cluster Virtual IP page is displayed.

Cluster Virtual IP

The Cluster Virtual IP is a shared IP address that floats between nodes in the Edge cluster. It acts as the primary point of contact for external devices—such as APs, switches, or the controller—ensuring seamless communication even if one node fails. Configure the virtual IP interface and the failover settings for all RUCKUS Edge devices in this cluster.
  1. Click Select Interface.
    The Select Interfaces sidebar is displayed.
  2. Select the interface from the Select Port drop-down.
  3. Click OK.
    The Node Name, Interface, and IP Subnet are added.
  4. For Virtual IP Address, enter the virtual IP address for the RUCKUS Edge cluster.
  5. For Failover Settings, slide the marker on the HA Timeout timeline bar to adjust the amount of time allowed to elapse before triggering a failover.
    Note: An HA failover time of 6 seconds or longer is recommended for RUCKUS Edge use-cases. A timer set to less than this is very aggressive and could potentially cause VRRP issues in some networks. HA timeout refers to the time period within which a node must receive a periodic heartbeat signal from the active node. If the timer expires prior to receiving a heartbeat signal, then the system initiates the failover process to select the next active node and maintain system functionality.
  6. Click Next.
    The Summary page is displayed.
  7. Review the configuration and click one of the following:
    • Apply & Continue to proceed to the Cluster Interface Settings configuration.
    • Apply & Finish to complete the LAG, Port, Sub-interface & Virtual IP Settings configuration without proceeding to the Cluster Interface Settings configuration.
    From the cluster details page, you can check the Dual-WAN statistics.

    Dual-WAN Statistics