General Controller Procedures And Guidelines; Using Master, Standby Master, And Local Controllers In Aruba Configuration; Pushing Device Configurations To Controllers - Dell PowerConnect W-Airwave Configuration Manual

General Controller Procedures and Guidelines

Using Master, Standby Master, and Local Controllers in Aruba Configuration

AWMS implements the following general approaches in relation to controllers.
Master Controller—This controller maintains and pushes all global configurations. AWMS pushes
configurations only to a master controller.
Standby Controller—The master controller synchronizes with the standby master controller, which
remains ready to govern global configurations for all controllers should the active master controller fail.
Local Controller—Master controllers push local configurations to local controllers. Local controllers
retain settings such as the interfaces and global VLANs.
AWMS is aware of differences in what is pushed to master controllers and local controllers, and
automatically pushes all configurations to the appropriate controllers. Thin AP provisioning is pushed to
the controller to which a thin AP is connected.
You can determine additional details about what is specific to each controller by reviewing information on
Groups > Aruba Config
the
standby master controller.

Pushing Device Configurations to Controllers

When you add or edit device configurations, you can push device configurations to controllers as follows:
Make device changes on the
Make devices changes on the
A device must be in
If you click Save and Apply when a device is in Monitor mode, this initiates a verification process in which AWMS
advises you of the latest mismatches. Mismatches are viewable from the APs/Devices > Mismatched page.
Additional Audit and Group pages list mismatched status for devices.
N O T E
Normally, devices are in
configuration changes in
general steps when implementing configuration changes for devices in
1. Make all device changes using the
Config
pending configuration changes that have not been pushed to the controller and APs.
2. Review the entire set of newly mismatched devices on the
3. For each mismatched device, navigate to the
changes as desired.
4. Once all mismatched device configurations are verified to be correct from the
use the
This instructs AWMS to push the device configurations to the controller.
5. As desired, return devices to
controllers.
40 | Using Aruba Configuration in Daily Operations
page, and the
Device Setup > Aruba Configuration
Groups > Aruba Config
Manage
mode to push configurations in this way.
Monitor
mode. It may be advisable in some circumstances to accumulate several
Monitor
mode prior to pushing an entire set of changes to controllers. Follow these
Save and Apply
page. Click
Modify Devices
link on the
Monitor
Groups > Monitor
page for any specific AP that lists its master and
page and click
Device Setup > Aruba Configuration
as you complete device-level changes. This builds an inventory of
APs/Devices > Mismatched
APs/Devices > Audit
Groups > Monitor
page to place these devices into
mode until the next set of configuration changes is ready to push to
AirWave Wireless Management Suite | Configuration Guide
Save and Apply
page and click
Save and Apply
.
Monitor
mode:
Groups > Aruba
page and the
page.
page to audit recent configuration
APs/Devices > Audit
Management
.
page,
mode.