Is there a way to join an LAP without entering MAC on controller?

Answered Question
Sep 25th, 2010

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?

I have this problem too.
0 votes
Correct Answer by Stephen Rodriguez about 6 years 1 month ago

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Stephen Rodriguez Mon, 09/27/2010 - 06:39


     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.

robertrusnak Mon, 09/27/2010 - 07:21

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?

Correct Answer
Stephen Rodriguez Mon, 09/27/2010 - 08:07

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.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode