Access points, wireless controllers, and WLAN configuration

Wireless management architectures

An access point (AP) provides the radio connection. A wireless LAN controller (WLC) manages supported APs and wireless policies. Autonomous APs manage themselves; controller-based designs coordinate APs centrally. Cloud-managed describes where management is hosted and does not, by itself, tell you where every user packet travels.

In controller deployments, local AP mode and FlexConnect have different forwarding options. Monitor mode observes radio activity rather than providing the ordinary client service. The wired switch link, PoE budget, AP registration and VLAN path matter as much as the SSID.

WPA2-Personal WLAN lab configuration

1. In your chosen simulator, place a supported controller, AP, switch, router/DHCP service and laptop. Check that the AP can discover and join the controller using the platform’s setup process.
2. Create a client subnet, such as 192.168.30.0/24, with gateway .1 and a DHCP pool excluding infrastructure addresses.
3. In the controller GUI, create WLAN name Training and SSID Training-WiFi. Map it to the intended client interface or VLAN.
4. Select WPA2-Personal/PSK with AES, set a lab-only passphrase and enable the WLAN. Menu names depend on the controller and software.
5. Join the laptop with matching settings. Check its lease, ping its gateway and test an allowed service.

Use Cisco’s linked legacy-controller example for its specific GUI, not as an exact menu map for every controller. The exercise is a build checklist, not a claim of a tested Packet Tracer file. The practice-tools page also has a clearly labelled configuration reasoning exercise.