AP2702i-UXK9 can not join to the c9800 !!

[stan.hung]

Hi, I bought a C9800-L, the version is 17.3.6, because there are several C2702i, but just one is air-ap2702i-uxk9, other APs have already joined the C9800, only this one has been unable to join, In the past, there was a document for reference, but it was for the old WLC. When you encounter C9800, I don’t know if you have encountered it or is there any way to allow air-ap2702i-uxk9 to join C9800?! Thank you

[marce1000 · Accepted solution]

   - Note that 17.9.3 will support these APs too (again) ; Check controller and AP logs when the AP tries to join , the latter usually means the AP boot process. Have a checkup of the 9800 controller configuration with the CLI command show tech wireless ; feed the output into : https://cway.cisco.com/wireless-config-analyzer/
                    Consider this procedure mandatory

 Further on , for the particular AP use these tools for debugging join issues :
                             https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin

 M.
                         

[stan.hung]

Hi :

According to the following log, it is in this infinite loop, and there is a pre-download update to 17.3.6 in the middle. After restarting, such a log keeps appearing~~

*Aug 1 06:47:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.241.64.11 peer_port: 5246
*Aug 1 06:47:10.211: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.241.64.11 peer_port: 5246
*Aug 1 06:47:10.211: %CAPWAP-5-SENDJOIN: sending Join Request to 10.241.64.11
*Aug 1 06:47:10.231: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.241.64.11
*Aug 1 06:47:10.231: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.241.64.11:5246
*Aug 1 06:47:10.231: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 27
*Aug 1 06:47:10.235: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 27
*Aug 1 06:47:10.347: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - EASY_ADMIN is not set, turn off easy admin service!

*Aug 1 06:47:10.347: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - Easy Admin is not enabled, turn it off!

*Aug 1 06:47:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug 1 06:47:11.403: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Aug 1 06:47:11.411: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 1 06:47:12.395: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug 1 06:47:12.403: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Aug 1 06:47:12.431: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 1 06:47:12.439: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug 1 06:47:12.447: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 1 06:47:13.431: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Aug 1 06:47:13.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug 1 06:47:13.467: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 1 06:47:14.467: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug 1 06:47:20.403: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Aug 1 06:47:20.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.241.64.11 peer_port: 5246
*Aug 1 06:47:50.003: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0xE74C104!

*Aug 1 06:48:19.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.241.64.11:5246
*Aug 1 06:48:19.999: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Aug 1 06:48:20.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.241.64.11 peer_port: 5246
*Aug 1 06:48:37.791: %IPV6_ND-6-DUPLICATE_INFO: DAD attempt detected for FE80::2F6:63FF:FE46:C4A0 on BVI1
*Aug 1 06:48:49.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0xE74C104!

*Aug 1 06:49:19.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.241.64.11:5246
Not in Bound state.
*Aug 1 06:50:05.503: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Aug 1 06:50:10.623: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.241.64.86, mask 255.255.255.0, hostname AP00f6.6346.c4a0

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

[Flavio Miranda]

Hi @stan.hung 

 This AP is different from the others? I mean, the partnumber uxk9 ? This is an universal AP and it should not have problem with Country EXCEPT you are in Israel.

 If the AP have the same partnumber as others, factory reset it and try to join after that.

[stan.hung]

Hi @Flavio Miranda 

I am wondering if it is caused by the country code problem~~ Before setting the AP of UXK9, you must follow this article, and will use the Cisco APP, but this APP can no longer be downloaded and used

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/ux-ap/guide/uxap-mobapp-g.html#pgfId-87791

[Leo Laohoo]

What is the status of the AP, is it always in a "Downloading" state? 

If it is, then it is because of FN - 72524 - During Software Upgrade/Downgrade, Cisco IOS APs Might Remain in Downloading State After December 4, 2022 Due to Certificate Expiration which 17.3.6 is in the "affected" list.

[stan.hung · Accepted solution]

Hi @Leo Laohoo :

It has been pre-downloaded and updated to 17.3.6. After restarting, it has been unable to join the WLC, I am wondering if it is caused by the country code problem~~ Before setting the AP of UXK9, you must follow this article, and will use the Cisco APP, but this APP can no longer be downloaded and used

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/ux-ap/guide/uxap-mobapp-g.html#pgfId-87791

[Leo Laohoo]

Someone really needs to read my response carefully because I always phrase my responses short and easy-to-understand. 

[stan.hung]

I forgot to mention, I have updated APSP, the result is the same，Sorry

[Rich R · Accepted solution]

- Are the other APs also -UX?
- Was the AP country primed before you tried to connect it to the 9800?

If the answers are no and no then you can try to RMA the AP it you have it on support and ask Cisco to replace with a standard regulatory domain AP, otherwise bin.
For reference: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvw04567
If other APs are also UX then you can use them to prime the remaining AP as per the guide.

I recommend moving to 17.9.4 - I already have it in lab and will be looking to deploy soon.

[stan.hung]

I'll be testing it, thanks a lot

[JPavonM]

I would recommend you to move to 17.9.3 (or new 17.9.4) to see if that solves the issue.

Cisco has kept support for x700 series from 17.9.3 and new 17.12