Configuring Core, Access, and Cluster Interface Ports in the Cluster

When the Edge nodes in a cluster display a Needs Port Config status in the Node Status column, core, access, and cluster interface port configurations must be completed as the next step in the SD-LAN workflow.
You can choose to configure a Core or Access port using:
  • Untagged Ethernet Interface
  • LAG interface
  • Sub-interface
    • Based on untagged Ethernet interface
    • Based on LAG interface

Note: Core and Access ports can use different interface types. Valid combinations include:

  • Core: LAG interface — Access: untagged Ethernet interface

  • Core: sub-interface on a LAG — Access: untagged Ethernet interface

  • Core: untagged Ethernet interface — Access: LAG sub-interface

Core and access ports can be configured on any supported interface type and do not need to match.

In a single‑leg deployment, the same interface may be configured as both the core and access port. For each Edge node in the cluster, only one access port, one core port, and one cluster interface are supported. The default gateway must be reachable via the access port, while connectivity to the DC Core Router, DMZ Cluster, or L2GRE tunnel endpoints is provided through the core port.

Configure static routes on each Edge device to ensure that traffic destined for the DMZ Cluster network and L2GRE tunnel endpoints is routed through the core port.

The cluster interfaces for all Edge nodes in a cluster must be the same interface type, either a physical port or a LAG.

Follow these steps to configure untagged Ethernet interfaces as core and access ports:
  1. From the RUCKUS One navigation bar, select Gateway > RUCKUS Edge.
    This displays a list of the RUCKUS Edge clusters and devices.
  2. When the cluster nodes display a Needs Port Config status, select the cluster and click Run Cluster & RUCKUS Edge Configuration Wizard.

    Node Status

  3. Select LAG, Port, Sub‑interface & HA Settings, and then click Next.

    Cluster Configuration Wizard

  4. From the Cluster & RUCKUS Edge Configuration Wizard, configure the core and access ports using one of the following options:
  5. After completing the cluster configuration, review the Summary page. This page displays a consolidated view of the cluster configuration based on the selected Access and Core port options. In addition to port configuration details, the Summary page also includes the configured HA settings and Fallback schedule. From the Summary page, review the configuration for the following options:
    • When untagged Ethernet interfaces are used as Core and Access ports.

      Summary Page of Untagged Ethernet Interfaces Option

    • When LAG interfaces are used as Core and Access ports.

      Summary Page of LAG Interfaces Option

    • When sub-interfaces are used as Core and Access ports.

      Summary Page of Sub-Interfaces Option

    • When LAG interface is used as Core port and Sub-interfaces are used as Access port.

      Summary Page Showing LAG as Core Port and Sub‑Interface as Access Port Option

    • In a one-leg deployment where Core port and Access port are on the same interface.

      Summary Page in a One-Leg Deployment Option

  6. Click one of the following to confirm the configuration:
    • Apply & Continue to proceed to the Cluster Interface Settings configuration.
    • Apply & Finish to complete the LAG, Port, Sub-interface & HA Settings configuration without proceeding to the Cluster Interface Settings configuration.