Sometimes you have an AP that for whatever reason doesn’t want to join the WLC. To solve this, there are three things you could check:
- The WLC logfile (management > logs).
- The console of the access point.
- The console of the WLC.
You don’t always see what you need on the access point console or the wireless controller logfile. The best way to solve these issues is to enable a debug:
(Cisco Controller) >Debug capwap errors enable
This will output the following items:
(Cisco Controller) >show debug MAC debugging .............................. disabled Debug Flags Enabled: capwap error enabled. capwap critical enabled. lwapp errors enabled.
Once you connect the AP, it will join the WLC, and you’ll see the following debug:
(Cisco Controller) >*spamApTask3: Feb 05 09:19:22.696: 00:22:90:92:c2:80 Failed to parse CAPWAP packet from 10.56.60.165:2321 *spamApTask2: Feb 05 09:20:58.000: 00:22:90:92:c2:80 Refusing Discovery Request from AP 00:22:90:92:c2:80 - limit for maximum APs supported 5 reached *spamApTask2: Feb 05 09:20:58.000: 00:22:90:92:c2:80 State machine handler: Failed to process msg type = 1 state = 0 from 10.56.60.165:2320
In this example, the debug message is pretty clear…we hit the license limit of the WLC. Whatever the reason, this debug will produce a useful message that gives you more insight into what to look for.
To disable all debugging:
(Cisco Controller) >debug disable-all
Hopefully, this is helpful to you to debug some of your troublesome access points!