Software Defined Local Area Network

Software Defined Local Area Network (SD-LAN) is a service provided on RUCKUS One that is implemented on RUCKUS Edge devices.

Overview

The SD-LAN service provides centralized forwarding for RUCKUS access points (APs), enabling the APs to tunnel User Equipment (UE) traffic to an Edge device. All intermediate network hops are hidden from the end user’s traffic.

The SD-LAN service works as follows:

  • A Generic Protocol Extension for Virtual Extensible LAN (VxLAN-GPE) tunnel is established between the access point (AP) and the Edge device to facilitate the forwarding of UE traffic.
  • The AP associates the VLAN with the corresponding Virtual Network Identifier (VNI) (both having the same ID). For example, VLAN 10 maps to VNI 10, and vice-versa.
  • Layer 2 (L2) bridging allows UE traffic to be forwarded based upon the chosen Forwarding Destination. It can be bridged to DC network over core port or can be forwarded to L2GRE Tunnel.

SD-LAN also provides the capability to forward Captive Portal guest WLAN traffic between a Data Center (DC) Edge and an Edge device located in the DMZ portion of network. In the context of Wi-Fi networks, the DMZ is a logical network segment that adds an extra layer of security for the Local Area Network (LAN) by providing a safe zone, separating the LAN from untrusted networks (such as public internet).

SD-LAN service Functionality

  • Centralized Forwarding: SD-LAN provides centralized forwarding for RUCKUS APs, allowing for efficient management and control of network traffic.
  • VxLAN Tunneling: Supports Virtual Extensible LAN (VxLAN) tunnels between APs and RUCKUS Edge devices to facilitate the forwarding of UE traffic.
  • Guest Traffic Management: Enables the forwarding of guest WLAN traffic from the Data Center RUCKUS Edge to the RUCKUS Edge device located in the DMZ, enhancing security and isolation.
  • Layer 2 (L2) Bridging: Allows UE traffic to be forwarded into the core network, supporting seamless integration of wired and wireless networks.
  • Upstream L2GRE Tunneling: In Active-Active Cluster deployments, L2GRE tunnels are supported between the DC Edge device and upstream devices to facilitate the forwarding of UE traffic to the Core network.
  • Access-Core Separation: A network design centered on the RUCKUS Edge cluster, decoupling the Access layer (where APs connect) from the Core layer (where upstream services reside). Decoupling is achieved using an SD-LAN, a VxLAN-GPE tunnel from APs to the Edge cluster, L2GRE tunnel and DMZ tunnel from the Edge cluster to upstream devices. The two-leg deployment clearly defines the role of each port:
    • Core port: Connects to the service provider or upstream network via an L2GRE tunnel. The uplink port is responsible for forwarding UE traffic to the upstream network after VxLAN-GPE tunnel termination.
    • Access port: Connects to the local LAN or client devices. This port terminates VxLAN-GPE tunnels from RUCKUS APs and serves as the default gateway for the APs. The Access port also serves as a route to reach RUCKUS One and is used for management access.

    RUCKUS Edge clusters support enabling Core and Access in both Active-Active and Active-Standby deployments. In an Active-Active cluster, interfaces can be configured as either tagged or untagged for both Access and Core roles. In contrast, the Active-Standby cluster supports only untagged interfaces for Access and Core port configuration.

  • NAT-Traversal: NAT allows multiple devices on a private network to share a single public IP address. While it works well for outgoing connections, it typically blocks incoming connections unless explicitly configured to allow them. Enabling NAT-T support for Generic Protocol Extension for Virtual Extensible LAN (VxLAN-GPE) tunnels addresses deployment scenarios where VxLAN-GPE traffic between RUCKUS devices must traverse a NAT router, ensuring seamless tunnel establishment and communication.

Requirements

Ensure the following requirements are met before configuring the SD-LAN service:

  • A venue is configured with APs and a Wi-Fi network.
  • APs are running firmware version 7.x or later.

Considerations

This feature has no special considerations pertaining to feature enablement or usage.

Limitations

The SD-LAN service has the following limitations:

  • Network types supported:
    • Traffic tunneling between an AP and a Data Center Edge device: Supports all types of WLANs.
    • Traffic tunneling between a Data Center Edge device and a DMZ Edge device: Supports Captive Portal WLANs only.
  • Captive Portal WLAN support:
    • Captive portal terminating to Data Center Edge support: Supports SSID-VLAN and VLAN pooling.
    • Captive portal terminating to DMZ Edge support (redirected through Data Center Edge): Supports only SSID-VLAN.
  • Tunnelling support:
    • Is not available for RUCKUS switches.
    • Tunnelling is supported only for RUCKUS AP wireless clients and not AP wired ports.
    • The Edge can use either L2GRE or DMZ as the tunnel destination, but not both simultaneously.
  • Path MTU Discovery (PMTUD) is not supported for tunnels between two Edge devices. PMTU should be manually configured for these tunnels.
  • VNI-1 forwarding is not supported for DC or DMZ peer destinations.
  • VLAN-1 is supported only when traffic is forwarded via an L2GRE tunnel.
  • Only one Core port and one Access port can be configured per Edge device.
  • All the Edge devices in the cluster must have both a Core port and an Access port configured to enable SD-LAN services.
  • Ensure VLAN uniqueness across WLANs with distinct forwarding destinations: The RUCKUS Edge device performs Layer 2 forwarding on a per-VLAN basis. For each VLAN, it creates a single bridge domain and associates it with one forwarding path.
    • Multiple WLANs can share the same VLAN ID only when they use the same forwarding destination, such as the same L2GRE peer, core or bridge path, or peer Edge path.
    • Multiple WLANs must not share the same VLAN ID if those WLANs use different forwarding destinations.

    If multiple WLANs share a VLAN but use different forwarding destinations, the system behavior becomes undefined. The first traffic flow detected for that VLAN typically determines the forwarding path, which can cause the Edge device to misforward or drop traffic from other WLANs.

  • The RUCKUS Edge device relies on accurate VLAN and forwarding-destination mappings.
    • Assign a unique VLAN to each WLAN that requires a different forwarding destination.
    • Verify WLAN-to-VLAN and WLAN-to-forwarding-destination mappings before enabling SD-LAN.
    • Do not use VLAN pooling for SSIDs that require different forwarding destinations.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

This feature has no prerequisites to feature enablement or usage.