Deployment Guide
47
IT Staff User Profile
1. Click
HiveAP Configuration
>
QoS Policies
>
User Profiles
>
(Add button).
The New User Profile dialog box appears.
2. On the General page, enter the following:
•
User Profile Name:
IT
(You cannot include any spaces when defining a user profile name.)
•
User Profile ID:
3
•
Comment:
QoS for the IT staff
3. Click the
QoS
tab, enter the following, and then click
OK
:
•
Entire User Profile Rate Limit:
54000
Kbps (default)
This is the maximum amount of bandwidth that all users belonging to this profile can use. This setting
provides IT staff members with the maximum amount of available traffic.
•
Entire User Profile Weight:
40
Because you want the HiveAPs to favor IT staff traffic over employee and guest traffic, you give this profile
a higher weight than those, but a lower one than that for voice traffic (see
"VoIP User Profile" on page 46
).
•
Per User Rate Limit:
54000
Kbps (default)
This is the maximum amount of bandwidth that a single user belonging to this profile can use. It is the
maximum so that even if only one IT staff member is on the network, he or she can use all the available
bandwidth if needed.
•
Per User Queue Management: Keep all the settings at their default values.
Emp (Employees) User Profile
1. Click
HiveAP Configuration
>
QoS Policies
>
User Profiles
>
IT
> (Clone button).
The Clone User Profile dialog box appears.
2. In the Profile Name field, type
Emp
, and then click
OK
.
The Emp User Profile dialog box appears with the same values you entered for the IT profile, except that the
user profile ID has already been changed to 4.
3. In the General tab, enter the following:
•
User Profile Name: Emp (read only)
•
User Profile ID:
4
Because the ID number for the def-user, VoIP, and IT user profiles are 1, 2, and 3 respectively, enter "4"
here. This number can be any unique number from 4 to 15.
•
Comment:
QoS for employees
4. Click the
QoS
tab, make the following change while keeping all the other cloned settings, and then click
OK
:
•
Entire User Profile Weight:
25
Because you want the HiveAPs to prioritize IT staff traffic first, employee traffic second, and guest traffic
last, you give this profile a weight of 25. This weight is less than that for IT staff traffic (40) and more than
what you are going to assign to guest traffic (5) next. 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, and 40 bytes of IT 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.
Содержание HiveAP 20 ag
Страница 1: ...Aerohive Deployment Guide...
Страница 6: ...HiveAP Compliance Information 6 Aerohive...
Страница 64: ...Chapter 4 HiveManager Examples 64 Aerohive...