Quiz Entry - updated: 2026.07.14
What are the steps to configure a VLAN interface on the WLC for an Enterprise WLAN, and why is this needed?
Enterprise WLANs (Wireless Local Area Networks) need a separate VLAN (Virtual Local Area Network) interface so that wireless clients land on their own subnet with their own DHCP (Dynamic Host Configuration Protocol) scope, isolated from management traffic. Create the interface, assign VLAN ID, IP (Internet Protocol) address, and DHCP server address.
Why a separate VLAN interface is needed:
- The management interface is for WLC (Wireless LAN Controller) administration — you don't want wireless users on the management VLAN
- Each WLAN should map to its own VLAN for segmentation and security
- Different WLANs (e.g., Corporate, Guest, IoT) can map to different VLANs with different policies
VLAN interface configuration steps on WLC:
| Step | Action |
|---|---|
| 1 | Navigate to Controller → Interfaces → New |
| 2 | Enter the interface name (e.g., "vlan5") and VLAN ID (e.g., 5) |
| 3 | Configure the port and IP address/subnet for this interface |
| 4 | Configure the DHCP server address (where clients in this VLAN get their IPs) |
| 5 | Click Apply to confirm |
| 6 | Verify the new interface appears in the Interfaces list |
Then configure a DHCP scope (if the WLC acts as DHCP server):
- Navigate to Controller → Internal DHCP Server → DHCP Scope → New
- Configure: pool name, address range (e.g., 192.168.200.240-249), default router, DNS (Domain Name System)
- Enable the scope and Apply
Finally, map the WLAN to this interface:
- When creating/editing the WLAN → General tab → set Interface/Interface Group to your new VLAN interface (e.g., "vlan5")