05-09-2007 05:14 AM - edited 07-03-2021 02:02 PM
Hello,
I have a weird problem. I converted a AP1240 to LAP (k9w8.tar). Now they dont connect to the WLCs. I sniffered the traffic to find some clue. the following happens:
1. LAP sends LWAPP-disovery to the IP-Adresses of our 3 WLCs and a broadcast. (192.168.2.6,192.168.2.22 and 192.168.2.38)
2. WLCs acknoledges.
3. AP sends LWAPP-JOIN command to 192.168.2.39.
4. nobody answers (of course, because there is no one on 2.39) and LAP reboots and everything starts over again.
Why tries the LAP to join 2.39? Where can I configure that he tries on of the real 3 (which he knows via DNS, he is sending dicoveries in step 1 to them)
p.k.
05-09-2007 05:39 AM
Hi PK,
Can you confirm what is the ip which you configured for ap-manager interface. Also I believe your APs are in same subnet as controller management interface.
Can you post the output of "debug lwapp event enable"?
Regards,
Ankur
05-09-2007 07:11 AM
Ahh, you were right. 2.39 was the ap-manager interface of the third controller.
Today, I upgraded the Firmware of the 3rd WLC to 4.1.171. Then it worked. It is unclear to me, why it didnt work before, because I didnt change the WLC configs itself, but nevertheless the issue seems to be resolved with the upgrade.
Thanks for your help. p.k.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide