While we generally categorize AeroHive as a “WLAN Switch” manufacturer, their product model does not quite fit the standard mold. AeroHive’s collaborative control solution is built on intelligent access points that provide the functionality of a centrally-controlled WLAN switching environment without the central controller. This fully-distributed architecture becomes more important as WLAN traffic increases with the advent of the higher capacity 802.11n radio link. There have been concerns with designs that pass all traffic through a central controller, that the controller itself might become a major capacity chokepoint.AeroHive’s collaborative distributed traffic handling eliminates that concern, and should also reduce delay and jitter for WLAN voice traffic.
AeroHive’s announcement involved a number of enhancements to their basic architecture along with the addition of a line of 802.11n-capable access points. First, the cooperative control architecture can now support wireless bridging. They have long supported mesh-extensions as well as the traditional wired AP connections though AeroHive’s VP of Product Management Adam Conway is quick to point out that they are not looking to compete with the likes of Firetide, Strix, Motorola-Mesh Networks or the other providers of mesh-based solutions that are designed to cover entire metropolitan areas.
According to Stephen Philip, Sr. Director of Marketing, AeroHive’s basic collaborative architecture is based on what is essentially a “wired-mesh”, so the addition of wireless mesh is a natural extension. One interesting twist on the AeroHive solution is that their wired access points can use the mesh capability as a back-up. If the wired connection to a dual-radio access point fails, the AP can drop client access on one band (typically the 5 GHz 802.11a band) and use the mesh capability on that channel as a back-up for the wired connection. The different coverage pattern produced by the MIMO-based the 802.11n radio also adds value in their collaborative control structure.
AeroHive also announced a new Guest Access Appliance. Guest services have been an ongoing concern in enterprises with the result that many organizations simply refuse to support any form of guest access; this is a real annoyance to those of us who are regular visitors in those facilities. AeroHive’s new solution provides the ability for a receptionist or security guard to provide each visitor with unique credentials when they check in. Those credentials will allow them policy-based(e.g. visitor, visiting employee, contractor) access to WLAN services for a specified period of time. It also allows the network manager to identify usage with a particular individual, and to cancel those privileges (i.e. deauthenticate the user) instantly if that becomes necessary.
They also announced a location tracking capability that incorporates AeroScout’s location tag and device location solution in their HiveManager management system.
On the 802.11n front, they announced three different dual-radio (i.e. 2.4 GHz/5 GHz) access points that will support 802.11n. The standard and industrial-strength indoor models (HiveAP 320 and 340) are due out in July, and the outdoor model (HiveAP 380) is due in 4Q08. All will be capable of 3x3 transmit chain MIMO (for the significance of that, see my piece The Big News in WLANs: 802.11n from March 2008) using the Atheros DFS II chip set.
AeroHive also has some interesting approaches to one of the current problems with 802.11n, supporting the more power hungry 802.11n access points over standard 802.3af Power over Ethernet (PoE). Siemens made a splash in March with the announcement of the first 802.11n APs that could operate over standard PoE. AeroHive adds a few new twists to that.
They claim that in most cases the AeroHive 802.11n-capable APs should run on standard PoE. However that claim is predicated on the assumption that most PoE feeds provide more than the nominal 15.6W and that most Ethernet drops are less than 100m.
With the AeroHive implementation, if the supplied wattage drops below the required threshold, the device can reduce its power requirements by shifting from 3x3 to 2x3 MIMO operation. The AeroHive APs can also support dual 100 Mbps or 1 Gbps wired Ethernet interfaces; with dual 100 Mbps feeds, they can use link aggregation to provide a 200 Mbps capacity to the AP, possibly eliminating the need to upgrade the wired connection to 1 Gbps. In either dual feed option, the PoE can be supplied over both interfaces, essentially providing redundant power feeds lessening the likelihood the device will have to resort to power saving tactics. What’s more, those two interfaces can be connected to two different LAN switch modules (i.e. “dual homing”) thereby providing a redundant transmission path as well as a redundant power feed.
Conclusion
AeroHive can boast a network architecture that sets them apart from the rest of managed WLAN solutions, but there is still a concern that they showed up at the managed WLAN party a little too late to have an impact. They first emerged in May 2007 when Aruba, Meru, Trapeze, Xirrus, and of course, Cisco, were all well established. New and interesting architectures attract attention, but if the customers are already committed to other products, that merits you an honorable mention in the “Shoulda’, Woulda’, Coulda” hall of fame.
AeroHive makes a strong case for their pricing model however, and if the customer hasn’t committed as yet, money talks. Conway argues that there are lots of customer networks that have yet to upgrade from the first generation “fat APs”, so there are lots of potential customer networks still in play. More importantly, as AeroHive’s solution does not require a costly central controller (and their APs are priced at virtually the same level as the other guys’ “thin APs), they can deliver a managed solution for a far better price than the majors. Clearly this announcement shows that AeroHive is committed to stay in the game, and incorporating 802.11n and these other capabilities into their collaborative control architecture, certainly helps build their case.