cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
244
Views
5
Helpful
4
Replies
Beginner

My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

gs from AP console

****************************

*Jul 14 10:13:05.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:06.330: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:06.330: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.32.104
*Jul 14 10:13:06.340: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.32.104
*Jul 14 10:13:06.340: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.32.104:5246
*Jul 14 10:13:06.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:06.254: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:06.257: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.32.104
*Jul 14 10:13:06.267: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.32.104
*Jul 14 10:13:06.267: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.32.104:5246
*Jul 14 10:13:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:27.257: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:27.257: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.32.104
*Jul 14 10:13:27.264: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.32.104
*Jul 14 10:13:27.264: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.32.104:5246
*Jul 14 10:13:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:27.257: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.32.104 peer_port: 5246
*Jul 14 10:13:27.257: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.32.104
*Jul 14 10:13:27.273: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.32.104
Not in Bound state.

 

Logs from WLC:

 


*spamApTask7: Jul 14 15:40:55.832: 64:ae:0c:87:07:10 Join Request from 172.16.32.16:38836

*spamApTask7: Jul 14 15:40:55.832: 64:ae:0c:87:07:10 Allocate database entry for AP 172.16.32.16:38836, already allocated index 65535

*spamApTask7: Jul 14 15:40:55.832: 64:ae:0c:87:07:10 AP Allocate request at index ffff
*spamApTask7: Jul 14 15:40:55.876: 44:d3:ca:59:7b:25 Deleting AP entry 172.16.32.16:38836 from temporary database.
*spamApTask7: Jul 14 15:40:55.876: 64:ae:0c:87:07:10 Dropping request or response packet to AP :172.16.32.16 (38836) by Controller: 172.16.32.104 (5246), message Capwap_wtp_event_response, state Capwap_no_state

*spamApTask7: Jul 14 15:40:55.876: 64:ae:0c:87:07:10 Message type Capwap_wtp_event_response is not allowed to send in state Capwap_no_state for AP 172.16.32.16

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Finding DTLS connection to delete for AP (172:16:32:16/38836)
*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Disconnecting DTLS Capwap-Ctrl session 0x9778b70 for AP (172:16:32:16/38836). Notify(true)
*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 CAPWAP State: Dtls tear down

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 MIC AP is not allowed to join by config

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Join Request failed!

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 DTLS connection closed event receivedserver (172.16.32.104/5246) client (172.16.32.16/38836)
*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Entry exists for AP (172.16.32.16/38836)
*spamApTask7: Jul 14 15:40:55.882: 64:ae:0c:87:07:10 AP Delete request
*spamApTask7: Jul 14 15:40:55.882: 64:ae:0c:87:07:10 No AP entry exist in temporary database for 172.16.32.16:38836

2 ACCEPTED SOLUTIONS

Accepted Solutions
Beginner

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 MIC AP is not allowed to join by config

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Join Request failed!

 

 

Check that MIC certificates are accepted by the vWLC in the Security -> AAA -> AP Policies menu.

Highlighted
Beginner

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

Thank you so much..It works for me now..
4 REPLIES 4
Hall of Fame Community Legend

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

Post the complete output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time; and
3. AP: sh version
VIP Mentor

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

Pls check your WLC got licenses activated.

 

Also note that vWLC supported FlexConnect mode only, so once AP registered, you have to change it to FlexConnect mode from Local mode

 

HTH

Rasika

*** Pls rate all useful responses ***

Beginner

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 MIC AP is not allowed to join by config

*spamApTask7: Jul 14 15:40:55.881: 64:ae:0c:87:07:10 Join Request failed!

 

 

Check that MIC certificates are accepted by the vWLC in the Security -> AAA -> AP Policies menu.

Highlighted
Beginner

Re: My AIR-CAP3502I-N-K9 is not joining the vWLC. Need expert advice

Thank you so much..It works for me now..
CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards