1562I won't join 2504 controller

[Nettech98]

We just purchased a 1562I (AIR-AP-1562I-B-K9) and it won't join our 2504 controller.  The AP has version 8.4.100 and our controller is 8.3.111.  I have also installed the matching AP bundle (hopefully correctly).  This is our first outdoor access point.  Following is an extract from the console (domain info changed to XXX):

===========================

[*08/24/2017 20:30:37.7119] CRIT-MeshLink: Set Root port Mac: 2C:33:11:0E:4B:60 BH Id: 0 Port:0 Device:DEVNO_WIRED0
[*08/24/2017 20:30:37.7123] CRIT-MeshLink: Notify Capwap Link Up: mac: 2C:33:11:0E:4B:60 BH Id: 0 GW_reachable: No Roam: false
[*08/24/2017 20:30:37.7136] driver_wpas:  - wpa_driver_wpas_init
[*08/24/2017 20:30:50.8858] ethernet_port wired0, ip 192.168.3.124, netmask 255.255.255.0, gw 192.168.3.1, mtu 1500, bcast 192.168.3.255, dns1 192.168.3.10, domain XXX.localDOT11_CFG[0] Radio Mode is changed from Bridge to Bridge
[*08/24/2017 20:30:52.4254] DOT11_CFG[1] Radio Mode is changed from Bridge to Bridge
[*08/24/2017 20:30:52.4453] AP IPv4 Address updated from 0.0.0.0 to 192.168.3.124
[*08/24/2017 20:30:52.4585] dtls_init: Use MIC device cert
[*08/24/2017 20:30:52.4589] dtls_init: Use MIC device cert private key
[*08/24/2017 20:30:52.4591]
[*08/24/2017 20:30:52.4591] CAPWAP State: Init
[*08/24/2017 20:30:52.4597]
[*08/24/2017 20:30:52.4597] PNP is not required, Starting CAPWAP discovery
[*08/24/2017 20:30:52.4597]
[*08/24/2017 20:30:52.4599]
[*08/24/2017 20:30:52.4599] CAPWAP State: Discovery
[*08/24/2017 20:30:52.4606] IP DNS query for CISCO-CAPWAP-CONTROLLER.XXX.local
[*08/24/2017 20:30:52.4972] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*08/24/2017 20:30:52.4973]
[*08/24/2017 20:30:52.4973] CAPWAP State: Discovery
[*08/24/2017 20:30:52.4990] Discovery Response from 192.168.3.70
[*08/24/2017 20:56:37.0002] Discovery response from MWAR 'XXX'running version 8.3.111.0 is rejected.
[*08/24/2017 20:56:37.0002] Failed to decode discovery response.
[*08/24/2017 20:56:37.0002] CAPWAP SM handler: Failed to process message type 2 state 2.
[*08/24/2017 20:56:37.0002] Failed to handle capwap control message from controller - status 4
[*08/24/2017 20:56:37.0003] Failed to process unencrypted capwap packet 0x15ca000 from 192.168.3.70
[*08/24/2017 20:56:37.0003] Failed to send capwap message 0 to the state machine. Packet already freed.
[*08/24/2017 20:56:37.0003] IPv4 wtpProcessPacketFromSocket returned 4
[*08/24/2017 20:56:37.1977] set led_patteren 12

=================================

Any help is appreciated!

[Francesco Molino]

Based on the below document 

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

And also based on Cisco download page (8.3.111 differed release), upgrade to at least 8.3.112

Thanks

[Leo Laohoo]

Ok, so try upgrading the controller firmware to 8.3.122.0.

[Quietman]

I had experienced an issue similar to this. The solution in my case was to issue the following command in the console CLI: ap-type capwap

Nothing else worked, including AP policies or MAC lists. As soon as I typed the ap-type command the AP rebooted and joined the controller immediately. It seems the 1562 APs are shipping in either ME mode or a hybrid discovery mode, because when I consoled into the AP it was in Mobility Express setup wizard. SSH or Telnet do not work when it is sitting in this mode, only the console works for this command after rebooting the AP to get it out of ME controller setup mode.

WLC code was 8.3.121 and it appeared that the AP would reach out to the controller but not complete the join process. After a while I think it flips to the ME mode and you can't revert it without running the ap-type command.

I hope this helps.

[helpdesk147]

This command worked on our new 1542is that wouldn't join our WLC. Thank you!

[LUinfra]

Having this same issue and already attempted the ap-type capwap which is not working even after a reboot of the ap device.

Our WLC is running 8.3.141.0 and the aps are running 8.4.100.0.  The previous Engineer stated that the above command worked for him without any issues.

I read and re-read the many comments in this thread and the only current option I see is updating the firmware version.  My question is which one?  The WLC or the AP?  In either case, where can I find the step-by-step instructions to complete?  In addition, IF done on the WLC, I am believing that this will cause an outage?  IF so, how long would this be?

Thank you in advance for your responses.

Sincerely,

Scott Mellring

[Leo Laohoo]

config ap-type capwap

[LUinfra]

We found that the actual command that worked for us is: capwap ap mode local

[tcggg0]

I think Cisco has really dropped the ball on this one.  Brand new 1562's in the ceiling and you need to console into them to fix the issue?  That is not acceptable. 

[thukuthed]

Hi All, i also have the same problem with my new setup WLC 3504 and 1542i-E-K9. Cant even see unjoined Ap on Monitor>Statistics>AP Join. When i monitor the switchport i see the port goes up and down. Kindly assist

AP console messages:

[*04/13/2020 00:21:43.3799] IPv6: ADDRCONF(NETDEV_CHANGE): wired0: link becomes ready
[*04/13/2020 00:21:44.4199] Waiting for uplink IPv4 configuration
[*04/13/2020 00:21:49.4299] Waiting for uplink IPv4 configuration
[*04/13/2020 00:21:54.4299] Waiting for uplink IPv4 configuration
[*04/13/2020 00:21:59.4299] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:04.4299] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:09.4399] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:14.4399] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:19.4399] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:24.4499] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:29.4499] Waiting for uplink IPv4 configuration
[*04/13/2020 00:22:30.4499] Resetting wired0 and restart DHCP client 

[Leo Laohoo]

Is DHCP Option 43 configured properly?