Troubleshooting
Here are some useful commands for troubleshooting a WAP. For me, the
problems usually revolve around association. The command show dot11 associations is a great tool. If you
have Cisco devices associated, it will even show you what they are:
Cisco-WAP#sho dot11 associations
802.11 Client Stations on Dot11Radio0:
SSID [Coolness] :
MAC Address IP address Device Name Parent State
0014.a524.5b7a 192.168.1.129 ccx-client hp-laptop self Assoc
001d.a231.6568 192.168.1.135 CP-7921 SEP001DA2316568 self Assoc
001e.a98b.0018 192.168.1.120 unknown - self Assoc
7c6d.62a4.6aad 192.168.1.110 unknown - self AssocKeeping the monitor session active with the terminal monitor command
is a must when troubleshooting association problems. This will ensure that
console message are sent to your terminal session when you’re using Telnet
or SSH to connect to the WAP. Here is the console output that resulted
from a wireless client losing power:
*Mar 1 00:56:54.671: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0025.0046.3f26 Reason: Sending station has left the BSS
Here is the resulting console message after power was restored:
*Mar 1 00:58:25.607: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 0025.0046.3f26 Associated KEY_MGMT[NONE]
These debug commands can be very helpful when you are troubleshooting wireless authentication:
debug dot11 aaa authenticator process debug dot11 aaa authenticator state-machine
If WPA or WPA2 Enterprise is enabled and RADIUS is involved, debugging ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access