Cisco access-points not joining WLC

[Anjali Devi]

We have an issue where APs not joining WLC.  AP is 3500 and WLC is 5508. When we do a manual registration,we do not have any issues. However, this is not happening automatically. I cannot ask the customer to go for manual way, since he has around 70 APs. The APs and WLC get IP from an external DHCP server. All APs are able to ping the WLC and vice-versa.

[Leo Laohoo]

Need more info than this.

Do you have DNS and DHCP option 43 enabled?

What is the firmware of the WLC?

[Anjali Devi]

Hi

DNS and DHCP option is 43 and 60 is enabled?

Firmware version FPGA 1.3, Env 1.6

[w.janarthanan]

Hi Anjali,

Is you AP is AIR-CAP3502I-E-K9 ???

BR

Jana

[Anjali Devi]

Hi Jana,

No the correct PID AIR-CAP3502I-N-K9

[Anjali Devi]

can i have some response on my query.

[w.janarthanan]

Hi,

Is your APs connected via flexconnect mode or local mode, if its through flexconnect mode you will have to add each AP one by one.

BR

Jana

[Anjali Devi]

Hi

its connected via loca mode.

[Leo Laohoo]

Hi
DNS and DHCP option is 43 and 60 is enabled?
Firmware version FPGA 1.3, Env 1.6

Are you asking us a question to answer OUR question?

[Anjali Devi]

sorry. it was my answer...

[Leo Laohoo]

Can you please post the bootup sequence of the WAP?

[Anjali Devi]

When the AP boots and receives an IP address, it sends a discover request. If the discover request reaches WLC it replies back. On receiving this discover reply AP sends a join request and WLC sends a join reply. In our case the AP is sending the Discover. WLC receives it too. However, it ignores it saying:

"*spamApTask0: Apr 18 10:28:23.617: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (105) on interface (13) from AP a4:56:30:5d:e3:30

*spamApTask0: Apr 18 10:28:20.932: %LWAPP-3-DISC_INTF_ERR2: spam_lrad.c:1334 Ignoring discovery request received on a wrong VLAN (105) on interface (13) in L3 LWAPP mode from AP f0:f7:55:39:69:a3"

Also,

We have created Cisco LWAPP- contoller local domain entry in the local DNS Server.

[Leo Laohoo]

*spamApTask0: Apr 18 10:28:20.932: %LWAPP-3-DISC_INTF_ERR2:

Please post the entire bootup process and discovery process.

Note:  I don't know how "old" this output is but look at the time and date.  It's all wrong.

[mrcaldera1]

Have you created the CISCO-LWAPP-CONTROLLER.localdomain entry on the local DNS server?

[Anjali Devi]

When the AP boots and receives an IP address, it sends a discover request. If the discover request reaches WLC it replies back. On receiving this discover reply AP sends a join request and WLC sends a join reply. In our case the AP is sending the Discover. WLC receives it too. However, it ignores it saying:

"*spamApTask0: Apr 18 10:28:23.617: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (105) on interface (13) from AP a4:56:30:5d:e3:30

*spamApTask0: Apr 18 10:28:20.932: %LWAPP-3-DISC_INTF_ERR2: spam_lrad.c:1334 Ignoring discovery request received on a wrong VLAN (105) on interface (13) in L3 LWAPP mode from AP f0:f7:55:39:69:a3"

Also,

We have created Cisco LWAPP- contoller local domain entry in the local DNS Server.