User's Manual

Chapter 8 HiveManager Configuration Examples
134 Aerohive
These weights skew the rate at which the HiveAPs forward queued traffic using the WRR (weighted
round robin) scheduling discipline. Roughly, for every 5 bytes of guest traffic per second, a HiveAP
forwards 25 bytes of employee traffic, 40 bytes of IT traffic, and 60 bytes of VoIP traffic. These
numbers are not exact because HiveAPs also have internal weights per class that also affect the amount
of traffic that a HiveAP forwards.
Unregistered-Guests profile
Although the Unregistered-Guests user profile is required for the configuration of the "guest" SSID using
a captive web portal, the HiveAP never applies the QoS settings for this user profile because it never
forwards traffic from unregistered guests.
WLANpolicy-hq2
This WLAN policy is for all the HiveAPs in Building 2 at the corporate headquarters depicted in Figure 1 on page 89.
Because this policy consists of nearly identical elements to those in WLANpolicy-hq1, you clone the first WLAN
policy and simply change the WLAN policy name and description, and the hive in the configuration.
Click Configuration > WLAN Policies > (check box) WLANpolicy-hq1 > Clone, change only the following, and
then click Save:
• Name: WLANpolicy-hq2
•Description: HiveAPs in Bldg 2 at HQ
•Hive: Hive2
WLANpolicy-branch1
This WLAN policy is for all the HiveAPs at the branch site depicted in Figure 1 on page 89. Because this policy
consists of nearly identical elements to those in WLANpolicy-hq1 and WLANpolicy-hq2, you can clone either policy
and simply change the WLAN policy name and description, and the hive in the configuration.
Click Configuration > WLAN Policies > (check box) WLANpolicy-hq2 > Clone, change only the following, and
then click Save:
• Name: WLANpolicy-branch1
•Description: HiveAPs at the branch site
•Hive: Hive3