Edge Delegation with IPSec

Feature Overview

IPSec encryption enhances VxLAN‑GPE tunnels between APs and RUCKUS Edge devices by securing data transported across untrusted networks.

Within an Edge Delegation environment, IPSec is configured and managed exclusively from the MSP tenant using Templates, while EC tenants receive read‑only, delegated versions of these configurations.

To ensure all IPSec and tunnel configurations remain centrally controlled by the MSP and consistently propagated to EC tenants, the MSP workflow is as follows:

  1. Create the IPSec Profile Template: Define the PSK, IKE/ESP proposals, DPD settings, NAT‑T behavior, timers, and any advanced parameters.
  2. Update the Tunnel Profile Template: Enable Tunnel Encryption and select the IPSec Profile; adjust MTU and keepalive values as needed.
  3. Apply and (optionally) Enforce: Apply the templates to EC tenants, and use the Show Drifts and Sync functions after any MSP‑side updates.

Requirements

This feature has the following requirements:

  • Tunnel Type: VxLAN-GPE (AP to Edge). IPSec is not available for L2GRE.
  • Template Flow: Create an IPSec Profile Template (MSP), reference it in a VxLAN-GPE Tunnel Profile Template, and apply to EC tenants.
  • Delegation Model: MSP retains ownership; EC shows read-only Tunnel Profile and IPSec details.

Limitations

This feature includes the following limitations:

  • Only IPv4 is supported.
  • IPSec tunneling is not supported; optional AES‑128/256‑CBC payload encryption is available.
  • NAT‑T functionality is limited to the AP side, as Edge devices cannot operate when placed behind a NAT.
  • IEEE 802.1ad Q‑in‑Q is not supported.

Considerations

RUCKUS suggests the following best practices regarding this feature:

  • Disruptive Change: Enabling or disabling encryption forces all tunnels to tear down and re‑establish; perform this operation during a maintenance window.
  • NAT‑T and DPD: Turning on encryption automatically enables NAT‑T and DPD. When encryption is later disabled, NAT‑T remains enabled.
  • Single IPSec Profile: Only one IPSec Profile can be associated with each Tunnel Profile; multiple profiles per tunnel are not supported.

Best Practices

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

  • Manage IPSec strictly through MSP Templates, and use Enforcement to prevent configuration drift.
  • Reconcile any differences by use the Show Drifts and Sync functions after updating the template.

Prerequisites

This feature has no prerequisites to feature enablement or usage.