Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

SD-Access and Wireless Integration

Control plane traffic is CAPWAP inside of VXLAN-GPO. Dataplane traffic can just ride VXLAN-GPO

Fabric design

FEW — Fabric Enabled wireless

The client mac is the EID.

SD access wireless

  • CAPWAP the control plane traffic
  • VXLAN-GPO the data plane, tunnel it to an edge node.
  • APs act as VTEPS.

Fabric APs

  • Go into the AP subnet, in the overlay
    • Go in the INFRA_VN
  • Use CAPWAP for control-plane only
  • Converts wireless data into VXLAN-GPO, encoding the VNI, and SGT
  • Join the WLC in Local mode
  • 20ms of latency, max

Nonfabric design

  • AKA OTT (Over The Top)
  • Rides VXLAN, not VXLAN aware.
  • Good for existing networks, where the wireless is already working and disruption would be costly.

CUWN wireless OTT

  • CUWN: Cisco Unified Wireless Network

Everything is CAPWAP inside of VXLAN-GPO. Central switching.

FlexConnect OTT

  • CAPWAP Tunnel the control traffic.
  • Dump the traffic at the local switch.

Mixed mode OTT

  • Some APs tunnel all their traffic back with CAPWAP.

WLC

  • Subnet for the WLC goes into the underlay network, via an IGP.

IPAM integraiton

  • Infoblox
  • Bluecat

References

Integrating IP Address Management with Catalyst Center via REST - Cisco Catalyst Center API 3.1.3 - Cisco DevNet

SD-Access Wireless Design and Deployment Guide - Cisco DNA center 2.1.1

LISP VXLAN Fabric Configuration Guide, Cisco IOS XE Cupertino 17.9.x (Catalyst 9000 Series Switches) - Configuring Wireless Support in a LISP VXLAN Fabric Cisco Catalyst 9300 Series Switches - Cisco

Cisco SD-Access Best Practices

Last Modified • Saturday, June 27, 2026. 12:39 am UTC+00:00 • Commit: f69a731