topic Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller in Wireless

Cisco AIR-AP2802I-E-K9 Failing to Join Controller

calluuml — Mon, 05 Jul 2021 17:32:29 GMT

Hi,

We are having an issue where our AP will not join any of our Wireless LAN controllers.

Console output shows;

[*01/18/2019 15:05:13.3086] CAPWAP State: Discovery
[*01/18/2019 15:05:13.3088] Got WLC address 172.16.1.5 from DHCP.
[*01/18/2019 15:05:13.3088] IP DNS query for CISCO-CAPWAP-CONTROLLER.ourdomain.com
[*01/18/2019 15:05:13.3124] Discovery Request sent to 172.16.1.5, discovery type DHCP(2)
[*01/18/2019 15:05:13.3126] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*01/18/2019 15:05:13.3137] Discovery Response from 172.16.1.3
[*01/18/2019 15:05:13.3137] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*01/18/2019 15:05:13.3137] Failed to decode discovery response(status = 4).
[*01/18/2019 15:05:13.3137] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/18/2019 15:05:13.3138] Failed to handle capwap control message from controller - status 4
[*01/18/2019 15:05:13.3138] Failed to process unencrypted capwap packet 0x26fc000 from 172.16.1.3
[*01/18/2019 15:05:13.3138] Failed to send message to CAPWAP state machine, msgId 0
[*01/18/2019 15:05:13.3138] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/18/2019 15:05:13.3138] IPv4 wtpProcessPacketFromSocket returned 4
[*01/18/2019 15:05:13.3139] Discovery Response from 172.16.1.4
[*01/18/2019 15:05:13.3139] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*01/18/2019 15:05:13.3139] Failed to decode discovery response(status = 4).
[*01/18/2019 15:05:13.3139] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/18/2019 15:05:13.3139] Failed to handle capwap control message from controller - status 4
[*01/18/2019 15:05:13.3139] Failed to process unencrypted capwap packet 0x26f6000 from 172.16.1.4
[*01/18/2019 15:05:13.3139] Failed to send message to CAPWAP state machine, msgId 0
[*01/18/2019 15:05:13.3140] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/18/2019 15:05:13.3140] IPv4 wtpProcessPacketFromSocket returned 4

From the log it looks like a version mismatch - https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

The compatibility matrix shows that version 8.2.110.0 is supported and the AP is running 8.5.135.0

cisco AIR-AP2802I-E-K9 ARMv7 Processor rev 1 (v7l) with 1028584/672912K bytes of memory.
Processor board ID XXX
AP Running Image : 8.5.135.0
Primary Boot Image : 8.5.135.0
Backup Boot Image : 8.3.143.0
2 Gigabit Ethernet interfaces
1 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version : 2.4.24

Could somebody point me in the right direction?

Thanks

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Jonas Kalldert — Mon, 10 Jun 2019 14:43:43 GMT

Hello callumlee,

What version are you running on the WLC?

2802E requers the WLC to run at minimum 8.2.110.0.

regards,
Jonas
**Don't forget to rate helpful posts**

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Ambuj M — Mon, 10 Jun 2019 17:37:45 GMT

Looks like CSCvf71074, would recommend you to contact TAC.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Sandeep Choudhary — Tue, 11 Jun 2019 05:27:32 GMT

pasthe the output of the command:

sh sysinfo from WLC

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Leo Laohoo — Tue, 11 Jun 2019 07:23:58 GMT

Post the complete output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time
Initial output shows the AP has the wrong time and date. Make sure the WLC is configured with NTP.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

calluuml — Tue, 11 Jun 2019 07:41:06 GMT

sh sysinfo from one of the WLC, the other is a 9800-CL which doesn't recognise the command.

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.5.135.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
OUI File Last Update Time........................ Sun Sep 07 10:44:07 IST 2014

Build Type....................................... DATA + WPS

System Name...................................... XXXXXX
System Location..................................
System Contact................................... Network Manager
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 172.16.1.3
IPv6 Address..................................... ::
Last Reset....................................... Software reset
System Up Time................................... 224 days 22 hrs 2 mins 37 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh

--More or (q)uit current module or <ctrl-z> to abort
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +38 C
External Temperature............................. +22 C
Fan Status....................................... OK

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 11
Number of Active Clients......................... 434

OUI Classification Failure Count................. 0

Burned-in MAC Address............................ XXXXXXXX
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1

and sh time from the same controller;

Time............................................. Tue Jun 11 08:36:03 2019

Timezone delta................................... 0:0
Timezone location................................ (GMT) London, Lisbon, Dublin, Edinburgh

NTP Servers
NTP Version.................................. 3
NTP Polling Interval......................... 600

Index NTP Key Index NTP Server Status NTP Msg Auth Status
------- ---------------------------------------------------------------------
1 0 172.17.8.21 In Sync AUTH DISABLED
2 0 172.17.8.22 Not Synched AUTH DISABLED

The time is very far off on the AP, but is usually set by the controller.

Thanks

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Leo Laohoo — Tue, 11 Jun 2019 12:09:57 GMT

Post the complete output to the command "sh capwap client rcb".
You may need to upgrade the firmware of the controller because I suspect this is CSCvf71074.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Rich R — Tue, 11 Jun 2019 13:27:10 GMT

It can't be CSCvf71074 because that is fixed in 8.5.110.0 and this WLC is running 8.5.135.0. But upgrading WLC code would address a number of other possible bugs. We've recently seen https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk53499 which also prevents APs joining and despite what the notes say reloading the AP doesn't always help but it is fixed in latest MR candidate which you can get from https://community.cisco.com/t5/other-wireless-mobility-subjects/8-5-mr5-interim-build-availability/td-p/3832744

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

calluuml — Tue, 11 Jun 2019 13:27:58 GMT

That command is not recognised on the WLC for some reason, the AP is also failing to join our new 9800-CL which was built recently with the latest stable release, im guessing it is a problem with the AP or would the bug carry over?

Could we look further into the time mismatch, is setting the time manually possible? I tried to "clock set" command but it was not recognised.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

patoberli — Wed, 12 Jun 2019 14:08:58 GMT

Which version is running on the 9800-CL?
Please note, it first tries to contact 172.16.1.5 and afterwards 172.16.1.4, which is which WLC?

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

calluuml — Thu, 13 Jun 2019 07:33:59 GMT

version on the 9800-CL is 16.10.1e

9800-CL is the 1.5 IP

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Sandeep Choudhary — Thu, 13 Jun 2019 07:45:44 GMT

OK then you need to upgrade the AP software firs5t to : ap3g3-k9w8-tar.153-3.JI3.tar

9800 SW 16.10.1e is equivalent to AirOS 8.8.111.0 and then AP need minimum version of 15.3(3)JI3 to Joiun WLC.

Regards

Dont forget to rate helpful posts

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

RADOSLAV Machaj — Thu, 05 Sep 2019 10:24:21 GMT

hello is this bug also apply for 2800 series access points?

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

Leo Laohoo — Thu, 05 Sep 2019 11:04:53 GMT

It applies to AP2800/AP3800.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

cameronmyers — Thu, 25 Jun 2020 20:05:24 GMT

Ok, I don't want to throw a red herring into this but...

I had this issue with a new install 2802i. The AP booted and connected fine but then started to fail during programing. Same error messages as this and many threads.

I did a capwap erase all on the AP CLI and the AP came up again and connected with no errors.

I changed the AP name from the controller to the one we had chosen for it and it crashed again. Same error messages again.

I cleared the capwap config again and it came back to life and connected once again with no errors.

This time I added the ap group first and then the high availability second with no issues. I then updated the name to something different than we used before with the word test in it. No errors. I changed the name to a more appropriate name but still not the one we used before, still working fine. Sync'd the controller to Prime and all is well.

The original name was 22 characters, the new name is 19 characters. Weird problem is that the original name with 22 characters is the same name as an AP that is online and working but has a 1 at the end instead of a 2.

Running for an hour now with no issues. I don't dare try and go back to the other name.

AIR-AP2802I-B-K9 - ver. 8.5.135.0

5520 controller

Only 1 out of 13 of the same APs did this.

The related bugs listed for this issue all say that 8.5.135.0 is a known fixed version so it shouldn't be happening. But it did.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

cameronmyers — Mon, 13 Jul 2020 17:00:02 GMT

Mine died again. After my fix that got it running it started being bad again. Same issue.

Weird that it is just this AP and not any others. I guess it will have to go back to Cisco. No one seems to have an answer.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

patoberli — Tue, 14 Jul 2020 07:37:30 GMT

And you are still running 8.5.135.0? If yes, first try to upgrade to the latest 8.5 release. If that doesn't help, the unit might be broken (if it only happens to one) and needs to be replaced.

Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller

cameronmyers — Tue, 14 Jul 2020 15:28:20 GMT

Yep, after clearing the CAPWAP config again it completely stopped responding. It gets DHCP and shows up in CDP neighbors but is non-responsive to the cli. Can't get better info until it returns from the site. Starting an RMA.