Examkin

Question

Difficulty: Very hardWireless LAN Client Connectivity Configuration via WLC GUI

A network engineer is tasked with deploying a new WPA2-Enterprise wireless network on a Cisco Wireless LAN Controller (WLC) using the web GUI. The WLAN must enforce 802.1X authentication via an external RADIUS server and support dynamic VLAN assignment using AAA override. What is the correct chronological sequence of steps to configure this WLAN on the WLC GUI from initial creation to feature enablement?

  1. 1Navigate to WLANs > WLANs, select 'Create New' from the drop-down menu, click 'Go', and define the Profile Name and SSID broadcast parameters.
  2. 2Access the WLANs > Edit page and under the General tab, map the WLAN to the appropriate base interface/interface group and select the 'Status' checkbox to enable it.
  3. 3Navigate to the Security > Layer 2 tab, select WPA+WPA2 L2 Security, enable WPA2 Policy with AES Encryption, and set Authentication Key Management to 802.1X.
  4. 4Navigate to the Security > AAA Servers tab and select the active RADIUS server under the Server 1 drop-down menu for Authentication Servers.
  5. 5Navigate to the Advanced tab and check the 'Allow AAA Override' checkbox to allow the RADIUS server to dynamically assign VLAN IDs to authenticated clients.

Answer

The correct sequence for configuring a WPA2-Enterprise WLAN with AAA Override on a Cisco WLC GUI is: 1) Create New WLAN (define Profile Name/SSID), 2) Set Interface and Enable Status under General tab, 3) Set WPA2-AES and 802.1X under Security > Layer 2 tab, 4) Select RADIUS Server under Security > AAA Servers tab, and 5) Enable Allow AAA Override under Advanced tab.
The correct procedural order follows standard Cisco WLC administration logic: First, create the WLAN instance with its Profile Name and SSID. Next, configure fundamental interface mapping and admin status on the General tab. Then, configure Layer 2 security for WPA2-Enterprise (802.1X AKM) on the Security > Layer 2 tab. Fourth, link the global RADIUS server under the Security > AAA Servers tab. Finally, navigate to the Advanced tab to enable 'Allow AAA Override' for dynamic VLAN steering.

Step-by-Step Solution

1
Initiate WLAN creation in WLC GUI
WLAN ID is allocated and initial Profile Name and SSID parameters are bound to the controller database.
You cannot configure specific WLAN sub-tabs until the WLAN instance is created via WLANs > Create New.
2
Configure General tab settings
The WLAN is associated with a distribution interface/interface group and marked administratively enabled.
Binding to an interface provides network pathing for client traffic.
3
Configure Layer 2 Security parameters
Layer 2 security policy is set to WPA2 with AES cipher and 802.1X key management.
Specifying 802.1X key management is a prerequisite for utilizing RADIUS EAP-based client authentication.
4
Bind RADIUS Server under AAA Servers tab
The WLAN targets the specific external RADIUS server for client EAP authentication transactions.
Without selecting an active RADIUS server under AAA Servers, 802.1X authentication requests will fail.
5
Enable AAA Override on Advanced tab
The controller honors RADIUS-returned VLAN attributes (IETF 64, 65, 81) to override the default WLAN interface assignment per user.
AAA Override functionality is disabled by default and resides specifically under the WLAN Advanced settings tab.

Key Concept

WLC GUI WLAN Configuration Workflow and Feature Navigation
Estimated Time:2m 30s
Rate this question

Topics

Wireless LAN Client Connectivity Configuration via WLC GUI

More questions from this topic