Mobility Master Configuration Hierarchy

Mobility Master (ArubaOS 8.x.x.x) uses a centralized, multi-tier architecture under a brand new UI User Interface. that provides a clear separation between management, control, and forwarding functions. The entire configuration for both the Mobility Master and managed devices is set up from a centralized point, thereby simplifying and streamlining the configuration process. Mobility Master consolidates all-master, single master-multiple local, and multiple master-local deployments into a single deployment model.

Whereas, the architecture of ArubaOS 6.x and earlier versions consist of a flat configuration model that contains global and local configurations. The global configurations are applied to the master controller which propagates those to its local controllers. The local configurations are applied to the master or the local controller directly.

Mobility Master takes the place of a master controller in the network hierarchy. Mobility Master oversees controllers that are co-located (on-premises local controllers or off-campus branch office local controllers). All the controllers that connect to Mobility Master act as managed devices.

Starting from ArubaOS, the master controller mode deployment model is not supported on any controller platform.