I'm not sure why you'd want to do this, but the only way to do this that I'm aware of is to clear all config from an AP. If you configure an AP in Prime Infrastructure there is a button down at the bottom that says clear all config and your AP will reset and it will reset to defaults. This is only for one at a time, there is no way that I know of to do it to multiple APs at once.
Thanks Martin. That's about what I thought. (And I'm glad there's no one-stop-shop for defaulting my APs!)
Just for some background on why the heck I'd want to do this...
I would want to do this because I am migrating APs from WLCs with one codebase (184.108.40.206) to WLCs with another codebase (220.127.116.11, recommended by TAC but so was 18.104.22.168), and would like to make it a little less likely for the APs to find their 7.6 controllers after downloading the 7.4 code.
There's also the matter of licensing limits on each WLC, etc. While yes, given time and enough attempts, the APs will settle into a WLC with sufficient licenses, will go to their primary controller and settle into the proper codebase (with the help of manual reboots sometimes), etc, it would be nice to be able to reduce the time and number of attempts here.
In other words, there are plenty of reasons to want to do it; can't think of an argument against it offhand.
I guess for now we'll just set/clear it as we see 'em.
1. If you use Cisco Prime Infrastructure (or WCS) to manage your WLC, you can create a Lightweight AP Configuration Template to specify the Primary Controller Name and IP Address, and to specify a blank value (choose the first blank option in the drop down list) and 0.0.0.0 for the Secondary and Tertiary Controllers. Then you can apply that template to the AP's and it should remove (blank out) the values in those fields.
2. From the WLC CLI, you can run the following commands to blank out the fields:
config ap secondary-base ' ' APHOSTNAME 0.0.0.0
config ap tertiary-base ' ' APHOSTNAME 0.0.0.0
Note that between the quotes there are spaces. The secondary-base command has one space, the tertiary-base command has two spaces (the names have to be unique). While this does not completely blank out the field, the spaces do not resolve to a valid WLC hostname so it has the same effect and the AP ignores the spaces.
Both of these suggestions worked in our environment.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...