04-06-2016 05:01 PM - edited 03-05-2019 03:44 AM
Hi,
I'm having an issue with a Cisco WAP unable to join the controller. I keep seeing the below but I have no idea why it won't join. I only have remote console access to the WAP at this time.
Apr 6 23:57:26.470: Starting Ethernet promiscuous mode
*Apr 6 23:57:36.476: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 6 23:57:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.100 peer_port: 5246
*Apr 6 23:57:37.131: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.100 peer_port: 5246
*Apr 6 23:57:37.132: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.100
*Apr 6 23:57:42.132: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.100
*Apr 6 23:57:42.353: Starting Ethernet promiscuous mode
*Apr 6 23:57:42.390: %LWAPP-4-CLIENTEVENTLOG: No REAP configuration file to load. Connect to controller to get configuration file
*Apr 6 23:57:42.391: %LWAPP-4-CLIENTEVENTLOG: No REAP configuration file to load. Connect to controller to get configuration file
., 1) 6 23:58:00.390: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
*Apr 6 23:58:00.391: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Apr 6 23:58:00.391: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.100:5246
*Apr 6 23:58:00.425: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Apr 6 23:58:00.475: Starting Ethernet promiscuous mode
*Apr 6 23:58:10.481: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 6 23:58:11.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.100 peer_port: 5246
*Apr 6 23:58:12.124: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.100 peer_port: 5246
*Apr 6 23:58:12.125: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.100
*Apr 6 23:58:17.125: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.100
*Apr 6 23:58:17.336: Starting Ethernet promiscuous mode
*Apr 6 23:58:17.962: %LWAPP-4-CLIENTEVENTLOG: No REAP configuration file to load. Connect to controller to get configuration file
*Apr 6 23:58:17.963: %LWAPP-4-CLIENTEVENTLOG: No REAP configuration file to load. Connect to controller to get configuration file
., 1) 6 23:58:35.963: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
*Apr 6 23:58:35.963: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Apr 6 23:58:35.963: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.100:5246
*Apr 6 23:58:36.001: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Apr 6 23:58:36.051: Starting Ethernet promiscuous mode
04-06-2016 05:16 PM
Now seeing a bit of this:
%CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
But i can ping the controller IP and the DNS record "CISCO-CAPWAP-CONTROLLER" with no problems.
06-09-2016 05:48 AM
Guess nobody has seen this one before?
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