02-15-2019 10:52 AM - edited 07-05-2021 09:52 AM
This is terrible. I had a 5508 WLC that I couldn't access remotely but Prime reported that it was still serving APs. TAC RMA'ed it. Got the replacement, upgraded the code and I could access the GUI. I restored the config from a backup and guess what!?! Cant access the GUI or SSH to it. Yes it's enabled.
Do I have any other choice than to reconfigure this box click by click???
Solved! Go to Solution.
02-27-2019 03:13 PM
When you say manage wireless, you mean your laptop at your desk is attached to the local AP.. attached to WLC X,
is that X the one you can access or the one you can't. I would think that one WLC sees a wired link and the one hosting you sees the wifi link. Which is your problem?
02-27-2019 06:09 PM
02-27-2019 06:45 PM
02-27-2019 06:49 PM
02-17-2019 08:08 AM
Which tells that the AP got an option 43 from WLC but it could not join using that one.
Besides, you should not configure option 60 under the scope. You delete the configuraiton for option 60. option 60 should be included in the DHCP request from the AP.
I never tried it but it would possibly work with ASCII option 43 IP address. Nothing is saying it will not.
HEX format for option 43 has more informaiton than the ASCII because it is in TLV format. ASCII format lacks this information. But no document I found said "using ASCII won't work". But all docs mention only using hex format which is of course the best practice.
You may also conswider other options for discovery than DHCP; DNS for example.
Mapping "CISCO-CAPWAP-CONTROLLE" (without quotes) to your Management IP address on your DNS will get the issue resolved. But DHCP should of course be configured for correct IP address for DNS.
Good luck
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