topic the joining problem AP to WLC in Wireless

the joining problem AP to WLC

olgu arabaci — Sun, 04 Jul 2021 08:11:05 GMT

I have 5508 wireless lan controller and 3502 AP. I did all configuration on WLC using the configuration guide. But AP don't join the WLC. AP can assign an IP address and i can ping this IP from WLC. When i connect the AP from console i see the logs below;

*Mar 1 15:36:57.128: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLL ER
Not in Bound state.
*Mar 1 15:37:42.637: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Mar 1 15:37:46.730: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 15:37:46.793: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP addres s 10.17.25.13, mask 255.255.255.0, hostname AP4c00.82e9.a218

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 15:37:53.638: %CAPWAP-3-ERRORLOG: Did not get log server settings from DH CP.

I research similar problems in forums and i implement all they said but i can't solve the problem. there are also DHCP options below;

ddns-update-style interim;

allow bootp;

option space Cisco_LWAPP_AP;

option Cisco_LWAPP_AP.server-address code 43 = string;

subnet 10.17.25.0 netmask 255.255.255.0 {

authoritative;

option routers 10.17.25.1;

option subnet-mask 255.255.255.0;

range dynamic-bootp 10.17.25.10 10.17.25.20;

default-lease-time 300;

class "Cisco-AP-c3500" {

match if option vendor-class-identifier = "Cisco AP c3500";

option vendor-class-identifier "Cisco AP c3500";

vendor-option-space Cisco_LWAPP_AP;

option Cisco_LWAPP_AP.server-address f1:04:0a:11:07:0a; (Management IP : 10.17.7.10 )

}

What could be the cause of problem ??

Re: the joining problem AP to WLC

Rasika Nayanajith — Thu, 31 Oct 2013 23:55:36 GMT

Cannot see AP getting WLC ip from the output you posted.

Try to configure "capwap ap controller ip address 10.17.7.10" on your 3502 & see whether AP get register to your 5508.

If it is the case, then there is something wrong with your DHCP config sending option 43.

If not then we need to troubleshoot that.

Do this first & let us know what you see. Post the complete output of AP console during this AP registration process.

HTH

Rasika

*** Pls rate all useful responses ***

the joining problem AP to WLC

Leo Laohoo — Fri, 01 Nov 2013 00:02:18 GMT

Post the following output:

1. WLC: sh sysinfo;

2. WLC: sh time;

3. AP: sh version;

4. AP: sh inventory; and

5. AP: sh ip interface brief

the joining problem AP to WLC

olgu arabaci — Fri, 01 Nov 2013 07:05:00 GMT

I provide AP get an IP the same network as WLC management interface(10.17.7.0/24). And this time AP join the controller. You(

rasikanayanajith) probably right about DHCP option 43. Because if i try to get an IP to AP from different network (like before 10.17.25.0/24) AP get an IP but not join the controller. When i use different network for APs i probably can't send controller setting on DHCP option. what the cause of that, now i wonder this. Why AP can't join when AP getting IP from diffrent network as WLC management interface. By the way, thanks for your replies...

Re: the joining problem AP to WLC

Rasika Nayanajith — Fri, 01 Nov 2013 08:45:34 GMT

Did you try the requested command while AP is on different network? If not try that and see.

Sent from Cisco Technical Support iPad App

the joining problem AP to WLC

Jose Alberto Badilla Alfaro — Fri, 01 Nov 2013 20:40:31 GMT

Hi Man,

Perhaps you should try to manually set the parameter, just for you to see if the WLC is able to reach, or from the network, and after you see it at the network can try to connect it to the WLC

capwap ap ip address xx.xx.xx.xx xx.xx.xx.xx

capwap ap ip default-gateway xx.xx.xx.xx

capwap ap controller ip address xx.xx.xx.xx

also check cdp neighboar at the switch and the port configuration as well ( Vlan, status, etc).

Good luck!!