Aruba Networks, Inc. Understanding the Aruba Mobility Controller | 16
Aruba Mobility Controllers Validated Reference Design
Masters are responsible for the following functions in the WLAN:
Policy configuration: Configuration in the Aruba solution is split between policy and local
configurations. Local configuration relates to physical interfaces, IP networking, and VLANs,
which are different for each mobility controller. Policy configuration is centered on the operation
of APs and users, including AP settings such as the SSID name, encryption, regulatory domain,
channel, power, and ARM settings. Policy configuration extends beyond APs and also covers
user authentication, firewall policy, mobility domains (IP mobility), IPsec, and system
management. The policy is pushed to all locals in the form of profiles, and profiles combine to
create the configuration for the dependent APs.
AP white lists: Two types of white lists exist in the system, one for RAPs and one for CAPs that
use CPsec. These lists determine which APs can connect to the mobility controllers.
Unauthorized devices are prevented from connecting to the network.
Wireless security coordination: Wireless intrusion prevention activities involve looking for
rogue (unauthorized) APs and monitoring for attacks on the WLAN infrastructure or clients. The
master processes all data collected by Aruba APs and AMs. Instructions to disable a rogue AP
or blacklist a client from the network are issued through the master.
Valid AP list: All mobility controllers in the network must also know all legitimate APs that
operate on the WLAN. These APs must be added to the valid AP list. This list prevents valid APs
from being falsely flagged as rogue APs. This is important when APs that are attached to two
different locals are close enough to hear each other’s transmissions. The valid AP list helps
ARM to differentiate between APs that belong to the network and those that are neighbors.
Unlike traditional wireless intrusion detection system (WIDS) solutions, the master controller
automatically generates the valid AP list without network administrator intervention. All Aruba
APs are automatically learned and added to the list, but valid third-party APs must be added
manually. If more than one master/local cluster exists, AirWave should be deployed to
coordinate APs between clusters.
RF visualization: The Aruba RF visualization tools provide a real-time view of the network
coverage. This information is based on the AP channel and power settings and the data
collected from AMs and APs listening to transmissions during their scanning periods. This
information provides a real-time picture of the RF coverage as heard by the APs.
Location: Locating users in the WLAN is more difficult with mobile clients and IP mobility. The
IP address of the client is no longer synonymous with location. The Aruba WLAN scans off of the
configured channel, so it is possible to hear clients operating on other channels. This information
can then be used to triangulate users and rogue devices to within a small area. This information
is displayed on the master and allows for devices to be located quickly. This speed is critically
important for physical security and advanced services such as E911 calling.
Initial AP configuration: When an AP first boots up, it contacts its master to receive the
configuration generated by the master. The master compares the AP information and
determines its group assignment, and then redirects that AP to the proper local.
Control plane security: When CPsec is enabled, the master generates the self-signed
certificate and acts as the certificate authority (CA) for the network. The master issues
certificates to all locals in the network, which in turn certify APs. If more than one master exists in
the network, the network administrator assigns a single master as the trust anchor for that
network. The trust anchor issues certificates to the other master controllers in the network.