AIR-AP1562I-E-K9 not joining WLC 5508

[mhmservice]

Hi all

I have 2x newly installed AIR-AP1562I-E-K9 that won't join a 5508 controller

I have added AP MACs to the "AP Policy" section of the web interface (never had to do that before for other APs)

"debug capwap errors enable" gives the following (not very helpful):

*spamApTask6: Jun 03 15:43:37.539: [SA] 4c:xx:xx:xx:xx:xx ApModel: AIR-AP1562I-E-K9

CDP on the switch with AP Connected shows as follows:

Device ID: AP4CE1.xxxx.xxxx
Entry address(es):
IP address: 10.x.x.x
Platform: cisco AIR-AP1562I-E-K9, Capabilities: Router Trans-Bridge
Interface: GigabitEthernet0/21, Port ID (outgoing port): GigabitEthernet0
Holdtime : 146 sec

Version :
Cisco AP Software, ap3g3-k9w8 Version: 8.3.143.0
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2014-2015 by Cisco Systems, Inc.

advertisement version: 2
Power drawn: 29.900 Watts
Power request id: 27402, Power management id: 2
Power request levels are:29900 15400 0 0 0
Management address(es):
IP address: 10.x.x.x

Controller running the following software

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.3.143.0
Bootloader Version............................... 1.0.20

Does anyone have any ideas to fix this? Other APs in the site work fine (mix of 1602 and 1702)

The AP is installed in an extremely inaccessible location in a remote branch so console connection isn't an easy option..

[mhmservice]

Thanks for the reply,

Assuming that is the case what are the steps to fix it?

I will try to get someone on site to console to the AP but I can't ask them to do just that as I have to arrange a third party company to assist (site is in a remote country with no on site IT presence)

[Rich R]

Sandeep already provided the command to use above.
1562 usually defaults to mesh out of the box so if you didn't reconfigure them before installation then that is likely the problem like Leo and Sandeep said.

[mhmservice · Accepted solution]

I was affected  by this bug

https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html

Our SHA1 certificate expired in March 2020, I hadn't tried to connect any new APs since then

I worked around it by changing the time on the WLC back to 2019 and the APs joined instantly

I will try to get the fixed firmware mentioned installed

[Rich R]

Good that you finally solved it - had to point a few people towards that FN recently.
It didn't seem like the case for yours because you had said all other APs were working normally :)