Unable to Join AP to WLC - unsupported AP?

[Spidey's Curse]

I am in the process of updating my companies switches. We currently have 6 AP's AIR-CAP2702E-A-K9

I am running the WLC off of a C9120AXI-B, running 17.6.4

I can see my AIR-CAP2702E-A-K9 in the WLC, under join statistics and it even has an IP address, however the status is "Not Joined" and says unsupported AP.

Im really trying everything I can to not have to upgrade all of the AP's in my building, but I figured I would just see if there was a way to still be able to use these.

This is the info from the CAP2702E

APd8b1.900e.1ff4#show version
Cisco IOS Software, C2700 Software (AP3G2-RCVK9W8-M), Version 15.3(3)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Thu 19-Feb-15 10:27 by prod_rel_team

ROM: Bootstrap program is C2700 boot loader
BOOTLDR: C2700 Boot Loader (AP3G2-BOOT-M) LoaderVersion 15.2(4)JB5m, RELEASE SOFTWARE (fc2)

APd8b1.900e.1ff4 uptime is 19 hours, 38 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-xx"
Last reload reason:

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco AIR-CAP2702E-A-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FTX1928S0UL
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.115.0
1 Gigabit Ethernet interface

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: D8:B1:90:0E:1F:F4
Part Number : 73-15823-03
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC19240PSM
Top Assembly Part Number : 800-41175-02
Top Assembly Serial Number : FTX1928S0UL
Top Revision Number : A0
Product/Model Number : AIR-CAP2702E-A-K9

Configuration register is 0xF

When I PUTTY into the WAP, I get all of this 

*May 3 18:31:25.267: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:31:25.267: DHCP: SRelease: 275 bytes
*May 3 18:31:26.727: DHCP: SRelease attempt # 2 for entry:
*May 3 18:31:26.727: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:31:26.727: DHCP: SRelease: 275 bytes
*May 3 18:31:28.727: DHCP: SRelease attempt # 3 for entry:
*May 3 18:31:28.727: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:31:28.727: DHCP: SRelease: 275 bytes
Not in Bound state.
*May 3 18:31:30.767: RAC: DHCP stopped on interface BVI1
*May 3 18:31:30.767: DHCP: DHCP client process started: 10
*May 3 18:31:30.767: DHCP: Attempting to speed up renewal timer
*May 3 18:31:30.767: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 3 18:31:30.767: RAC: Starting DHCP discover on BVI1
*May 3 18:31:30.767: DHCP: Try 1 to acquire address for BVI1
*May 3 18:31:30.767: DHCP: allocate request
*May 3 18:31:30.767: DHCP: zapping entry in DHC_PURGING state for BV1
*May 3 18:31:30.767: DHCP: deleting entry 55B22FC 192.168.25.57 from list
*May 3 18:31:30.767: DHCP: new entry. add to queue, interface BVI1
*May 3 18:31:30.767: DHCP: SDiscover attempt # 1 for entry:
*May 3 18:31:30.767: DHCP: SDiscover: sending 302 byte length DHCP packet
*May 3 18:31:30.767: DHCP: SDiscover 302 bytes
*May 3 18:31:30.767: B'cast on BVI1 interface from 0.0.0.0
*May 3 18:31:32.771: DHCP: Received a BOOTREP pkt
*May 3 18:31:32.771: DHCP: offer received from 192.168.25.10
*May 3 18:31:32.771: DHCP: SRequest attempt # 1 for entry:
*May 3 18:31:32.771: DHCP: SRequest- Server ID option: 192.168.25.10
*May 3 18:31:32.771: DHCP: SRequest- Requested IP addr option: 192.168.25.58
*May 3 18:31:32.771: DHCP: SRequest: 314 bytes
*May 3 18:31:32.771: DHCP: SRequest: 314 bytes
*May 3 18:31:32.771: B'cast on BVI1 interface from 0.0.0.0
*May 3 18:31:32.771: DHCP: Received a BOOTREP pkt
*May 3 18:31:35.887: Allocated IP address = 192.168.25.58 255.255.255.0

*May 3 18:31:35.887: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.58, mask 255.255.255.0, hostname APd8b1.900e.1ff4

*May 3 18:31:36.771: DHCP: Sending notification of ASSIGNMENT:
*May 3 18:31:36.771: Address 192.168.25.58 mask 255.255.255.0
*May 3 18:31:36.771: DHCP Client Pooling: ***Allocated IP address: 192.168.25.58
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (8.8.8.8)

*May 3 18:31:41.767: DHCP: look up vendor specific information for BV1 ret: fail
*May 3 18:31:41.767: DHCP: look up prim Log Server for BV1 from lease any ret: fail
*May 3 18:31:41.767: DHCP: look up prim DNS for BV1 from lease good ret: 8.8.8.8
*May 3 18:31:41.767: DHCP: look up domain name for BV1 from lease any ret: fail
*May 3 18:31:43.771: DHCP: Client socket is closed
*May 3 18:31:51.787: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 3 18:31:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:31:53.263: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:31:53.267: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 3 18:31:53.271: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 3 18:31:53.271: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 3 18:31:53.271: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 3 18:31:53.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:31:53.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:31:53.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 3 18:31:53.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 3 18:31:53.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 3 18:32:13.267: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 3 18:32:14.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:32:14.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:32:14.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 3 18:32:14.267: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 3 18:32:14.267: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 3 18:32:14.267: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 3 18:32:14.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:32:14.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 3 18:32:14.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 3 18:32:14.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 3 18:32:24.263: DHCP: Sending notification of TERMINATION:
*May 3 18:32:24.263: Address 192.168.25.58 mask 255.255.255.0
*May 3 18:32:24.263: DHCP: Client socket is opened
*May 3 18:32:24.263: DHCP: SRelease attempt # 1 for entry:
*May 3 18:32:24.263: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:32:24.263: DHCP: SRelease: 275 bytes
*May 3 18:32:26.203: DHCP: SRelease attempt # 2 for entry:
*May 3 18:32:26.203: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:32:26.203: DHCP: SRelease: 275 bytes
Not in Bound state.
*May 3 18:32:28.203: DHCP: SRelease attempt # 3 for entry:
*May 3 18:32:28.203: DHCP: SRelease placed Server ID option: 192.168.25.10
*May 3 18:32:28.203: DHCP: SRelease: 275 bytes
*May 3 18:32:29.763: RAC: DHCP stopped on interface BVI1
*May 3 18:32:29.763: DHCP: DHCP client process started: 10
*May 3 18:32:29.763: DHCP: Attempting to speed up renewal timer
*May 3 18:32:29.763: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 3 18:32:29.763: RAC: Starting DHCP discover on BVI1
*May 3 18:32:29.763: DHCP: Try 1 to acquire address for BVI1
*May 3 18:32:29.763: DHCP: allocate request
*May 3 18:32:29.763: DHCP: zapping entry in DHC_RELEASING state for BV1
*May 3 18:32:29.763: DHCP: deleting entry 55B1F98 192.168.25.58 from list
*May 3 18:32:29.763: DHCP: new entry. add to queue, interface BVI1
*May 3 18:32:29.763: DHCP: SDiscover attempt # 1 for entry:
*May 3 18:32:29.763: DHCP: SDiscover: sending 302 byte length DHCP packet
*May 3 18:32:29.763: DHCP: SDiscover 302 bytes
*May 3 18:32:29.763: B'cast on BVI1 interface from 0.0.0.0
*May 3 18:32:31.767: DHCP: Received a BOOTREP pkt
*May 3 18:32:31.767: DHCP: offer received from 192.168.25.10
*May 3 18:32:31.767: DHCP: SRequest attempt # 1 for entry:
*May 3 18:32:31.767: DHCP: SRequest- Server ID option: 192.168.25.10
*May 3 18:32:31.767: DHCP: SRequest- Requested IP addr option: 192.168.25.59
*May 3 18:32:31.767: DHCP: SRequest: 314 bytes
*May 3 18:32:31.767: DHCP: SRequest: 314 bytes
*May 3 18:32:31.767: B'cast on BVI1 interface from 0.0.0.0
*May 3 18:32:31.767: DHCP: Received a BOOTREP pkt
*May 3 18:32:34.883: Allocated IP address = 192.168.25.59 255.255.255.0

*May 3 18:32:34.883: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.59, mask 255.255.255.0, hostname APd8b1.900e.1ff4

*May 3 18:32:35.767: DHCP: Sending notification of ASSIGNMENT:
*May 3 18:32:35.767: Address 192.168.25.59 mask 255.255.255.0
*May 3 18:32:35.767: DHCP Client Pooling: ***Allocated IP address: 192.168.25.59
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (8.8.8.8)

So there does appear to be some communication going on between the devices. Im just wondering if this is even supported and if I should keep trying to get it to work.

If it IS supported, then could anyone please help me understand what I need to do in order to get this AP connected?

Thank you so much in advance to anyone that can assist. Ive had a lot of positive interactions in this community and I am very grateful and thankful for everyone that has helped me thus far. 

[Flavio Miranda]

Hello

 It is not supported as per Cisco compatibility matrix

https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

[Leo Laohoo]

The WLC needs to be upgraded to 17.9.3 in order to support 1700/2700/3700/1570 & IW3700.

[Spidey's Curse]

Thank you so much!

So, I updated to 17.9.3, but still unable to join the AP

Im getting all of this...

isco AIR-CAP2702E-A-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FTX1928S0UL
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.115.0
1 Gigabit Ethernet interface

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: D8:B1:90:0E:1F:F4
Part Number : 73-15823-03
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC19240PSM
Top Assembly Part Number : 800-41175-02
Top Assembly Serial Number : FTX1928S0UL
Top Revision Number : A0
Product/Model Number : AIR-CAP2702E-A-K9
% Please define a domain-name first.
ipv6 enable
^
% Invalid input detected at '^' marker.

ipv6 address autoconfig
^
% Invalid input detected at '^' marker.

ipv6 address dhcp
^
% Invalid input detected at '^' marker.

Press RETURN to get started!

*Mar 1 00:00:13.367: APAVC: Initial WLAN Buffers Given to System is 2500

*Mar 1 00:00:13.419: APAVC: WlanPAKs 42878 RadioPaks 42270

*Mar 1 00:00:13.419: Starting Ethernet promiscuous mode
*Mar 1 00:00:13.427: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg

*Mar 1 00:00:15.439: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:15.439: %LINK-6-UPDOWN: Interface GigabitEthernet1, changed state to up
*Mar 1 00:00:15.575: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C2700 Software (AP3G2-RCVK9W8-M), Version 15.3(3)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Thu 19-Feb-15 10:27 by prod_rel_team
*Mar 1 00:00:15.623: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
lwapp_crypto_init: MIC Present and Parsed Successfully

*Mar 1 00:00:15.767: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:16.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:20.427: DPAA Initialization Complete
*Mar 1 00:00:20.427: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar 1 00:00:21.427: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:23.427: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:24.427: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Mar 1 00:00:27.607: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:00:28.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:28.679: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.29, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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:34.427: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg

%Error opening flash:/capwap-saved-config (No such file or directory)
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (8.8.8.8)

*Mar 1 00:01:05.463: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:16.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:17.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:17.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:17.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:17.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:23:17.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:17.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:17.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:17.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:17.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:23:32.255: %CDP_PD-4-POWER_OK: 15.4 W power - NEGOTIATED inline power source
*May 4 15:23:34.255: %LINK-5-CHANGED: Interface GigabitEthernet1, changed state to administratively down
*May 4 15:23:37.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:37.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:37.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:37.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:37.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:37.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:23:37.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:37.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:37.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:37.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:37.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:57.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:58.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:58.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:58.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:58.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:58.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:23:58.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:23:58.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:58.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:23:58.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:23:58.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:23:58.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
Not in Bound state.
*May 4 15:24:03.759: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:24:08.879: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.30, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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

*May 4 15:24:20.919: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*May 4 15:24:24.771: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:24:25.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:26.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:26.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:24:26.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:24:26.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:24:26.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:24:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:26.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:26.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:24:26.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:24:26.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:24:46.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:24:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:46.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:46.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:24:46.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:24:46.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:24:46.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:24:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:46.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:24:46.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:24:46.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
Not in Bound state.
*May 4 15:25:01.763: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:25:06.883: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.31, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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

*May 4 15:25:32.775: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:25:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:35.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:35.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:25:35.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:25:35.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:25:35.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:25:35.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:35.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:35.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:25:35.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:25:35.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:25:55.267: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:25:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:55.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:55.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:25:55.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:25:55.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:25:55.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:25:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:55.259: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:25:55.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:25:55.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
Not in Bound state.
*May 4 15:26:00.767: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:26:05.887: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.32, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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

*May 4 15:26:21.779: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:26:22.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:23.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:23.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:26:23.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:26:23.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:26:23.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:26:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:23.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:23.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:26:23.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:26:23.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:26:43.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:26:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:44.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:44.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:26:44.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:26:44.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:26:44.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:26:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:44.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:26:44.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:26:44.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:26:44.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
Not in Bound state.
*May 4 15:26:59.763: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:27:04.883: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.33, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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

*May 4 15:27:30.775: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:27:31.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:28:00.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x5CCF2A0!

*May 4 15:28:30.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:28:30.999: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:28:31.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:29:00.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x5B79E54!

*May 4 15:29:30.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:29:50.999: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:29:51.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:29:51.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:29:51.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:29:51.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:29:51.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:29:51.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:29:51.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:29:51.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:29:51.259: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:29:51.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:29:51.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
Not in Bound state.
*May 4 15:29:56.763: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:30:01.883: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.34, mask 255.255.255.0, hostname APd8b1.900e.1ff4

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

*May 4 15:30:17.775: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:30:18.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:19.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:19.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:30:19.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:30:19.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:30:19.259: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:30:19.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:19.267: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:19.267: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:30:19.271: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:30:19.271: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:30:39.275: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:30:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:39.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:39.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:30:39.263: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
*May 4 15:30:39.263: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.25.10:5246
*May 4 15:30:39.263: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*May 4 15:30:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:39.255: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.25.10 peer_port: 5246
*May 4 15:30:39.255: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.25.10
*May 4 15:30:39.259: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.25.10
Not in Bound state.
*May 4 15:30:54.759: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*May 4 15:30:59.879: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.25.35, mask 255.255.255.0, hostname APd8b1.900e.1ff4

[Leo Laohoo]

---

@Spidey's Curse wrote:

*May 4 15:30:54.759: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.

---

The AP does not know the WLC details. 

Console into the AP and use the following command:  capwap ap primary-base <WLC NAME> <WLC IP ADDRESS>

[Spidey's Curse]

Im sorry for the late response. 

It looks like Im still getting errors in the logs like this AP is not supported

2023/05/09 15:58:24.735233914 {wncd_x_R0-0}{1}: [capwapac-smgr-sess] [8861]: (note): MAC: d8b1.900e.1ff4 Received CAPWAP join request
2023/05/09 15:58:24.736538724 {wncd_x_R0-0}{1}: [apmgr-capwap-join] [8861]: (ERR): d8b1.900e.1ff4 Join request not accepted: Unsupported AP Model AIR-CAP2702E-A-K9
2023/05/09 15:58:24.736552824 {wncd_x_R0-0}{1}: [apmgr-capwap-join] [8861]: (ERR): d8b1.900e.1ff4 Failed to process join request. Unable to decode apmgr join response
2023/05/09 15:58:24.736617005 {wncd_x_R0-0}{1}: [ap-join-info-db] [8861]: (note): MAC: d8b1.900e.1ff4 AP disconnect initiated. Reason: Unsupported ap, Phase: Join
2023/05/09 15:58:24.736620065 {wncd_x_R0-0}{1}: [apmgr-ap-global] [8861]: (ERR): d8b1.900e.1ff4 Failed to handle ap sm join request. Unable to process apmgr join request
2023/05/09 15:58:24.736625665 {wncd_x_R0-0}{1}: [apmgr-ap-global] [8861]: (ERR): d8b1.900e.1ff4 Failed to process join request deleting session.

However, according to the compatibly matrix, it should be compatible. 

2700 Series

AIR-CAP2702IE

7.6.100.0

8.10.x

Cisco IOS XE Denali 16.3.1

Cisco IOS XE Amsterdam 17.3.x Cisco IOS XE Cupertino 17.9.3 Note   This AP is not supported in releases 17.4.1 – 17.9.2.

[Leo Laohoo]

And what firmware is the WLC running on?

[Spidey's Curse]

17.9.3

[Leo Laohoo]

---

The AP is attempting to join a controller that is NOT supporting the 2700.   Post the complete output to the AP command of "sh ap capwap client rcb".