01-31-2011 01:33 PM - edited 07-03-2021 07:45 PM
This is a new wlc installation on the network that already has fucnitonal wlc. I would like to introduce secondary controller for redundancy. Setup dhcp option 43 on router' DHCP server for secondary wlc but when AP trying to join to the new controller, the bellow messages appers.
Any troubleshooting idea would be appreciated.Thanks
Here is output of the debug
(Cisco Controller) >debug capwap info enable
(Cisco Controller) >*spamApTask7: Jan 31 21:22:13.002: 00:00:00:00:00:00 DTLS keys for Control Plane deleted successfully for AP 10.10.10.4
*spamApTask7: Jan 31 21:22:13.003: 00:00:00:00:00:00 DTLS connection closed event receivedserver (2.2.2.2/5246) client (10.10.10.4/4153)
*spamApTask7: Jan 31 21:22:13.003: 00:00:00:00:00:00 DTLS Connection not found for 10.10.10.4:4153
*spamApTask7: Jan 31 21:22:13.003: 00:00:00:00:00:00 No entry exists for AP (10.10.10.4/4153)
*spamApTask7: Jan 31 21:22:13.003: 00:00:00:00:00:00 Finding AP in database
*spamApTask7: Jan 31 21:22:13.003: 00:00:00:00:00:00 No entry exists in database
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 length = 4, packet received from 0:0:0:0:0:0
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery Request from 10.10.10.4:4154
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery request: Total msgEleLen = 94
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery Type = DHCP
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery request: Vendor payload type = 207, length = 10
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery request: Vendor payload type = 5, length = 17
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 250, joined Aps =0
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 msgLength = 36
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 encodeLen = 122 len = 16
*spamApTask0: Jan 31 21:22:13.606: 00:00:00:00:00:00 Discovery Response sent to 10.10.10.4:4154
*osapiBsnTimer: Jan 31 21:22:13.953: 00:21:a0:51:5d:80 Wait join timer expired for connection 10.10.10.4:4153
*spamApTask7: Jan 31 21:22:13.953: 00:21:a0:51:5d:80 Disconnecting due to a wait join timer expiry event for (10.10.10.4:4153) server details (2.2.2.2:5246)
*spamApTask7: Jan 31 21:22:13.953: 00:21:a0:51:5d:80 DTLS Connection not found for 10.10.10.4:4153
02-07-2011 12:48 AM
Wat does the AP console logs say??
Regards
Surendra
09-24-2013 09:48 AM
Seeing the same issue with 1140/7.4/5508 WLC: WLC debug capwap events log: *spamApTask7: Sep 24 11:43:46.143: 04:c5:a4:f2:79:40 Primary Discovery Request from xxxxxxxxx:34854 *spamApTask7: Sep 24 11:43:46.143: 04:c5:a4:f2:79:40 Primary Discovery Response sent to xxxxxxxxx:34854 *spamApTask0: Sep 24 11:43:46.334: 04:c5:a4:f2:79:40 Discovery Request from xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:46.335: 04:c5:a4:f2:79:40 Discovery Response sent to xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:46.335: 04:c5:a4:f2:79:40 Discovery Response sent to xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:46.335: 04:c5:a4:f2:79:40 Discovery Request from xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:46.335: 04:c5:a4:f2:79:40 Discovery Response sent to xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:46.336: 04:c5:a4:f2:79:40 Discovery Response sent to xxxxxxxxx:34855 *spamApTask0: Sep 24 11:43:57.027: 04:c5:a4:f2:79:40 DTLS keys for Control Plane are plumbed successfully for AP xxxxxxxxx Index 405 *spamApTask0: Sep 24 11:43:57.029: 04:c5:a4:f2:79:40 DTLS Session established server (xxxxxxxxx:5246), client(xxxxxxxxx:34855) *spamApTask0: Sep 24 11:43:57.029: 04:c5:a4:f2:79:40 Starting wait join timer for AP: xxxxxxxxx:34855 *osapiBsnTimer: Sep 24 11:44:56.935: 04:c5:a4:f2:79:40 Wait join timer expired for connection xxxxxxxxx:34855 *spamApTask0: Sep 24 11:44:56.935: 04:c5:a4:f2:79:40 Disconnecting due to a wait join timer expiry event for (xxxxxxxxx:34855) server details (xxxxxxxxx:5246) *spamApTask0: Sep 24 11:44:56.936: 04:c5:a4:f2:79:40 DTLS keys for Control Plane deleted successfully for AP xxxxxxxxx *spamApTask0: Sep 24 11:44:56.947: 04:c5:a4:f2:79:40 Deleting AP entry xxxxxxxxx:34855 from temporary database. *spamApTask0: Sep 24 11:44:56.948: 04:c5:a4:f2:79:40 No AP entry exist in temporary database for xxxxxxxxx:34855 AP log: *spamApTask4: Sep 24 12:29:36.269: b8:be:bf:15:e5:00 xxxxxxxxxap2: *Sep 23 21:55:06.468: %CAPWAP-3-ERRORLOG: Selected MWAR 'xxxxxwlc1'(index 0). *spamApTask4: Sep 24 12:29:36.269: b8:be:bf:15:e5:00 xxxxxxxxxap2: *Sep 23 21:55:06.468: %CAPWAP-3-ERRORLOG: Go join a capwap controller *spamApTask4: Sep 24 12:29:36.269: b8:be:bf:15:e5:00 xxxxxxxxxap2: *Sep 23 21:54:56.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: xxxxxxxxx peer_port: 5246 *spamApTask4: Sep 24 12:29:36.269: b8:be:bf:15:e5:00 xxxxxxxxxap2: *Sep 23 21:55:26.150: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached! *spamApTask4: Sep 24 12:29:36.269: b8:be:bf:15:e5:00 xxxxxxxxxap2: *Sep 23 21:55:55.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to xxxxxxxxx:5246
09-24-2013 12:55 PM
Do you have this issue with single 1140 AP or none of APs can join this 5508 ? Are you doing any AP Authorization ?
I would do "clear capwap private-config" on the AP & see whether it make any difference.
HTH
Rasika
09-24-2013 06:38 PM
Thanks Rasika, No AAA AP auth in place. 186 APs are currently connected. The APs in question are all on the same switch, but they join other 7.4 5508s without problem. Have been able to move 2600s over without issue. I have cleared the config once already, but may try it again. Regards,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide