Yet another AP not connecting to WLC

[IJsblok]

You know the drill. 

AP = AIR-CAP-1602I-E-K3, software version 15.3(3)JF14i

WLC =  AIR-CT2504-K9, software version 8.5.105.0

This is all in lab. Both WLC and AP are in same Vlan. No other devices are in the vlan, except the switch. Had DHCP enabled on WLC for IP assignment to AP. 

This is what AP does:

*Apr 1 15:19:04.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:05.311: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:05.311: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:05.311: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.3
*Apr 1 15:19:05.315: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.3:5246
*Apr 1 15:19:05.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:05.315: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:05.315: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:05.315: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.3
*Apr 1 15:19:05.315: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.3:5246
*Apr 1 15:19:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:26.311: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:26.311: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:26.315: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.3
*Apr 1 15:19:26.315: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.3:5246
*Apr 1 15:19:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:26.000: %CDP_PD-4-POWER_OK: All radios disabled - NEGOTIATED inline power source
*Apr 1 15:19:26.315: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:26.315: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:47.311: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:47.311: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:47.315: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.3
*Apr 1 15:19:47.315: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.3:5246
*Apr 1 15:19:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:47.311: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.3 peer_port: 5246
*Apr 1 15:19:47.315: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.3
*Apr 1 15:19:47.315: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.2.3
*Apr 1 15:19:47.315: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.3:5246
Not in Bound state.
*Apr 1 15:19:52.819: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Apr 1 15:19:55.891: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.2.19, mask 255.255.255.0, hostname AP78da.6ee0.0c02

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

Loop. 

Led start to go red-orange green right after the last message, so it seem sort of reset itself ore something.  Then AP gets an ascending IP from DHCP (like 192.168.2.20, 192.168.2.21, etc). Also, if no WLC is available in the VLAN, the AP does never reset itself. Assigning a static IP does not make much difference. 

Time and date is set correctly on WLC. 

I already checked some debugging guidelines found elsewhere, checked certificates, country code... can't find any related error messages. 

Any help is much appreciated. Thanks in Advance. 

[IJsblok · Accepted solution]

Ok, I am a n00b and this proofs it. 

Maybe I should have just, i don't know, do something with AP Policies on the WLC and, like, permit the AP to join the WLC there. 

Well, I learned to properly read debug logs where I noticed this, so that's something. 

[Scott Fella]

I think everyone goes through this when they are not familiar and or has not had much experience. There are a lot of information, like guides, blogs and videos on setting up a Cisco Wireless network. I know many whom gotten equipment just plugs things in and expect everything to work. The WLC matrix is something that is used by novice to the most experienced engineers to validate what they have can work or understand what model and versions work with the controller they currently have. All the other stuff like ntp, dhcp, country code, option 43, dns, same subnet join are all things that are required and optional that many engineers make sure they have completed before any implementation, even in a lab or home environment. There are also tools that are available to everyone on the website that helps you with validation of your configuration and or analyze your debugs. The only way to get better is just experience and repetitiveness.

[Leo Laohoo]

I have used 8.5.105.0 and all I can say is this:  Please upgrade the controller firmware.