Cisco Cisco 2106 Wireless LAN Controller Manual Técnico
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Background Information
In controller version 4.2.61.0, the controller now keeps track of all APs that send it a discovery request and
which APs it sends a discovery reply to. It also tracks APs that try to join the controller and whether or not
they are successful. There are 2 new CLI (console or SSH) commands on the controller to help troubleshoot
why an AP will fail to join the controller:
which APs it sends a discovery reply to. It also tracks APs that try to join the controller and whether or not
they are successful. There are 2 new CLI (console or SSH) commands on the controller to help troubleshoot
why an AP will fail to join the controller:
Show ap join stats summary [all | AP_Mac_Address]
Show ap join stats detailed AP_Mac_Address
Troubleshooting Algorithm
Use the show ap join stats summary all command to see which APs do not join the controller. The AP is
inserted into the show ap join stats list as soon as the controller receives a discovery request.
inserted into the show ap join stats list as soon as the controller receives a discovery request.
Note: The controller never removes the AP from the show ap join stats list until the controller is rebooted. In
some cases, the failed APs have tried to join for more than a day or are completely offline. Use the show ap
join stats detail command to find out when the last discovery request and last join request were sent from the
AP to determine if the AP has lost connectivity to the controller or has possibly moved to another controller.
some cases, the failed APs have tried to join for more than a day or are completely offline. Use the show ap
join stats detail command to find out when the last discovery request and last join request were sent from the
AP to determine if the AP has lost connectivity to the controller or has possibly moved to another controller.
The output gives the total number of APs from which the controller has received discovery requests and then
lists whether or not those APs are currently joined to the controller.
lists whether or not those APs are currently joined to the controller.
(Cisco Controller) >show ap join stats summary all
Number of APs................................. 3
00:0b:85:1b:7c:b0............................. Joined
00:12:44:bb:25:d0............................. Joined
00:13:19:31:9c:e0............................. Not joined
Once you have the MAC address of the AP that is not joined, use the show ap join stats summary <mac
addr> to discovery the last join and reason for failure.
addr> to discovery the last join and reason for failure.
(Cisco Controller) >show ap join stats summary 00:14:f2:63:12:50
Is the AP currently connected to controller............. Yes
Time at which the AP joined this controller last time...
Jan 24 12:21:32.414
Type of error that occurred last........................
AP got or has been disconnected
Reason for error that occurred last.....................
Timed out while waiting for ECHO response from the AP
Time at which the last join error occurred..............
Jan 24 12:21:14.751
If you want detailed information on discovery requests, join requests, and configuration requests, use the
command show ap join stats detail <mac−address> . This command also indicates whether or not the
controller sees only a discovery request from the AP but does not see a join request.
command show ap join stats detail <mac−address> . This command also indicates whether or not the
controller sees only a discovery request from the AP but does not see a join request.
(Cisco Controller) >show ap join stats detail 00:14:f2:63:12:50
Discovery phase statistics
− Discovery requests received........................... 2
− Successful discovery responses sent................... 2
− Unsuccessful discovery request processing............. 0
− Reason for last unsuccessful discovery attempt........