Aerohive HiveManager Configuration Workflow

Now that the Aerohive HiveAPs have been provisioned so they can discover and connect to a HiveManager management server, let's dive into how HiveManager handles configuration workflow, object definition, and nesting. This will serve as a foundation to prepare us to deploy an initial configuration to our HiveAPs.

The HMOL dashboard shows a new access point is connected

Initial Configuration State
Log into the HiveManager dashboard to get started. If you're using Aerohive's cloud management service, connect to HiveManager Online (HMOL) at https://myhive.aerohive.com and login using your supplied account credentials. From the "Navigate myHive" splash page, select "HiveManager Online" to access the management console. Once there, you should see the new access point listed in the Dashboard.

Navigating over to the Monitor - HiveAPs section, you can see that the access point connection details. You can also get to this page by clicking the "Number of New APs" hyperlink from the Dashboard.

The HiveAP monitor page shows the access point connection details

On this screen, notice that the AP is currently connected (green chain-link), the connection is secured (green padlock), and it is in Portal mode which integrates directly with the Ethernet network, as opposed to a Mesh Point that uses a wireless backhaul into the network through other mesh points or a portal.

Hovering over the red triangle in the audit column displays the pop-up message telling you that no configuration has been pushed to the AP yet. The red triangle alerts administrators that the current configuration on the AP does not match the desired configuration based on HiveManager templates assigned to the AP. Two green squares in the audit column would indicate that the configuration matches the defined template and no action is necessary.

HiveManager Configuration Workflow
Before jumping into the configuration, it's important to understand the workflow used within the system to define configuration items and how items relate to one another. Many enterprise wireless vendors implement a logical nesting, or roll-up, of foundational configuration items into larger groupings / profiles which then are applied to the equipment. This allows for creation of multiple profiles and easier testing, verification, and deployment.

The HiveManager configuration workflow consists of the following configuration items, nesting relationships, and profile objects which are then assigned to individual HiveAPs:

It is readily apparent from this workflow that configuration of four main objects is required:

1. User Profiles
2. SSIDs
3. WLAN Policies
4. Managed HiveAP Settings

Now that we have an understanding of the logical workflow and object nesting within HiveManager, we are prepared to define and deploy a working configuration to our HiveAPs.

Cheers,
Andrew