Aruba Product Portfolio and Architecture
The Aruba Product Portfolio and Architecture domain checks that you can place Aruba's hardware, software, and management options in the right design. Expect questions on controller-based versus controller-less WLANs, gateways, AP modes, and where Aruba Central fits.
Controllers, gateways, and APs
- Aruba Mobility Controllers run ArubaOS and can be hardware appliances or virtual appliances. In ArubaOS 8, the Mobility Master is the management and control hierarchy; managed controllers forward client traffic.
- Aruba gateways provide the data plane and control plane for ArubaOS 10/Central deployments, including tunneled or bridged traffic, firewall roles, and VPN termination.
- Access points range from Wi-Fi 5/6/6E indoor and outdoor models to specialized models. They can run as controller-managed APs, Instant APs, or Central-managed AOS 10 devices.
Operating models
- Controller-based: APs terminate to a controller or gateway; configuration and firmware are pushed from the controller; useful for centralized policy and roaming.
- Instant AP: a cluster of APs elects a conductor (virtual controller) that holds configuration and coordinates the cluster. No dedicated controller appliance is required.
- ArubaOS 10 with Central: APs and gateways are onboarded to Aruba Central; configuration is cloud-managed, with gateways providing the overlay and policy enforcement where needed.
- Aruba switches and ClearPass extend the portfolio: switches provide wired access and PoE; ClearPass provides AAA, policy, and guest services.
Management planes
- Aruba Central is the cloud management platform for monitoring, configuration, firmware, and AIOps.
- AirWave is the legacy on-premises management platform; it remains relevant in some installed environments.
- Local management uses the WebUI, CLI, and REST API. NetEdit provides template-based switch configuration in some deployments.
Worked example
A 12-AP branch needs local survivability and minimal on-site hardware. An Instant AP cluster fits: one AP becomes conductor, the others join, and the cluster keeps working if the conductor fails and a new one is elected. If the customer wants cloud visibility and centralized policy, ArubaOS 10 with Central and a gateway may fit better, but it adds subscription and gateway requirements. The reasoning is to match scale, redundancy, and management model, not just pick the newest product.
Traps that cost marks
- Mixing up Mobility Master with a data-plane forwarding controller.
- Assuming the Instant AP conductor is a separate hardware appliance.
- Expecting Central to manage devices without onboarding and a subscription.
- Forgetting that gateways are needed for tunneled AOS 10 designs.