04-18-2017 07:07 AM - edited 07-05-2021 06:52 AM
Hi There,
I have a 2504 WLC that is currently running 5 x 3702i and 1 x 1532. Today I received 6 x 1552H (AIR-CAP-1552H-E-K9) that I also need to join to the controller.
I activated the relevant licences, and confirmed I have 6 unused licenses available.
When I try to add one of the 1552Hs, it refuses to join - I can see it in the Monitor > Statistics > AP Join section of the WLC's web interface, and have added its MAC address in Security > AAA > MAC Filtering.
The detail in Monitor > Statistics > AP Join shows the APs status as "Not Joined" - under Discovery Phase Statistics both requests sent and received show as 2, and there's today's date next to "Last Successful Attempt Time" - but everything else is blank/0.
I've attached the text of the console from the AP when it boots/tries to join - if that's of any help, if there's any more info I can provide please let me know.
Can anyone help with this?
Regards, Lee.
Solved! Go to Solution.
04-19-2017 08:33 AM
Ahh.. yes switches are recommended. :)
Thanks for sharing your experience as well are all learning everyday.
William Kuczmera
04-18-2017 09:48 AM
04-18-2017 09:52 AM
Also, here is a nice little tidbit i could see myself missing out of the deployment guide.
http://www.cisco.com/c/en/us/td/docs/wireless/technology/mesh/8-2/b_mesh_82/Connecting_the_Cisco_1500_Series_Mesh_Access_Points_to_the___.html#ID4755
William Kuczmera
04-18-2017 10:24 AM
If he is running 3700 I would assume he is on 7.6 or better code.
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html#c1
Here is a list of examples with debugs of aps that cant join and why. AP isn't showing much detail. I would do a debug capwap events and PKI and see what that shows.
04-19-2017 02:01 AM
Thanks for your replies gents, the WLC is on 8.2.141.
I ran the sh int command, and that only returned one MAC address - which is the one I added to the filter list - the exact text was "BVI1 is up, line protocol is up
Hardware is BVI, address is 2c31.2470.7be0 (bia 2c31.2470.7be0)"
BUT.... Here's the strange thing - it has now joined successfully, some 6 hours after I last touched it! I left it connected up in my office last night, and the WLC reports the AP joined around 11pm, the last thing I did before I left at 5pm was restart both the WLC and the AP.
So I have another 5 of them to try - I'll try and get those to connect today before I mark this thread as solved.
Thanks again for all your help.
Lee.
04-19-2017 07:35 AM
Thanks for explaining the outcome Lee.
William Kuczmera
04-19-2017 07:45 AM
Soooo.... I tried joining the rest of the APs today - still no joy... until...
I unplugged the AP from the front ports of the WLC and plugged it into a nearby switch - worked straight away. Odd that the first one managed to join plugged into that port - even if it did take 6 hours - and as far as I remember, the APs that were previously joined to the WLC were plugged into its front ports.
You live. you learn!
Thanks once again for your assistance.
Regards, Lee.
04-19-2017 08:33 AM
Ahh.. yes switches are recommended. :)
Thanks for sharing your experience as well are all learning everyday.
William Kuczmera
04-19-2017 07:44 AM
Soooo.... I tried joining the rest of the APs today - still no joy... until...
I unplugged the AP from the front ports of the WLC and plugged it into a nearby switch - worked straight away. Odd that the first one managed to join plugged into that port - even if it did take 6 hours - and as far as I remember, the APs that were previously joined to the WLC were plugged into its front ports.
You live. you learn!
Thanks once again for your assistance.
Regards, Lee.
04-18-2017 10:45 PM
Paste the output of the command:
sh sysinfo from WLC
Regards
Dont forget to rate helpful posts
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