Controller Based WLANs

Configuration that are not pushed from a Master Controller to Local Controller

Environment : This article applies to Aruba Mobility Controllers running ArubaOS version 6.0 and Above.

 

Many settings are unique to a controller and therefore are not replicated from a master controller to a local controller. The following settings must be manually configured on a local controller 
 

  • Time zone and daylight savings time settings

  • VPN pools for remote APs and other VPN clients.

  • Controller and IP interfaces. 

  • IP routing and spanning-tree configurations

  • Remote AP whitelist and local-user database values

  • DHCP pools and reservations

  • NAT pools

  • SNMP, NTP, and syslog settings

  • Hostnames, DNS and SMTP servers

  • ACLs applied to ports

  • Certificates

  • RADIUS client details and RADIUS source interfaces

  • Stateful firewall settings

  • Customized captive portal pages and images, and the captive portal redirect address.

 

Note : By default, the local controllers forward the authentication requests for the RAP whitelist and the local user database to the master controller. Therefore, this data does not have to be manually replicated unless the default behavior has been altered. The user table is NOT synchronized, so if an AP fails over to a master from a local or vice versa, that AP will have to re-authenticate.

 

Version History
Revision #:
1 of 1
Last update:
‎06-29-2014 02:35 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.