Mobility Conductor Configuration Hierarchy

Mobility Conductor (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 Conductor and managed devices is set up from a centralized point, thereby simplifying and streamlining the configuration process. Mobility Conductor consolidates all-conductor, single conductor-multiple local, and multiple conductor-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 conductor controller which propagates those to its local controllers. The local configurations are applied to the conductor or the local controller directly.

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