Controller Based WLANs

What will and will-not get pushed out during whitelist DB sync?

Environment : This article applies to Aruba Mobility Controllers running ArubaOS version 6.3.0.0.

 

Just like Campus AP whitelist, the Remote whitelist records will now be synced across master-local and/or cluster controllers starting from AOS 6.3

Any new controller joining the deployment will learn all CAP and RAP entries from neighbors automatically. However, if it contains some CAP and RAP entries of its own, then they will be propagated to other controllers and essentially both will be merged.

During whitelist DB sync the following attributes of CAP and RAP are synchronized 
 

Campus AP 

AP MAC Address  -  MAC address of a campus AP that should support secure communications to

and from its controller.

Description (Optional) - field to add a brief description of the campus AP.
 

Remote AP

AP MAC Address - Mandatory parameter. Enter the MAC address of the AP.

Username - Enter a username that will be used when the AP is provisioned.

AP Group - Select a group to add the AP.

AP Name - Enter a name for the AP. If an AP name is not entered, the MAC address will be used instead.

Description - Enter a text description for the AP


The Remote-ip field in RAP Whiteist records are local to the controller, They are not synced and are unchanged with sync updates. Local administrators have ability to change such fields manually on local controller.

 

rtaImage.png

 

Also Adding/deleting/revoking a entry on any of local/master/cluster will get synced across all controller and newly Joined controllers with blank entries will not get synced across controllers.

 

Version history
Revision #:
1 of 1
Last update:
‎06-29-2014 06:05 PM
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.