Aruba, a Hewlett-Packard Enterprise company, unveiled their new Mobile First Platform last week and I had a front row seat as one of the Mobility Field Day Live delegates. Aruba’s announcement was made a day prior to our session, so it was pretty exciting to discuss such a fresh topic. The foundation that Aruba is creating here is impressive and the implications are tremendous, especially if we look at extrapolating this in the near future.
Aruba announced the release of AOS version 8.0, which marks the first major overhaul of the code in quite some time. This release is at the center of Aruba’s Mobile First Platform and is designed to handle the next ten years of wireless, which is quite an ambitious goal as the near future has 802.11ax (aka Ten Gigabit Wi-Fi). Aruba highlighted that the intelligent layer of services required to run networks today is reaching its limits on controllers, so they have created a new alternative in the form of a Mobility Master that can run these intelligent services on behalf of the controller hardware. The Aruba Mobility Master has been virtualized so that it can run on an x86 virtual machine in VMWare (KVM coming soon with version 8.0.1). This new role replaces the now legacy Master Controller so most environments will benefit from a reduced amount of hardware on-site and can leverage investments already made for the new architecture where desired. Also of interest for most is that there is zero cost for these virtual machines, the only thing that matters is the number of access points are being managed. The primary tradeoff between a controller-based and virtualized infrastructure today is throughput as the VM-based controllers do not have hardware encryption modules and as a result they cap out around 4-5 Gbps.
Aruba has also introduced a new UI with AOS 8.0, which is a welcome feature as it had been fairly complicated for a new user. The new UI brings some much needed features such as simplified profiles, tab completion for profile names in the CLI, multithreading in the CLI, etc.
In-Service Upgrades are also new with the advent of AOS 8.0 and the Mobility Master. The increased compute and storage allow for services that now reside on the Mobility Master to be upgraded and impact the environment immediately without requiring an upgrade to access points or controller infrastructure.
Watch more on AOS8 via the Tech Field Day YouTube Channel.
Zero Touch Provisioning
Included in the move to a Mobility Master, is Aruba Zero Touch Provisioning which allows the Mobility Master to handle all configuration for controllers throughout the environment. Additionally, the previous requirement for the Mobility Controller and Access Controllers to be running the same version of code has been removed. The Mobility Master must run the latest code supported in the environment, but will be backwards compatible with older versions of code running on the controllers. This feature will greatly benefit risk adverse customers to quickly take advantage of the new features in administrative buildings, but maybe roll out slowly to a hospital or manufacturing site.
The Multizone architecture allows for SSIDs to terminate to multiple controllers, creating an end-to-end encrypted session from client to controller when in tunneled mode. Terminating SSIDs on different controllers extends beyond the data flow and into how the AP is managed. Controller 1, as the primary, gets to set all of the AP settings (IP address, dhcp, etc..). Controller 2 gets to set only the settings for SSID 2. An admin of controller 2 cannot see any of the info for controller 1 including SSIDs, security types, auth servers, users, etc.
Aruba AOS8 brings controller clustering to the table. All elements in the cluster must be running the same code and be part of the same family (e.g. All 72XXs running 8.0 code). State information is maintained for clients and access points with a designated backup controller within the cluster. The clusters also participate in user load balancing. Primary and Backup controller per user is maintained in the cluster and will be shared with AirWave later in the year. This is useful across all customer types, but especially those with very large campuses (e.g. higher education or Fortune 500 headquarters, etc.). Clusters scale to 12 controllers with 72XX series and 4 with 70XX controllers.
Aruba Clarity allows the access points to associate to another access point and run synthetic tests from the “client AP” to the Clarity server, effectively building a baseline and providing tremendous visibility especially for remote sites. Clarity Live tracks DHCP and DNS requests and responses in real-time to profile the typical health of the network. Clarity Synthetic allows for RF performance testing, iPerf, web page loads to a URL (Salesforce, etc.) Upcoming features that were hinted at but not confirmed include scheduling and wired line monitoring and testing.
Another feature of AOS8 is Aruba’s new AirMatch feature that enables better channel reuse. This feature is important as legacy radio management was designed for a previous era of wireless networks. In today’s high capacity world that needs to support users and things the old way of doing things is not good enough. AirMatch looks at the system as a whole to maximize channel reuse and capacity on a daily basis and determines based on a day of usage what the best wireless combination of radios include. Advanced users will be able to tune AirMatch functionality to meet their needs from the command line, but this will be obscured from the GUI to protect users from causing harm.
The Mobility Master will have the context aware APIs that exist with Aruba’s Location Engine (ALE) to enable integrations with other systems via REST or published to other resources using a ZeroMQ to move that data to a database. Configuration APIs have also been enabled to allow APIs configure the network, SSIDs, etc.
Enhancements have been added that enable categorization of applications and grouping of applications. For instance, a group called “Students” or “Nurses” could be created simplifying management. Custom applications are now supported and AppRF definitions are now treated like antivirus updates and can be updated without impact to the network.
In all I was impressed with what was announced for this release. Our delegate panel kept asking for more, but when you look at what has been accomplished, our requests were in line with what you’d expect this roadmap to look like as it unfolds. The shift to an API driven infrastructure is exactly where the world needs to be heading and abstracting software from hardware is inline with every other major shift in the industry. I am looking forward to the APs themselves running microservices in the future that can be upgraded, restarted, etc. with no impact to end users—it seems to be an inevitability at this point. This Mobile First Platform is well thought out and perfectly aligned with the automated and intelligent future that we are all looking for as it allows us to focus on the core business and offers much needed agility.