WLC cannot detect the AP

Unanswered Question
Jun 20th, 2012

hi there,

i have some problem.

i have WLC 2540 and AP 1142..

i have configure them both and got connected(WLC can detect the AP) yesterday then i turn off them both and now when i powered up , the WLC cant detect the AP but AP and WLC can still ping each other they comunicated at layer 2, both WLC and AP in one IP segment.

here some debug from AP

*Jun 21 13:49:47.784: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.3.2

*Jun 21 13:50:05.913: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceed                                                                                        ., 1)x(UNKNOWN_MESSAGE_TYPE (5)

*Jun 21 13:50:05.913: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Jun 21 13:50:05.913: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.                                                                                        0.3.2:5246

*Jun 21 13:50:05.954: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led sta                                                                                      te 255

*Jun 21 13:50:06.042: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a                                                                                       dministratively down

*Jun 21 13:50:06.042: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to a                                                                                        dministratively down

*Jun 21 13:50:06.048: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Jun 21 13:50:06.073:  status of voice_diag_test from WLC is false

*Jun 21 13:50:06.077: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 21 13:50:07.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        1, changed state to down

*Jun 21 13:50:07.069: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Jun 21 13:50:07.074: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jun 21 13:50:08.064: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        1, changed state to up

*Jun 21 13:50:08.069: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        0, changed state to down

*Jun 21 13:50:08.094: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Jun 21 13:50:08.099: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Jun 21 13:50:08.104: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jun 21 13:50:09.094: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        0, changed state to up

*Jun 21 13:50:09.099: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        1, changed state to down

*Jun 21 13:50:09.125: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 21 13:50:10.125: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio                                                                                        1, changed state to up

*Jun 21 13:50:16.075: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jun 21 13:50:16.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i                                                                                     p: 10.0.3.2 peer_port: 5246

*Jun 21 13:50:16.776: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.0.3.2 peer_port: 5246

*Jun 21 13:50:16.777: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.3.2

and here the capwap debug event from WLC

*spamApTask4: Jun 21 13:54:30.683: f4:7f:35:dd:07:c0 Join Version: = 117597952

*spamApTask4: Jun 21 13:54:30.684: f4:7f:35:dd:07:c0 Join resp: CAPWAP Maximum Msg element len = 91

*spamApTask4: Jun 21 13:54:30.684: f4:7f:35:dd:07:c0 Join Response sent to 10.0.3.49:11059

*spamApTask4: Jun 21 13:54:30.684: f4:7f:35:dd:07:c0 CAPWAP State: Join

*spamApTask4: Jun 21 13:54:30.684: f4:7f:35:dd:07:c0 capwap_ac_platform.c:1224 - Operation State 0 ===> 4

*apfReceiveTask: Jun 21 13:54:30.685: f4:7f:35:dd:07:c0 Register LWAPP event for AP f4:7f:35:dd:07:c0 slot 0

*apfReceiveTask: Jun 21 13:54:30.685: WARP IEs: (12)

*apfReceiveTask: Jun 21 13:54:30.685:      [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*apfReceiveTask: Jun 21 13:54:30.685: f4:7f:35:dd:07:c0 Register LWAPP event for AP f4:7f:35:dd:07:c0 slot 1

*apfReceiveTask: Jun 21 13:54:30.685: WARP IEs: (12)

*apfReceiveTask: Jun 21 13:54:30.685:      [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*spamApTask4: Jun 21 13:54:30.808: f4:7f:35:dd:07:c0 Configuration Status from 10.0.3.49:11059

*spamApTask4: Jun 21 13:54:30.808: f4:7f:35:dd:07:c0 CAPWAP State: Configure

*spamApTask4: Jun 21 13:54:30.808: Invalid channel 1 spacified for the AP APa493.4c52.b318, slotId = 0

*spamApTask4: Jun 21 13:54:30.808: Invalid channel 56 spacified for the AP APa493.4c52.b318, slotId = 1

*spamApTask4: Jun 21 13:54:30.808: f4:7f:35:dd:07:c0 Updating IP info for AP f4:7f:35:dd:07:c0 -- static 0, 10.0.3.49/255.255.255.0, gtw 10.0.3.1

*spamApTask4: Jun 21 13:54:30.808: f4:7f:35:dd:07:c0 Updating IP 10.0.3.49 ===> 10.0.3.49 for AP f4:7f:35:dd:07:c0

*spamApTask4: Jun 21 13:54:30.809: f4:7f:35:dd:07:c0 Finding DTLS connection to delete for AP (10:0:3:49/11059)

*spamApTask4: Jun 21 13:54:30.809: f4:7f:35:dd:07:c0 Disconnecting DTLS Capwap-Ctrl session 0x14f2d7a0 for AP (10:0:3:49/11059)

*spamApTask4: Jun 21 13:54:30.809: f4:7f:35:dd:07:c0 CAPWAP State: Dtls tear down

*spamApTask4: Jun 21 13:54:30.809: f4:7f:35:dd:07:c0 DTLS keys for Control Plane deleted successfully for AP 10.0.3.49

*spamApTask4: Jun 21 13:54:30.810: f4:7f:35:dd:07:c0 DTLS connection closed event receivedserver (10:0:3:2/5246) client (10:0:3:49/11059)

*spamApTask4: Jun 21 13:54:30.810: f4:7f:35:dd:07:c0 Entry exists for AP (10:0:3:49/11059)

*spamApTask4: Jun 21 13:54:30.810: f4:7f:35:dd:07:c0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP f4:7f:35:dd:07:c0 slot 0

*spamApTask4: Jun 21 13:54:30.810: f4:7f:35:dd:07:c0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP f4:7f:35:dd:07:c0 slot 1

*apfReceiveTask: Jun 21 13:54:30.812: f4:7f:35:dd:07:c0 Deregister LWAPP event for AP f4:7f:35:dd:07:c0 slot 0

*apfReceiveTask: Jun 21 13:54:30.812: f4:7f:35:dd:07:c0 Deregister LWAPP event for AP f4:7f:35:dd:07:c0 slot 1

*spamApTask4: Jun 21 13:54:30.814: f4:7f:35:dd:07:c0 No AP entry exist in temporary database for 10.0.3.49:11059

*spamApTask3: Jun 21 13:54:48.967: f4:7f:35:dd:07:c0 Discovery Request from 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.967: f4:7f:35:dd:07:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0

*spamApTask3: Jun 21 13:54:48.967: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.967: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Request from 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Request from 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Discovery Request from 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.968: f4:7f:35:dd:07:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0

*spamApTask3: Jun 21 13:54:48.969: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:48.969: f4:7f:35:dd:07:c0 Discovery Response sent to 10.0.3.49:11058

*spamApTask3: Jun 21 13:54:58.968: f4:7f:35:dd:07:c0 DTLS connection not found, creating new connection for 10:0:3:49 (11058) 10:0:3:2 (5246)

*spamApTask3: Jun 21 13:54:59.743: f4:7f:35:dd:07:c0 Allocated index from main list, Index: 18

*spamApTask3: Jun 21 13:54:59.744: f4:7f:35:dd:07:c0 DTLS keys for Control Plane are plumbed successfully for AP 10.0.3.49. Index 19

*spamApTask3: Jun 21 13:54:59.744: f4:7f:35:dd:07:c0 DTLS Session established server (10.0.3.2:5246), client (10.0.3.49:11058)

*spamApTask3: Jun 21 13:54:59.744: f4:7f:35:dd:07:c0 Starting wait join timer for AP: 10.0.3.49:11058

i dont have any idea whats wrong..

help me please

thanks for your response

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (3 ratings)
maldehne Thu, 06/21/2012 - 02:38

From the AP:

Debug capwap client event

Debug capwap client error

From the WLC:

Debug mac addr < mac of the AP not connecting>

Debug capwap event enable

Debug capwap error enable

Debug pm pki enable

Show run-config

Show msglog

Show traplog

raitoboyz Sun, 06/24/2012 - 18:19

thanks for the answer maldehne.

the problem is on the country code from the first configuration in the WLC

ronshuster Thu, 07/18/2013 - 14:24

I have a question along the same lines :

I have an AP AIR-AP1142N-A-K9  with version ID of V05 and I just uploaded an image that works for the same model but V01 and my AP is unable to join the controller I get this message :

*Jul 20 21:06:38.711: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.2 peer_port: 5246

*Jul 20 21:06:38.711: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.2

*Jul 20 21:06:38.729: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.2

*Jul 20 21:06:38.729: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.2:5246

*Jul 20 21:06:38.781: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

The image I am using is c1140-k9w8-tar.152-2.JB.tar which works well with the the same model AP but version id V01 but not v05.

Any suggestion?

Actions

Login or Register to take actions

This Discussion

Posted June 20, 2012 at 11:59 PM
Stats:
Replies:4 Avg. Rating:5
Views:3327 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard