
Aerohive provides a controller-less architecture that distributes the data-forwarding and control-plane functions to
the HiveAPs. The HiveAPs operate together as a cooperative system in order to implement controller
functionality. Aerohive provides a network planner that is not as sophisticated as the AirMagnet Planner (i.e., it
does not perform auto-AP placement, multi-floor designs, or 3D modeling), but it is free and provides a low-cost
way to scope a WLAN design.
Aerohive's HiveManager application is delivered as a dedicated appliance, as a VMware virtual appliance, or as a
cloud-based service. The Control and Provisioning of Wireless Access Points (CAPWAP) protocol (see Request
for Comments [RFC] 5415) is the management protocol that the HiveManager uses to communicate with the
HiveAP. The network administrator must open firewall port 12222 for CAPWAP. The HiveManager provides a
device and site hierarchical view of the network (see Figure 2). Provisioning is assisted by the ability to create
provisioning policies that can be reused for different WLANs. The system supports HiveAP load balancing but
does not support band steering.
Aerohive was one of the first vendors to support an ATF and an SLA capability. The SLA enables administrators
to set SLA parameters (e.g., minimum throughput) for groups of users. The system monitors the network for SLA
violations using a feature called performance sentinel. If violations are found, the Aerohive airtime scheduling
engine will automatically re-allocate airtime in order to bring stations back into SLA compliance.
The Aerohive private PSK feature makes it easy to deploy unique PSKs to clients in order to encrypt client traffic
without the use of 802.1X. This is important in environments where 802.1X deployment is complex or not
possible (e.g., guest access, industrial handheld devices, or dual-mode phones).
Figure 2: Aerohive HiveManager
The diagnostic system can quickly find a user through a comprehensive search capability. In the client dashboard,
an association history shows where a client has been previously associated as well as where it is currently
associated. HiveManager calls this collection of client/AP associations a “session.” HiveManager stores
historical-session statistics that include client/AP airtime consumption, client/AP throughput, and roaming
history. HiveManager also provides current client location on a map, but it does not provide that information
historically.
Network administrators will rely on the reporting system and error logs to diagnose problems. The system cannot
integrate client problem diagnosis with location (i.e., show where the user was located over time and how network
events at that location may have affected the user). In addition, the system does not support spectrum analysis or
classification.
Aruba Networks
14
BURTON GROUP 7090 Union Park Center Suite 200 Midvale · Utah 84047 · P 801.566.2880 · F 801.566.3611 · www.burtongroup.com
Comentarios a estos manuales