Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

AIR-CAP2602 will not register with 5508WLC

I setup this controller a month or two ago and have joined several AIP-CAP2602I-A-K9 AP's to it. I went to add a few more and they will not register. Here is the data from the console of the AP.

Mar  1 00:00:13.047: %CDP_PD-2-POWER_LOW: All radios disabled - AC_ADAPTOR  (0000.0000.0000)
*Mar  1 00:00:13.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar  1 00:00:15.447: DPAA Initialization Complete
*Mar  1 00:00:15.447: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar  1 00:00:15.979: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
no bridge-group 1 source-learning
                   ^
% Invalid input detected at '^' marker.
%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar  1 00:00:46.563: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.8.58, mask 255.255.0.0, hostname APe02f.6da3.6037

Translating "CISCO-CAPWAP-CONTROLLER.JSMC.ORG"...domain server (10.1.0.20)
*Mar  1 00:00:57.539: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar  1 00:01:00.539: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.JSMC.OR

*Jul 25 13:36:54.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:36:56.443: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:36:56.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
*Jul 25 13:37:01.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
*Jul 25 13:37:01.447: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.7.47
*Jul 25 13:37:01.447: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.7.47:5246
*Jul 25 13:37:01.447: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 25 13:36:54.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:36:54.447: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:36:54.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
logging facility kern
        ^
% Invalid input detected at '^' marker.

logging trap emergencies
        ^
% Invalid input detected at '^' marker.

logging facility kern
        ^
% Invalid input detected at '^' marker.

logging trap emergencies
        ^
% Invalid input detected at '^' marker.

*Jul 25 13:36:59.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
*Jul 25 13:36:59.447: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.7.47
*Jul 25 13:36:59.447: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.7.47:5246
*Jul 25 13:36:59.447: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 25

*Jul 25 13:37:09.807: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 25 13:37:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:37:17.443: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:37:17.443: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
*Jul 25 13:37:22.443: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47
*Jul 25 13:37:22.443: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.7.47
*Jul 25 13:37:22.443: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.7.47:5246
*Jul 25 13:37:22.443: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 25 13:37:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.7.47 peer_port: 5246
*Jul 25 13:37:17.447: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.7.47 peer_port: 5246

*Jul 25 13:37:17.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47

logging facility kern

        ^

% Invalid input detected at '^' marker.

logging trap emergencies

        ^

% Invalid input detected at '^' marker.

logging facility kern

        ^

% Invalid input detected at '^' marker.

logging trap emergencies

        ^

% Invalid input detected at '^' marker.

*Jul 25 13:37:22.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.7.47

*Jul 25 13:37:22.447: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.7.47

*Jul 25 13:37:22.447: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.7.47:5246

*Jul 25 13:37:22.447: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

Any help would be greatly appreciated. Thanks in advance

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

Re: AIR-CAP2602 will not register with 5508WLC

can you get debug capwap event and debug capwap error as well on wlc

Sent from Cisco Technical Support iPad App

3 REPLIES
Bronze

Re: AIR-CAP2602 will not register with 5508WLC

can you get debug capwap event and debug capwap error as well on wlc

Sent from Cisco Technical Support iPad App

New Member

AIR-CAP2602 will not register with 5508WLC

Debug capwap event log:

*spamApTask6: Jul 25 12:02:06.487: e0:2f:6d:a3:60:30  Join request received from AP which is already present. Deleting  previous  connection                                                                                                                                         10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.487: e0:2f:6d:a3:60:30 Finding DTLS connection to delete for AP (10:1:8:58/13828)

*spamApTask6: Jul 25 12:02:06.487: e0:2f:6d:a3:60:30 Disconnecting DTLS Capwap-Ctrl session 0x146ee4d8 for AP (10:1:8:58/13828)

*spamApTask6: Jul 25 12:02:06.487: e0:2f:6d:a3:60:30 CAPWAP State: Dtls tear down

*spamApTask6: Jul 25 12:02:06.488: e0:2f:6d:a3:60:30 DTLS keys for Control Plane deleted successfully for AP 10.1.8.58

*spamApTask6: Jul 25 12:02:06.489: e0:2f:6d:a3:60:30 DTLS connection not found. Ignoring join request from 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.489: e0:2f:6d:a3:60:30 DTLS  connection closed event receivedserver (10:1:7:47/5246) client  (10:1:8:58/13828)

*spamApTask6: Jul 25 12:02:06.489: e0:2f:6d:a3:60:30 No entry exists for AP (10:1:8:58/13828)

*spamApTask6: Jul 25 12:02:06.489: e0:2f:6d:a3:60:30 No AP entry exist in temporary database for 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.849: e0:2f:6d:a3:60:30 Discovery Request from 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.849: e0:2f:6d:a3:60:30 Join  Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25,  joined Aps =4

*spamApTask6: Jul 25 12:02:06.849: e0:2f:6d:a3:60:30 Discovery Response sent to 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.849: e0:2f:6d:a3:60:30 Discovery Response sent to 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.850: e0:2f:6d:a3:60:30 Discovery Request from 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.850: e0:2f:6d:a3:60:30 Join  Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25,  joined Aps =4

*spamApTask6: Jul 25 12:02:06.850: e0:2f:6d:a3:60:30 Discovery Response sent to 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:06.850: e0:2f:6d:a3:60:30 Discovery Response sent to 10.1.8.58:13828

*spamApTask4: Jul 25 12:02:09.661: 04:da:d2:4e:93:e0 WTP Event Request from 10.1.8.55:7061

*spamApTask4: Jul 25 12:02:09.661: 04:da:d2:4e:93:e0 WTP Event Response sent to 10.1.8.55:7061

*spamApTask3: Jul 25 12:02:15.409: 24:01:c7:c1:e2:00 WTP Event Request from 10.1.8.56:13827

*spamApTask3: Jul 25 12:02:15.409: 24:01:c7:c1:e2:00 WTP Event Response sent to 10.1.8.56:13827

*spamApTask6: Jul 25 12:02:16.847: e0:2f:6d:a3:60:30 DTLS  connection not found, creating new connection for 10:1:8:58 (13828)  10:1:7:47 (5246)

*spamApTask6: Jul 25 12:02:17.295: e0:2f:6d:a3:60:30 Allocated index from main list, Index: 114

*spamApTask6: Jul 25 12:02:17.295: e0:2f:6d:a3:60:30 DTLS keys  for Control Plane are plumbed successfully for AP 10.1.8.58. Index 115

*spamApTask6: Jul 25 12:02:17.295: e0:2f:6d:a3:60:30 DTLS Session established server (10.1.7.47:5246), client (10.1.8.58:13828)

*spamApTask6: Jul 25 12:02:17.295: e0:2f:6d:a3:60:30 Starting wait join timer for AP: 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:17.297: e0:2f:6d:a3:60:30 Join Request from 10.1.8.58:13828

*spamApTask6: Jul 25 12:02:17.298: e0:2f:6d:a3:60:30 Deleting AP entry 10.1.8.58:13828 from temporary database.

*spamApTask6: Jul 25 12:02:17.298: e0:2f:6d:a3:60:30 MIC AP is not allowed to join by config

*spamReceiveTask: Jul 25 12:02:20.053: 04:da:d2:4e:93:e0 Configuration update request for delete station sent to 10.1.8.55:7061

*spamApTask4: Jul 25 12:02:20.054: 04:da:d2:4e:93:e0 Configuration Update Response from 10.1.8.55:7061

*spamApTask4: Jul 25 12:02:20.055: 04:da:d2:4e:93:e0 Configuration Update Response from 10.1.8.55:7061

*spamApTask4: Jul 25 12:02:20.403: 24:01:c7:f7:2e:60 Echo Request from 10.1.8.70:60150

*spamApTask4: Jul 25 12:02:20.403: 24:01:c7:f7:2e:60 Echo Response sent to 10.1.8.70:60150

*spamApTask6: Jul 25 12:02:22.296: e0:2f:6d:a3:60:30 Join Request from 10.1.8.58:1382

Capwap Error:

*spamApTask6: Jul 25 12:06:37.352: e0:2f:6d:a3:60:30 Multiple Join Request: Join request received from AP which is already present. Deleting previous conne

*spamApTask6: Jul 25 12:06:37.354: e0:2f:6d:a3:60:30 State machine handler: Failed to process  msg type = 3 state = 0 from 10.1.8.58:13828

*spamApTask6: Jul 25 12:06:37.354: e0:2f:6d:a3:60:30 Failed to parse CAPWAP packet from 10.1.8.58:13828

*spamApTask6: Jul 25 12:06:37.354: e0:2f:6d:a3:60:30 Discarding non-ClientHello Handshake OR DTLS encrypted packet from  10.1.8.58:13828)since DTLS session is not established

*spamApTask6: Jul 25 12:06:37.806: e0:2f:6d:a3:60:30 State machine handler: Failed to process  msg type = 3 state = 0 from 10.1.8.58:13828

*spamApTask6: Jul 25 12:06:37.806: e0:2f:6d:a3:60:30 Failed to parse CAPWAP packet from 10.1.8.58:13828

New Member

AIR-CAP2602 will not register with 5508WLC

I resolved it. I noticed in the CAPWAP event log where it says "MIC AP is not allowed to join by config". I told the controller to accept Manufactured Installed Certificate (MIC) and they are registering now. Thanks for the help

1141
Views
0
Helpful
3
Replies