AP2802 cannot join WLC

[Rps-Cheers]

Hi everyone,

i have met a issue that is AP2802 cannot join WLC.

AP model:AIR-AP2802I-H-K9

software:8.3.143.0

WLC release:8.3.143.0

AP get the ip address by DHCP. the log as below:

ethernet_port wired0, ip 10.1.1.30, netmask 255.255.255.0, gw 10.1.1.254, mtu 1500, bcast 10.1.1.255, dns1 10.1.2.11, dns2 192.168.3.11, domain cn.daliang.comDOT11_DRV[1]: set_channel Channel set to 36

There are some abnormal message:

[*12/06/2018 22:00:40.8805] CAPWAP State: Discovery
[*12/06/2018 22:00:40.8854] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

after i config the WLC sysname and ip address,also have these abnormal message：

[*12/06/2018 22:03:17.8061] Discovery Request sent to 192.168.2.100, discovery type STATIC_CONFIG(1)
[*12/06/2018 22:03:17.8070] Discovery Request sent to 192.168.2.101, discovery type STATIC_CONFIG(1)
[*12/06/2018 22:03:17.8071] Got WLC address 192.168.2.101 from DHCP.
[*12/06/2018 22:03:17.8104] Discovery Request sent to 192.168.2.100, discovery type STATIC_CONFIG(1)
[*12/06/2018 22:03:17.8112] Discovery Request sent to 192.168.2.101, discovery type STATIC_CONFIG(1)
[*12/06/2018 22:03:17.8121] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

Could you help me to reslove this issue.

Thanks.

[Leo Laohoo]

Post the COMPLETE output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time;
3. AP: sh version and
4. AP: sh ip interface brief

[Rps-Cheers]

Hi Leo,
Thanks for your response.
For AP:
AP08EC.F655.45C7#sho ip int brief
Interface IP-Address Method Status Protocol Speed
wired0 10.1.1.30 DHCP up up 1000
wired1 unassigned unset down down n/a
wifi0 unassigned unset administatively down down n/a
wifi1 unassigned unset administatively down down n/a
srcr6 unassigned unset up up n/a


AP08EC.F655.45C7#sho version
Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c) of the Commercial
Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

This product contains some software licensed under the
"GNU General Public License, version 2" provided with
ABSOLUTELY NO WARRANTY under the terms of
"GNU General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

This product contains some software licensed under the
"GNU Library General Public License, version 2" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Library
General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

This product contains some software licensed under the
"GNU Lesser General Public License, version 2.1" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Lesser
General Public License, version 2.1", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html

etah_CCO/label/barbados]3), [wnbu-bld-lnx8:/san/BUILD/workspace/83MR4_Repost_Che--More--
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Mon Jun 14 20:21:32 PDT 2018

ROM: Bootstrap program is U-Boot boot loader
BOOTLDR: U-Boot boot loader Version 2013.01-gad8bd06 (Sep 28 2017 - 17:03:04)

AP08EC.F655.45C7 uptime is 0 days, 0 hours, 8 minutes
Last reload time : Thu Dec 7 22:01:30 UTC 2018
Last reload reason : unknown

cisco AIR-AP2802I-H-K9 ARMv7 Processor rev 1 (v7l) with 1030640/706976K bytes of memory.
Processor board ID FGL2250A0Q4
AP Running Image : 8.3.143.0
Primary Boot Image : 8.3.143.0
Backup Boot Image : 0.0.0.0
2 Gigabit Ethernet interfaces
2 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version :

Base ethernet MAC Address : 08:EC:F6:55:45:C7
Part Number : 0-000000-00
PCA Assembly Number : 800-105672-01
PCA Revision Number : A0
PCB Serial Number : FGL2250A0Q4
Top Assembly Part Number : 800-105672-01
Top Assembly Serial Number : FGL2250A0Q4
Top Revision Number : A0
Product/Model Number : AIR-AP2802I-H-K9

I cannot access wlc at this time,i just know the software is 8.3.143.0 of wlc.There are some AP2802I have joined in WLC.

[cmarva]

not sure offhand what the H regulatory domain is, but you do have the appropriate country code enabled on the WLC, correct?

[Rps-Cheers]

Yes，the country code is correct on WLC.

[Leo Laohoo]

I want to see the output from the WLC.

[patoberli]

AP and WLC are not in the same network. Are the required ports open between the two networks?
Can you try the AP in the same VLAN as the WLC ap-management address?

[Rps-Cheers]

thanks for your reply,

i can't do that put the ap in the same VLAN as the WLC ap-management address.I have some other APs also in this vlan,but they are working well，i don't know why the ap always stuck in "Discovery Request sent to 192.168.2.251, discovery type STATIC_CONFIG(1)"

[patoberli]

Please provide:
1. WLC: sh sysinfo;
2. WLC: sh time;
Also, what is the ap-management IP address of the WLC? Is it the one the client tries to connect to?

[Rps-Cheers]

I don't get the WLC "show sysinfo" and "show time" info.
Ap-management ip of wlc is 192.168.2.100 and 192.168.2.101.I want to make ap connect to wlc2504 directly next time.To check ap if work well or not !

[patoberli]

In that case your AP is probably wrongly configured.

It logged this here:

Discovery Request sent to 192.168.2.251

That means you have either the wrong WLC address hard configured on the AP, or it gets it by DHCP or DNS. 

[fsedanoc]

It seems you're not sending the controller IP on DHCP, so the AP is trying other methods - And not getting right controller IP from any.

For some reason there's a static config of 192.168.2.100 and 192.168.2.101 on your AP. You can see is sending join request there, but since the controller is another IP and another subnet it can't be found.

You have several options:

- set up controller IP on DNS on on DHCP

- Manually set controller ip:

On the AP, go to enable mode and type the following command:

capwap ap primary-base wlc <ip address of your controller>

That should make the AP join the controller. Please post the output if this does not work.

Thanks,

[Rps-Cheers]

Hi all,
Thanks for your reply,i have connected ap2802 to another switch,it can be work well,but we must config wlc's ip address on ap2802 for join wlc.We also have some ap1602 and ap2702,they can join to wlc after obtain ip address.So i don't know whether there are some limitation of ap2802.At a same switch,other aps can work normal,ap2802 cannot work as them,and need config a ip address of wlc....

[patoberli]

It depends on which discovery process you use to join and if the AP is in the same VLAN as the AP-Management Interface.

See here for the possible variants an AP will discover a WLC: https://community.cisco.com/t5/wireless-mobility-documents/joining-process-of-an-cisco-access-point/ta-p/3149279

Which variant have you chosen?

[Rps-Cheers]

OK ,got it,thanks for your help.
I config the dhcp with option43,AP can get wlc's ip address,and send discovery to wlc,ap2700 and ap1600 can work well,but ap2800 cannot work normal.i don't know how to confirm the L2 or L3 discovery process..