Table of Contents
Advertisement
H
M
IVE
ANAGER
Assuming that you have already installed your HiveAPs, uploaded maps (see
and decided on the features and settings you want them to use, you are now ready to start configuring the HiveAPs
2
through the HiveManager
reference when configuring other objects. The typical workflow, shown in
1. Define network objects. You can then reference them when defining QoS traffic classification and marking
settings, SSID profiles, and hive profiles. If you do not plan to use network objects, you can skip this step.
2 and 3. Configure various features and compile them into a device group.
4 and 5. Define radio profiles (or use default settings) and hive profiles. You can define radio profiles at any point in
the configuration process because they do reference any other previously defined object. Similarly, if you do
not make use of MAC filters in the hive profile configuration, you can define those at any point in the process.
6. Assign the device group, radio profile, and hive profile to one or more HiveAPs and then push the configurations
to the physical devices on the network.
Figure 9 Configuration Workflow
1
Network Objects:
Services, MAC Addresses, MAC OUIs
2
QoS Classification
and Marking
User Profiles
(QoS Policy
+
User Profile ID)
3
Device Group
(User Profile + SSID + VLAN)
2. When HiveAPs are in the same subnet as the HiveManager, they can use CAPWAP (Control and Provisioning of Wireless Access
Points) to discover the HiveManager on the network. CAPWAP works within a layer-2 broadcast domain and is enabled by
default on all HiveAPs. If the HiveAPs and HiveManager are in different subnets, then you must configure the DHCP server to
include option 225 in its responses to DHCPDISCOVER and DHCPREQUEST messages from the HiveAPs. This option provides
either the IP address or domain name of the HiveManager. If it provides the domain name, then you must also configure
resource records for the HiveManager on the DNS server that is authoritative for that domain. With this information, the
HiveAPs can contact the HiveManager.
Deployment Guide
C
ONFIGURATION
. When using the HiveManager to configure HiveAPs, you first define objects that you later
HiveManager
MAC Filters
SSID
AAA
Profiles
Settings
Management
Service Set
(DNS, NTP,
Syslog)
4
5
Radio
Profiles
H
IVE
W
ORKFLOW
"Setting Up Topology Maps" on page
Figure
1. If you need to reference network objects in QoS traffic
classifications, SSID profiles, and hive profiles, you must define
them first. Otherwise, this step is unnecessary.
2. Use default settings or configure new settings for various
features that, when combined, constitute a device group:
• QoS traffic classification and marking
• User profiles (a combination of QoS policy settings—mainly
traffic forwarding rates and schedules—and a user profile ID)
• SSID profiles
• Management service set (DNS, NTP, and syslog)
• AAA settings (for user authentication using IEEE 802.1X with
RADIUS)
3. Compose a device group by referencing elements set in Step 2.
4. Use default settings or define one or more radio profiles for the
HiveAP to use.
5. Define a hive profile to which the HiveAP will belong.
6. Apply the device group, radio profiles, and hive profile to one or
more HiveAPs, and then push the configurations to the physical
devices across the network.
6
Hive
Profile
M
C
ANAGER
ONFIGURATION
9, proceeds like this:
HiveAP
W
ORKFLOW
37),
31
Advertisement
Table of Contents
