I use WLC 4400 with product version 126.96.36.199 that supports 25 LAP.
There are 14 AIR-LAP-1522-A-K9 that were installed and configured with controller. All of them are working fine. Recently we bought AIR-LAP-1524SB-A-K9.
I followed the same steps in configuring as for 1522, I add MAC to MAC filter, booted the 1524. LAP receives IP but it does not register on controller.
Here are logs from controller:
*Feb 21 20:02:13.851: %LWAPP-3-DECODE_ERR: spam_lrad.c:1663 Error decoding discovery request from AP 00:26:98:3a:50:00
*Feb 21 20:02:13.851: %LWAPP-3-DISC_OTAP_ERR: spam_lrad.c:6020 Ignoring OTAP discovery request from AP 00:26:98:3a:50:00, OTAP is disabled
Then I enabled OTAP.
*Feb 21 20:02:57.010: %CAPWAP-3-DECODE_ERR: capwap_ac_sm.c:1458 Error decoding discovery request from AP 00:26:98:3a:50:00
and nothing happened again.
Then I connected to LAP's console, and here what I get:
*Mar 1 00:23:38.151: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 1 00:23:38.151: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 1 00:23:38.151: %MESH-6-LINK_UPDOWN: Mesh station 0026.983a.50fc link Down
*Mar 1 00:24:01.399: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:24:03.387: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 1 00:24:03.387: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
*Mar 1 00:24:03.387: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 1 00:24:03.387: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Mar 1 00:24:03.387: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
*Mar 1 00:24:06.495: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:24:06.503: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:24:06.531: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:22:43.351: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Mar 1 00:22:43.351: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
*Mar 1 00:22:43.351: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Mar 1 00:22:43.351: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.5.5.101
*Mar 1 00:22:43.371: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
The reason why it's not working is because your WLC is running CAPWAP image while your AP is a Mesh AP. Fortunately, you can correct this by running the Mesh IOS.
If my post helps you in any way please don't hesitate to rate. Thank you very much.
I'm new to WLC based networks. So would you please give me detailed information on how can I change CAPWAP image to Mesh IOS. And don't forget that I have 14 AIR-LAP-1522-A-K9 working properly and these are Mesh APs too. May be it will be better to change IOS on 1524?
1522 has Cisco IOS Software, C1520 Software (C1520-K9W8-M), Version 12.4(18a)JA, RELEASE SOFTWARE (fc4)
Thanks in advance.
Go to the Cisco Download Centre (http://www.cisco.com/cisco/psn/web/download/index.html), go to Wireless, Wireless LAN Controllers, Standalone, 4400, choose anyone of the two and then choose Mesh Controller Software.
We installed 188.8.131.52M IOS. 1524SB AP gets IP address, WLC management interface ip address (option 43) from the DHCP server.
After that it starts sending CNTL DISCOVERY_REQUEST to management ip address of WLC and gets CNTL DISCOVERY_REPLY back
from WLC and this process keeps going. Registered 1522 APs send CNTL JOIN_REQUEST to AP-manager interface immediately after getting DISCOVERY_REPLY. This doesn't happen with 1524 AP.
Any help would be appreciated.
According to above link (Table 16) 1524 SB requires 6.0 or later.
Is it worth trying?
Sorry you had to go so long without a valid answer and had to resolve it yourself. I missed this thread.
5.2+ is Mesh capable Code and the 1520 Series can only do mesh. So there is nothing different to do for the AP/WLC.
Your problem, as you correctly diagnosed, had to do with the 1524-SB not being supported before 6.0.
It is kind of like trying to take an 1140 Series AP and join it to 4.2, it just won't happen.