Which two actions would you use to begin to troubleshoot an access point that fails to join a wireless LAN controller successfully?

Although most debugging is done on the controller, the unified WLAN solution also allows you to run specific debug and show commands on an AP. You can achieve this in two ways:

■ Accessing the AP via the console and executing the debug/show commands like you used to do on every IOS device.

■ Executing the show/debug commands from the controller using the AP remote-debug feature.

The first method is the one you are used to from IOS devices, although it is not always possible to use this method. That is because the console port from APs is not always physically cabled, and APs are often mounted at places based on a good RF coverage rather than comfortable console access.

To execute an AP show/debug command via the controller console, you first need to enable remote debugging on the AP. The following commands needs to be executed using debug ap Cisco_AP. After this, you can execute every IOS command using debug ap command command Cisco_AP syntax. Example A-1 shows how to display the contents of logging buffers of the AP with the name SE.AP-01-1240 using the remote debugs on the controller CLI. Example A-2 shows how to enable CAPWAP event debugs on the AP with the name SE.AP-01-1240 using the remote debugs on the controller CLI.