converted 1140 AP can't join the WLC 5508

18091988n · ‎12-21-2011

Hello! Please, help me to sort my problem out.

We have bought autonomous APs AIR-AP1141N-E-K9 and converted them to the lightweight mode, but they cannot join the WLC 5508. The errors are below. There were NO problems with the LAPs that were bought before, together with the WLC.

AP's IP: 172.22.90.27 IOS version 12.4

WLC's IP: 172.22.90.20 IOS version 6.0.188.0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This Discussion has been converted into document:- https://supportforums.cisco.com/docs/DOC-23054

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

logs from the AP:

Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

*Oct 13 21:37:06.044: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Oct 13 21:37:06.045: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Oct 13 21:37:06.046: bsnInitRcbSlot: slot 1 has NO radio

*Oct 13 21:37:06.056: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a

dministratively down

*Oct 13 21:37:06.066: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r

eset

*Oct 13 21:37:06.098: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Oct 13 21:37:15.060: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLL

ER

*Oct 13 21:37:24.060: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL

LER

*Oct 13 21:37:34.060: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 13 21:38:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i

p: 172.22.90.20 peer_port: 5246

*Oct 13 21:38:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Oct 13 21:38:34.822: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully

peer_ip: 172.22.90.20 peer_port: 5246

*Oct 13 21:38:34.823: %CAPWAP-5-SENDJOIN: sending Join Request to 172.22.90.20

*Oct 13 21:38:34.823: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Contr

ol Message from 172.22.90.20

*Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.

*Oct 13 21:38:34.825: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag

e from controller

*Oct 13 21:38:39.823: %CAPWAP-5-SENDJOIN: sending Join Request to 172.22.90.20

*Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Contr

ol Message from 172.22.90.20

*Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.

*Oct 13 21:38:39.823: %CAPWAP-3-ERRORLOG: Failed to handle capwap control messag

e from controller

*Oct 13 21:38:39.824: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap p

acket from 172.22.90.20

*Oct 13 21:39:33.999: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1

72.22.90.20:5246

*Oct 13 21:39:34.000: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 13 21:38:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i

p: 172.22.90.20 peer_port: 5246

*Oct 13 21:38:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Oct 13 21:38:34.001: %DTLS-5-PEER_DISCONNECT: Peer 172.22.90.20 has closed conn

ection.

*Oct 13 21:38:34.001: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1

72.22.90.20:5246

*Oct 13 21:38:34.001: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination

*Oct 13 21:38:34.125: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is

not established.

logs from the WLC:

debug capwap events enable

*Dec 21 15:02:06.244: 68:bc:0c:63:3d:a0 DTLS keys for Control Plane deleted successfully for AP 172.22.90.27

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 DTLS connection closed event receivedserver (172:22:90:20/5246) client (172:22:90:27/21077)

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Entry exists for AP (172:22:90:27/21077)

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 1

*Dec 21 15:02:06.246: 68:bc:0c:63:3d:a0 Deregister LWAPP event for AP 68:bc:0c:63:3d:a0 slot 1

Ble

*Dec 21 15:04:03.194: 68:bc:0c:63:3d:a0 capwap_ac_platform.c:1223 - Operation State 0 ===> 4

*Dec 21 15:04:03.194: 68:bc:0c:63:3d:a0 Register LWAPP event for AP 68:bc:0c:63:3d:a0 slot 0

*Dec 21 15:05:36.253: 68:bc:0c:63:3d:a0 Join Version: = 100711424

*Dec 21 15:05:36.253: 68:bc:0c:63:3d:a0 Join resp: CAPWAP Maximum Msg element len = 93

debug capwap errors enable

*Dec 21 16:16:51.879: 68:bc:0c:63:3d:a0 DTLS connection was closed

*Dec 21 16:17:09.940: 68:bc:0c:63:3d:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =5

debug capwap detail enable

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 CAPWAP Control Msg Received from 172.22.90.27:21078

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 packet received of length 281 from 172.22.90.27:21078

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Msg Type = 3 Capwap state = 5

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: Result Code message element len = 8

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 1. 47 0

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 2. 232 3

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 3. 6 0

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 4. 12 0

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: AC Descriptor message element len = 48

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 acName = Wi-Fi_Controller

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: AC Name message element len = 68

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: WTP Radio Information message element len = 77

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Join resp: CAPWAP Control IPV4 Address len = 87

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Sending encrypted packet to AP 172:22:90:27 (21078)

*Dec 21 16:21:49.961: 68:bc:0c:63:3d:a0 Releasing WTP

*Dec 21 16:24:12.212: 68:bc:0c:63:3d:a0 CAPWAP Control Msg Received from 172.22.90.27:21077

*Dec 21 16:24:12.212: 68:bc:0c:63:3d:a0 DTLS connection 0x167c8b20 closed by controller

*Dec 21 16:24:12.212: DTL Deleting AP 9 - 0.0.0.0

*Dec 21 16:24:12.214: CAPWAP DTLS connection closed msg

*Dec 21 16:24:12.216: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'mfpSendEventReport+168' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.216: Received SPAM_MFP_RADIO_DOWN message

*Dec 21 16:24:12.218: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'l2roamInit+560' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.220: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamCallbackInSpamContext+1224' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.222: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamSendBlackListTable+376' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.224: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'rrmIappSendChdPacket+2320' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.226: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'asTrackInitTask+19360' for AP 68:bc:0c:63:3d:a0(0)

*Dec 21 16:24:12.228: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'mfpSendEventReport+168' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.228: Received SPAM_MFP_RADIO_DOWN message

*Dec 21 16:24:12.230: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'l2roamInit+560' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.232: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamCallbackInSpamContext+1224' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.234: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'apfSpamSendBlackListTable+376' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.236: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'rrmIappSendChdPacket+2320' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.238: 68:bc:0c:63:3d:a0 Sending LWAPP Event DeReg to 'asTrackInitTask+19360' for AP 68:bc:0c:63:3d:a0(1)

*Dec 21 16:24:12.238: 68:bc:0c:63:3d:a0 Deleting and removing AP 68:bc:0c:63:3d:a0 from fast path

P.S. The time is set to the WLC with the NTP

P.P.S. Don't lookup at the time the logs were made - they were made not during the same day/time

Scott Fella · ‎12-21-2011

Have you tried to reinstall the rcv image?

-Scott
*** Please rate helpful posts ***

18091988n · ‎12-21-2011

tried that too, thanks! had few monthes of a headache because of a MAC beginning not with 00:

Stephen Rodriguez · ‎12-21-2011

can you rerun the debgs and capture for two of the AP's reboot cycles?

debug mac-address 68:bc:0c:63:3d:a0

debug capwap events enable

debug capwap errors enable

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

18091988n · ‎12-21-2011

I have solved this as soon as published my problem!!!

the answer is published here:

https://supportforums.cisco.com/thread/2004491

especially in the post of Matthew Fowler

Hi,

Please take a look at CSCte01087.

I see that your WLC is 10.0.13.5 and your AP is 10.0.13.28/24 so they are on the same subnet. I also see your AP MAC address does not begin with 00. This is why I believe it is relevant.

Please try the workaround or open a TAC case if you need a fix.

-Matt

 Symptom:
 An access point running 6.0.188.0 code may be unable to join a WLC5508.
 Messages similar to the following will be seen on the AP.
 
   %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
   %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message
   
 Conditions:
 At least one of the following conditions pertains:
 
 - The high order byte of the AP's MAC address is nonzero, and the AP is in
 the same subnet as the WLC5508's management (or AP manager) interface
 
 - The WLC's management (or AP manager) interface's default gateway's
 MAC address' high order byte is nonzero.
   
 Workaround:
 
 If the MAC address of the WLC's default gateway does not begin with 00,
 and if all of the APs' MAC addresses begin with 00, then: you can put
the APs into the same subnet as the WLC's management (or AP manager)
interface.

In the general case, for the situation where the WLC's default gateway's
MAC does not begin with 00, you can address this by changing it to begin
with 00. Some methods for doing this include:
 
 -- use the "mac-address" command on the gateway, to set a MAC address
 that begins with 00
 
 -- then enable HSRP on the gateway (standby ip ww.xx.yy.zz) and use this
 IP as the WLC's gateway.
 
 For the case where the APs' MAC addresses do not begin with 00, then make
 sure that they are *not* in the same subnet as the WLC's management
 (AP manager) interface, but are behind a router.
   
 Another workaround is to downgrade to 6.0.182.0.  However, after
 downgrading the WLC to 6.0.182.0, any APs that have 6.0.188.0 IOS
 (i.e. 12.4(21a)JA2) still installed on them will be unable to join.
 Therefore, after downgrading the WLC, the APs will need to have a
 pre-12.4(21a)JA2 rcvk9w8 or k9w8 image installed on them.

different vlan!!!! yes! thank you Matthew Fowler sooooo much!!!!

Vinay Sharma · ‎03-12-2012

This Discussion has been converted into document:- https://supportforums.cisco.com/docs/DOC-23054

Thanks,

Vinay Sharma

Thanks & Regards

18091988n · ‎03-12-2012

woow! very welcome news) hope, that will help people with similar situation