08-24-2017 05:14 PM - edited 07-05-2021 07:35 AM
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!
08-24-2017 05:21 PM
@Nettech98 wrote:
[*08/24/2017 20:56:37.0002] Discovery response from MWAR 'XXX'running version 8.3.111.0 is rejected.
Upgrade the firmware of the controller to, say, 8.3.122.0.
08-24-2017 05:27 PM
08-24-2017 05:34 PM
As long as I'm upgrading, is there a reason I shouldn't go to 8.4.x or 8.5.x?
Is the AP bundle file required for this AP?
Thanks!
08-24-2017 05:56 PM
08-24-2017 05:39 PM
Hi
There're several things that can block an app to join your wlc.
Under security tab, ap policy, have you activated mic cert to join your wlc? Otherwise you'll need to add the ap mac address.
Did you validate the country code?
Thanks
PS: Please don't forget to rate helpful answers and mark as accepted answer if this solves your issue
08-24-2017 05:45 PM - edited 08-24-2017 05:46 PM
MIC cert was already activated, but I had also tried adding the AP to the MAC filtering list, with no change in outcome.
I didn't 'validate country code', but it is a B model. How would one validate that?
Thanks.
08-24-2017 05:56 PM
Is it your first universal ap?
Have you already done the priming?
If not, take a look here:
https://www.cisco.com/c/en/us/td/docs/wireless/access_point/ux-ap/guide/uxap-mobapp-g.html#52524
Thanks
PS: Please don't forget to rate helpful answers and select add correct answers if this solved your issue
08-24-2017 06:00 PM
@Francesco Molino wrote:
Is it your first universal ap?
There is no such thing as a "universal AP" or "universal Regulatory Domain" for the 1800/2800/3800 and 1540/1560/1570.
The "universal AP" or "universal Regulatory Domain" has temporarily been suspended after 1700/2700/3700 APs.
08-24-2017 06:06 PM
08-24-2017 06:29 PM
I don't think it needs priming as it's a B model - AIR-AP1562I-B-K9. Right?
08-24-2017 05:57 PM
@Nettech98 wrote:
I didn't 'validate country code', but it is a B model. How would one validate that?
Post the complete output to the command "sh sysinfo".
08-24-2017 06:43 PM - edited 08-24-2017 06:44 PM
On the AP or the controller? I only seem to have access to the GUI on the controller remotely now....
08-24-2017 06:49 PM
@Nettech98 wrote:
On the AP or the controller? I only seem to have access to the GUI on the controller remotely now....
The controller. I want to see what country codes are enabled on the WLC.
08-24-2017 07:10 PM
Based on the GUI, the only country code enabled is US
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide