09-25-2010 08:40 AM - edited 07-03-2021 07:13 PM
I have an unusual customer setup where the lightweight APS are installed temporarily to any number of sites for a specific job and then removed. The APS come from a commmon distribution inventory as required and may not be paired with the same controller everytime they are used. The number of access point per distribution site will be huge.
So basically, I need to be able to configure the controller so that it accepts/authorizes any LAP request to join without having to create a MAC filter list on each Controller.
Any ideas?
Solved! Go to Solution.
09-27-2010 08:07 AM
AH, ok. For MESH you do have to have the MAC in the AP Policy list, no other way to do it at this time.
09-27-2010 06:39 AM
Rob,
You never have to put the MAC address of a LAP on the WLC, unless it has a SSC or you are running MESH. If you are using a AP that came as a LAP, it should have a MIC installed, and would not need the MAC address entry in the AP Policy list.
However, if you enable AP authorization, then you need the MAC entry for a MIC AP, in either the local AP Policy list, or in AAA. Some companies do use this feature, as it will keep AP's that are not yours from joining the WLC.
09-27-2010 07:21 AM
Sorry, I did forget that the APs are being used for a portable indoor MESH network. There is no intrusion concerns as the network only hooks up to a single PC long enough to perform the task and then the network is torn down.
So in a MESH network is there a way to allow a MAP or RAP join the controller without the MAC address being entered in the MAC FIlter list?
09-27-2010 08:07 AM
AH, ok. For MESH you do have to have the MAC in the AP Policy list, no other way to do it at this time.
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