WLC 4402 cannot register APs

[akobwaycct]

hey

my wireless network has 20 LAPS,recently my controller lost 11 LAPS,i did a reboot on the controller and the remaining 9 LAPS were also lost.

i have tried several suggestions but nothing has workd

i upgraded the controller from 3.2.119. image to 4.0.219.0.i also changed to LAPS from LAPS to APS and back but nothing seem to work.

does anyone have an idea as to what the problem might be.

[m-geisler]

Hmm, I had a similar problem. Solved it by reverting the controller to 3.2.(whatever).

but first check if the APs are upgrading that takes sometimes longer than the official 5 min.

Good luck

Michael

[sabhasin]

do you see anything on the controller (while running debug lwapp events enable)? How are the APs and the controller connected to the network?

[akobwaycct]

no i don see anything in the controller absolutely nothing,even the laps cannot get a lwapp response from the controller after issueing a lwapp request.

please see the attached diagram of how the laps and the controller are connected to the network.

[mirek.tichy_2]

Hello,

your topology is not trivial. I would say :

1) be sure about propper IP layer configuration - ping from the controller to LAPs

2) what about the controller discovery on LAPs ? If the LAPs know the right conntroller you must see a registration attempts. Try to switch on "debug lwapp events", "debug lwapp packets" and "debug lwapp errors". Best to try on only one LAP.

3) on older converted APs there can be a problem with a certificate. It can be watched on the WLC by "debug pm pki"

I have had LAP registration problems many times but it was always some stupid mistake.

[mstefanka]

You may also check if you have enabled authorization of LAPs against AAA.

Security > AP Policies ...

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_configuration_example09186a00808c7234.shtml

[akobwaycct]

i cannot ping from the controller to any laps because the controller is supposed to assign ip addresses to the LAPS so if the Laps cannot register with the controller then i cannot ping any of them.

i have tried your suggestion at some point but like i said when the lap issues a lwapp discovery it cannot find the controller.

ip configs are ok, that i am sure of beacuse the same config was working before.

[mirek.tichy_2]

For the LWAPP registration the LAP needs to be given by a valid IP address. So there must be a short time period before rebooting the AP has a correct IP address and starts the registration. On console of the LAP you can see it by "show lwapp ip config". Moreover if the WLC is behind router you need properly configured DHCP option 43 or DNS config for the WLC discovering. Can you see the registration requests on WLC's debug lwapp?

[akobwaycct]

the LAP does not get an address i confirmed that,hey recently the IT department change their DHCP server,what is configured in the WLC is now a relay to the DHCP server and the controller is seating behind a cisco 6509.

Do you think it could be the issue of cofiguring DHCP option 43.

[mirek.tichy_2]

Hi,

on the Cisco 2611 router there has to be an "ip helper-address" pointing to the right DHCP. Try another thing. Take one of the LAPs and connect it to the WLC managemnent VLAN on the Cat 6509. In this case you don't need the option 43.