User's Manual
Table Of Contents
Deployment Guide 85
HIVEMANAGER CONFIGURATION WORKFLOW
HIVEMANAGER CONFIGURATION WORKFLOW
Assuming that you have already installed your HiveAPs, uploaded maps (see "Setting Up Topology Maps" on page 91),
accepted the HiveAPs for management, and decided on the features and settings you want to use, you are now
ready to start configuring the HiveAPs through HiveManager
1
. You can configure numerous objects, some of which
might need to reference other objects. An efficient configuration strategy is to first define any objects that you will
later need to use when configuring others. The typical workflow, shown in Figure 8, proceeds like this:
1. Define network objects. You can then reference them when defining other parts of the configuration. If you do
not plan to use network objects, you can skip this step.
2. Configure various features.
3. Define radio profiles (or use default settings).
4 and 5. Compile the features from step 2 into a WLAN policy, assign the radio profiles and WLAN policy to one or
more HiveAPs, and then push the configurations to the physical devices on the network.
Figure 8 Configuration Workflow
1. When HiveAPs are in the same subnet as HiveManager, they can use CAPWAP (Control and Provisioning of Wireless Access Points)
to discover 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 can use one of several approaches to enable
HiveAPs to connect to HiveManager. For information about these options, see "How HiveAPs Connect to HiveManager" on
page 95.
MAC Filters
User
Profiles
SSIDs
Mgt
Services
AAA
Settings
Radio Profiles WLAN Policy
Hive
HiveManager
Managed
HiveAP
1. If you need to reference network objects in another part of the
configuration, you must define them first. Otherwise, this step
is unnecessary.
4. Compose a WLAN policy by referencing items set in Step 2.
2. Use default settings or configure new settings for various
features that, when combined, constitute a WLAN policy:
• Mobility policies
• Firewall policies
• QoS traffic classification and marking
•MAC Filters
•SSIDs
• User profiles
• Management services (DNS, NTP, SNMP, syslog, location)
• AAA settings (for user authentication using IEEE 802.1X)
• Wireless IDS policy
•Hive
1
2
3
4 5
QoS Traffic
Classification
and Marking
3. Use default settings or define one or more radio profiles.
5. Apply the WLAN policy and radio profiles to one or more
HiveAPs, and then push the configuration to the physical
devices across the network.
MAC
Addresses
Network Objects:
MAC
OUIs
Services
IP
Addresses
Mobility
Policies
IDS
Policy
VLANs
Firewall
Policies