Mobility groups and MAC filtering

Unanswered Question

We have a 4402 controller and we are doing MAC filtering. We have reached the default number of MAC addresses, 512. It has been recommended that we add an additional controller instead of increasing this past the default. Three questions:

1. Is there an increased (enough to impact performance) load placed on the WLC if the limit of MACs is increased, say to the max of 2048?

2. If we add an additional controller, configured in a mobility group, how do we configure the MAC filter to load balance? Or do we have to configure the same MAC table on both controllers? Which leads to....

3. Is there a benefit to adding another controller as far as MAC filtering is concerned?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Roman Rodichev Thu, 07/23/2009 - 19:19

Why not deploy Cisco ACS or Microsoft IAS and do AAA MAC filtering instead of configuring local MAC database?



Roman Rodichev Fri, 07/24/2009 - 07:21

As it stands, you would need to manually replicate internal mac filtering database between two controllers, so you're not gaining much with the second controller. As regards to increasing database size and what effects it will have, I don't have an educated answer for you, sorry.




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