07-26-2019 07:28 AM - edited 07-05-2021 10:45 AM
Hi,
I have been testing different AP's with WLC and facing issues with two of the AP's as they are unable to join the WLC and always showing as unjoined and giving errors.
Previously these AP's were configured with Autonomous SW and then i have upgraded it to controller version ap3g2-k9w8-tar.153-3.JI3.tar now its is giving error on 2702i-C-K9
*Jul 26 05:58:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:58:46.523: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:58:46.523: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:58:51.523: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:58:51.523: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.7
*Jul 26 05:58:51.523: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.7:5246
*Jul 26 05:58:51.523: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Jul 26 05:58:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:58:52.535: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:58:52.539: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:58:57.539: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:58:57.539: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.7
*Jul 26 05:58:57.539: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.7:5246
Not in Bound state.
*Jul 26 05:59:13.543: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Jul 26 05:59:16.615: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 172.16.0.205, mask 255.255.0.0, hostname APa46c.2a89.11f0
Translating "CISCO-CAPWAP-CONTROLLER.avanza.pk"...domain server (172.16.0.5)
*Jul 26 05:59:45.547: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Jul 26 05:59:45.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:59:46.519: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:59:46.519: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:59:48.279: WARNING - Received pak from RXTX port - Check log for detailed info
*Jul 26 05:59:51.519: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:59:51.519: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.7
*Jul 26 05:59:51.519: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.7:5246
*Jul 26 05:59:51.519: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Jul 26 05:59:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:59:52.531: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 05:59:52.531: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:59:57.531: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 05:59:57.531: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.7
*Jul 26 05:59:57.531: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.7:5246
*Jul 26 06:00:17.531: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Jul 26 06:00:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 06:00:17.519: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.0.7 peer_port: 5246
*Jul 26 06:00:17.519: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 06:00:22.519: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.0.7
*Jul 26 06:00:22.519: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.0.7
*Jul 26 06:00:22.519: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.0.7:5246
*Jul 26 06:00:22.519: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Jul 26 06:00:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection reque
Can anyone help me out
07-26-2019 07:34 AM
@ShariqSiddiqui5033 wrote:
*Jul 26 05:59:13.543: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
Is DHCP Option configured (correctly)?
07-29-2019 04:26 AM
from where I can check this option since right now AP is not joined by WLC
07-31-2019 06:28 AM
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