Users Guide

135 | Control Plane Security Dell Networking W-Series ArubaOS 6.4.x| User Guide
Purging the Master or Local Controller Whitelist
There is no need to purge a master controller whitelist during the course of normal operation. If, however, you
are removing a controller from the network, you can purge its controller whitelist after it has been
disconnected from the network. To clear a local controller whitelist entry on a master controller that is still
connected to the network, select that individual whitelist entry and delete it using the delete option.
In the WebUI
To purge a controller whitelist:
1. Navigate to Configuration > Controller.
2. Select the Control Plane Security tab.
3. To clear the Local Controller whitelist: In the Local Switch List For AP Whitelist Sync section, click
Purge.
Or,
4. To clear the Master Controller whitelist: In the Master Switch List For AP Whitelist Sync section, click
Purge.
In the CLI
To purge a controller whitelist:
(host) #whitelist-db cpsec-master-switch-list purge
(host) #whitelist-db cpsec-local-switch-list purge
Working in Environments with Multiple Master Controllers
This section describes the configuration steps required in a multiple master controllers network.
Configuring Networks with a Backup Master Controller
If your network includes a redundant backup master controller, you must synchronize the database from the
primary master to the backup master at least once after all APs are communicating with their controllers over a
secure channel. This ensures that all certificates, IPsec keys, and campus AP whitelist entries are synchronized
to the backup controller. You should also synchronize the database any time the campus AP whitelist changes
(APs are added or removed to ensure that the backup controller has the latest settings).
Master and backup controllers can be synchronized using either of the following methods:
l Manual Synchronization: Issue the database synchronize command in enable mode to manually
synchronize databases from your primary controller to the backup controller.
l Automatic Synchronization: Schedule automatic database backups using the database synchronize
period command in configuration mode.
If you add a new backup controller to an existing controller, you must add the backup controller as the lower priority
controller. If you do not add the backup controller as a lower priority controller, your control plane security keys and
certificates may be lost. If you want the new backup controller to become your primary controller, increase the
priority of that controller to a primary controller after you have synchronized your data.
Configuring Networks with Clusters of Master Controllers
If your network includes multiple master controllers each with their own hierarchy of APs and local controllers,
you can allow APs from one hierarchy to failover to any other hierarchy by defining a cluster of master
controllers. Each cluster has one master controller as its cluster root, and all other master controllers as cluster
members. The master controller operating as the cluster root creates a self-signed certificate, then certifies its