Controller Based WLANs

How to prevent a new controller from overwriting the RAP whitelist in on the master controller?
Q:

Why is RAP whitelist-db getting modified when we add new controller to the cluster?

 

 



A:

When we add a new controller with non-empty RAP whitelist-db to an existing Master-Local setup, it will push its whitelist-db contents to the master which will push it to the whole cluster. This can cause issues if the new controller has entries for same RAPs which are already present on whitelist-db on the master. 

 

Issue: The new controller  will push its whitelist-db to the cluster. If the new controller already has an entry for a RAP present in master whitelist, but with a different ap-group, it will be over-written and the RAP will be assigned to a new AP-group. 

 

1. RAP white-list is synchronized between all controllers in a cluster automatically. This cannot be disabled. We need not execute "write memory". 

2. RAP white-list can be changed from any controller in the cluster. The change will be pushed to all other controllers automatically. 

3. Before adding a new controller to the cluster, make sure that it doesn't have any conflicting RAP entries. 

4. As a best practice, we can purge all the entries on the new controller before adding it to the cluster:

 

#whitelist-db rap purge

 

 

Version History
Revision #:
2 of 2
Last update:
‎06-15-2015 05:14 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.