Users Guide

Table Of Contents
384 | Control Plane Security Dell PowerConnect ArubaOS 5.0 | [User Guide
z Automatic Synchronization: Schedule automatic database backups using the database synchronize period
CLI command in config mode.
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 will have one master controller as its cluster root, and all other master controllers as cluster members.
The master controller operating as the cluster root will create a self-signed certificate, then certify it’s own local
controllers and APs. Next, the cluster root will send a certificate to each cluster member, which in turn certifies
their own local controllers and APs. Since all controllers and APs in the cluster will all have the same trust anchor,
the APs can switch to any other controller in the cluster and still remain securely connected to the network.
Figure 68 A Cluster of Master Controllers using Control Plane Security
To create a controller cluster, you must first define the root master controller and set an IPsec key for
communications between the cluster root and cluster members.
Creating a Cluster Root
To identify a controller as a cluster root via the WebUI:
1. Access the WebUI of the controller you want to become the cluster root, and navigate to
Configuration>Controller.
2. Click the Cluster Setting tab.
3. For the cluster role, select Root.
4. In the Cluster Member IPsec Keys section, enter the switch IP address of a member controller in the cluster.
If you want to use a single key for all member controllers, use the IP address 0.0.0.0.
5. In the IPSec Key and Retype IPSec Key fields, enter the IPsec key for communication between the specified
member controller and the cluster root.
6. Click Add.
7. Optional: repeat steps 4-6 to add another member controller to the cluster.
Note: If you add a new backup controller to an existing controller, the backup controller must be added as the lower priority
controller. If the backup controller is not added 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.