Week 4 · Lesson 9

Wireless Architectures and the WLC

One access point is easy. Two hundred of them, spread across a campus, all sharing one SSID and one security policy, are not. This final lesson of Week 4 shows how wireless is architected: from a lone self-managed access point, to a fleet of lightweight APs steered by a central Wireless LAN Controller, to management that lives in the cloud. It closes with the AP modes and deployment choices that make a wireless design actually work.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

Why wireless architecture matters

A wireless network is not just radios; it is a system. Each access point must serve clients on the right SSID, apply the right security, hand them onto a VLAN, and cooperate with its neighbours so a moving client can roam without dropping its session. Doing that consistently is a management problem as much as a radio problem, and the way you solve it defines your wireless architecture.

There are two poles. In the autonomous model, every access point is a small, self-sufficient device you configure one by one. In the controller-based model, the access points are deliberately made “lightweight” — dumb about policy, smart only about radio — and a central Wireless LAN Controller (WLC) holds the configuration, security, and RF intelligence for the whole fleet. A third, newer option moves that central brain into the cloud. The trend across the industry is unmistakable: from standalone, to on-premises controller, to cloud-managed.

The three architectures · select one

Part 2

Autonomous access points

An autonomous access point (sometimes called standalone) runs the full wireless stack itself. It holds its own configuration, advertises its own SSID, authenticates its own clients, and bridges them to the wired LAN. You manage it by console, Telnet/SSH, or a web interface, and you repeat that work for every single AP.

Autonomous APs are simple and robust — there is no controller to fail and no tunnel to maintain — which makes them fine for a home, a small office, or a branch with one or two APs. They scale badly: changing the Wi-Fi password means touching every device, there is no central view of the RF environment, and roaming and security consistency are hard to guarantee. These are exactly the pains the controller-based model was invented to remove.

Strengths
No controller to fail, no CAPWAP tunnel to maintain, no licence or platform to buy. The AP keeps working on its own if the management network goes down.
Weaknesses
Every change is repeated on every device. No central view of the RF environment, inconsistent roaming, and security drift as one AP is missed during an update.
Part 3

Controller-based WLANs and the WLC

In a controller-based deployment the access points are lightweight (Cisco calls them LWAPPs, or lightweight access points). They no longer hold the network configuration. Instead they join a WLC, which becomes the single point of configuration, monitoring, security policy, and RF management. Configure one WLAN profile on the WLC and every joined AP offers it.

The WLC also presents several logical interfaces you should know by name: the management interface (for administering the controller, usually on a management VLAN), the dynamic interfaces (one per client VLAN/WLAN), the AP-manager interface (handling AP joins), the virtual interface (used for mobility and DHCP relay), and on some models a service-port for out-of-band management. A wireless client’s traffic typically maps from an SSID to a WLAN on the WLC and then to a dynamic interface — and therefore to a VLAN.

Cloud-managed wireless is the same idea with the controller relocated: the management and policy engine lives in a vendor cloud portal rather than in a box on site. Between the two sits Cisco’s own management platform, Catalyst Center (formerly DNA Center), which can configure and monitor both wired and wireless as a single fabric.

Exam tip. The WLC is the single point of configuration, monitoring, security policy, and RF management for the whole fleet. Remember its logical interfaces by role: management (administer the controller), dynamic (one per client VLAN or WLAN), AP-manager (AP joins), virtual (mobility and DHCP relay), and service-port (out-of-band management on some models).
Part 4

Split-MAC: which job lives where

To make a lightweight AP useful, the 802.11 MAC functions are split between the AP and the WLC — hence the name split-MAC. The guiding rule is simple: real-time radio work stays at the edge; management and policy work moves to the controller.

FunctionLightweight APWLC
Beacons and probe responsesYes — time-criticalNo
ACKs, retransmissions, frame timingYes — real-time 802.11No
Authentication, association, roamingNoYes — central policy
Security policy and key managementNoYes
RF management, transmit power, channelsAssistsYes — RRM decides
Client traffic to the wired LANTunnels it (local mode)Bridges it to the correct VLAN
Definition — split-MAC. The division of 802.11 MAC responsibilities between a lightweight AP and a WLC: the AP keeps the real-time radio functions (beacons, ACKs, retransmissions), while the WLC owns the management functions (authentication, association, roaming, security, and RF policy). The two halves coordinate over a CAPWAP tunnel.
AP 1 local AP 2 FlexConnect AP 3 monitor Access switch (wired LAN) WLC CAPWAP control UDP 5246 · data UDP 5247 (DTLS)

Lightweight APs carry no network configuration. They discover and join the WLC, then tunnel both their control traffic and (in local mode) their client data through it using CAPWAP over the wired LAN. The WLC applies authentication, roaming, security, and RF policy for every AP at once.

Which side owns this function? · select a function

Part 5

CAPWAP: discovery and join

The protocol that carries a lightweight AP’s traffic to the WLC is CAPWAP — Control And Provisioning of Wireless Access Points (RFC 5415/5416). It is the modern successor to the older Cisco LWAPP, and its ports are exam facts:

CAPWAP tunnelTransportPurpose
ControlUDP 5246AP join, configuration, and management messages; encrypted with DTLS.
DataUDP 5247Client traffic tunnelled to the WLC (optional DTLS encryption).

Before any of this, the AP must find the controller. A booting AP gets an IP address from DHCP, then performs CAPWAP discovery using, in order of preference:

Once it finds the WLC, the AP and controller exchange discovery and join messages, establish DTLS security on the control channel, and the WLC downloads configuration. The AP is then ready to serve clients.

Exam tip. Fix the ports in memory: CAPWAP control = UDP 5246, CAPWAP data = UDP 5247. If a question asks which protocol and port a lightweight AP uses to reach its controller, the answer is CAPWAP over UDP, control 5246 and data 5247 — not TCP, and not LWAPP (the legacy predecessor).
CAPWAP tunnels · select the tunnel

Part 6

Cloud-managed wireless

Cloud-managed wireless (for example Cisco Meraki) removes the on-premises controller entirely. Access points connect out to a vendor cloud dashboard where the administrator configures SSIDs, security, and RF settings, and where statistics and monitoring are aggregated. There is no local controller appliance to buy, license, or maintain, and the network is manageable from anywhere.

The trade-off is dependence on the cloud connection and on the vendor’s platform. For many distributed organisations — many small sites, few IT staff — that trade is worth it. The exam level insight is simply to recognise the three models side by side: autonomous (per-AP, no controller), controller-based (lightweight APs plus an on-premises WLC), and cloud-managed (lightweight APs plus a cloud dashboard).

Exam tip. The three architectures, in the order the industry adopted them: standalone/autonomous AP → controller-based (lightweight APs plus WLC) → cloud-managed. All three still exist in the field, and a scenario question may well tell you which one is in play.
Part 7

Access point modes

A Cisco lightweight AP can be placed in one of several modes, each giving the radio a different job. Know all six:

ModeWhat the AP does
LocalThe default mode. Serves clients on its WLANs and tunnels traffic to the WLC. While not busy it scans other channels for rogue APs.
FlexConnectFor branch offices. The AP can switch client traffic locally at the branch while staying controlled by a central WLC, and can keep serving clients if the WAN link to the controller fails.
MonitorDedicated to listening. Serves no clients; scans all channels for rogue access points and wireless attacks (IDS/IPS).
SnifferCaptures 802.11 frames on a chosen channel and forwards them to a packet analyser such as Wireshark, for deep protocol troubleshooting.
Bridge / MeshProvides wireless links between access points (mesh), including point-to-point bridging where cabling is impractical.
SE-connectSpectrum Expert Connect: passes raw RF spectrum data to a spectrum-analysis tool to find interference and non-Wi-Fi sources.
Note. The two modes most likely to appear in a scenario are local (serve clients, tunnel to the WLC) and FlexConnect (branch, local switching, survive WAN loss). If the question mentions “a branch office with a link back to headquarters”, FlexConnect is the answer.
AP modes · select a mode

Part 8

Deployment considerations and the bands recap

Deciding where and how to deploy APs is as important as choosing the architecture.

Bands and channels recap

Bring the week full circle. The radio bands decide range, throughput, and how much channel reuse you get:

BandCharacterChannel reuse
2.4 GHzBest range and wall penetration; most interferenceOnly 1, 6, 11 do not overlap
5 GHzMore throughput, less interference, shorter rangeMany non-overlapping channels
6 GHzCleanest, shortest range; enables Wi-Fi 6EThe most channels of all

The design lesson is that architecture and radio are one design. A controller gives you consistent channels and power across the fleet through its RF management, but the physics — range against throughput, and the 1/6/11 constraint in 2.4 GHz — still sets the floor.

Key terms. Autonomous AP — a standalone access point that holds its own configuration and serves clients without a controller. Lightweight AP — an access point that joins a WLC and relies on it for configuration, security, and RF policy. WLC — Wireless LAN Controller; centralises configuration, authentication, roaming, and RF management for a fleet of APs. Split-MAC — the division of 802.11 MAC work between the AP (real-time radio) and the WLC (management and policy). CAPWAP — Control And Provisioning of Wireless Access Points; tunnels AP traffic to the WLC on UDP 5246 (control) and UDP 5247 (data). FlexConnect — an AP mode for branches that can switch client traffic locally and survive a WAN outage. Cloud-managed wireless — a deployment where management lives in a vendor cloud dashboard rather than an on-premises controller.
Part 9 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Calhoun, P. et al. RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification (2009). rfc-editor.org/rfc/rfc5415.
  2. Calhoun, P. et al. RFC 5416: CAPWAP Protocol Binding for IEEE 802.11 (2009). rfc-editor.org/rfc/rfc5416.
  3. Cisco. Wireless LAN Controller Configuration Guide (AP modes, CAPWAP, split-MAC, WLC interfaces). cisco.com.
  4. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals — wireless architectures and AP modes. cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.