topic Re: Problem with WLC 4400 and LAP1524 in Wireless

Problem with WLC 4400 and LAP1524

jmonsalvez — Sun, 04 Jul 2021 02:18:19 GMT

Hi everyone,

Please we need some help.

Yesterday we have a big problem with our wireless infraestructure. For any reason our WLC4400 made a reboot(or something like that) and ours APs(1524) didn't connect again. We try to find the problem and find in the logs the message : "Controller time base status - Controller is out of sync with the central timebase". We don't know if this message have some relation with the reboot.

Another problem was the authentication of our AP. The APs doesn't authenticated to the WLC, we suppose that was because in the WLC the option of allow clients with dinamic IP enable automactly where the system restart and we have clients with static IP(DHCP Server). It's possible avoid to that feature enable automactly when the system reboot??

Can any help with this issue please.

regargs,

Re: Problem with WLC 4400 and LAP1524

Raul Manzano Barroso — Tue, 19 Oct 2010 18:26:00 GMT

Hi.

First, please make sure your WLC is in time; any wireless infrastructure should be synchronize with a ntp server, first of all because the Ap´s and WLC use certificates to autenticate and register them. Make sure the mac of your MESH AP´s are in you mac-filtering.

Then, if you ap´s not register in your WLC, you can capture the output of the following commands:

- debug capwap events enable

- debug capwap errors enable

With this information, I´m sure we can help you

Best regards.

Re: Problem with WLC 4400 and LAP1524

jmonsalvez — Thu, 21 Oct 2010 12:18:18 GMT

Thanks Raul,

So it is possible that a problem in the synchronize create problems in the authetication and registering of the APs??? why happen this??? It is possible that the controller restart automatic by cause of this problem in the syncronization??? we have all the mac of ours APs in the mac-filtering.

And what about the case of enable automatic dhcp to clients connection when the controller restart. Is there any way to avoid this situation??? We have clients with static IP and we need that they stay connecting all the time.

regards.

Re: Problem with WLC 4400 and LAP1524

Raul Manzano Barroso — Thu, 21 Oct 2010 16:58:55 GMT

For the problems with a wlc out of date:

Q. The lightweight access points (LAPs) do not register with the controller. What might be the problem? I see these error messages on the controller: `Thu Feb 3 03:20:47 2028: LWAPP Join-Request does not include valid certificate in CERTIFICATE_PAYLOAD from AP 00:0b:85:68:f4:f0. Thu Feb 3 03:20:47 2028: Unable to free public key for AP 00:0B:85:68:F4:F0`.

A. When the access point (AP) sends the Lightweight Access Point Protocol (LWAPP) Join Request to the WLC, it embeds its X.509 certificate in the LWAPP message. It also generates a random session ID that is included in the LWAPP Join Request. When the WLC receives the LWAPP Join Request, it validates the signature of the X.509 certificate using the APs public key and checks that the certificate was issued by a trusted certificate authority. It also looks at the starting date and time for the AP certificate validity interval, and compares that date and time to its own date and time.

This problem can occur due to an incorrect clock setting on the WLC. In order to set the clock on the WLC, issue the show time and config time commands.

http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008082c464.shtml

For the other question, sorry, I don´t understand what is the problem Can you explain better?? My english is still poor

Best Regards.

Re: Problem with WLC 4400 and LAP1524

jmonsalvez — Thu, 28 Oct 2010 21:36:04 GMT

Raul,

Thanks for the help.

Don't worry about the other problem. I think is a problem of configurations.

regards.