Chapter 12 Common Configuration Examples
162
Aerohive
Expand Firewalls, and enter the following in the IP Firewall Policy section:
From-Access: guest-IP-policy-from-access
This is the policy that you created in
"Firewall Policy" on page 159
.
To-Access: (nothing)
Default Action: Deny
Expand QoS Settings, and enter the following:
Rate Control & Queuing Policy: QoS-Guests
This is the policy that you created in
"QoS Rate Limiting" on page 158
. The HiveAP applies these
rates and scheduling to users that belong to this user profile on an individual basis.
CAC Guaranteed Airtime: 0 (default)
CAC (Call Admission Control) monitors the HiveAP resource load and airwaves for congestion, and
then determines whether to allow additional VoIP calls using SIP (Session Initiation Protocol) or
Vocera services to initiate on that HiveAP. If the HiveAP and airwaves are already over-utilized,
then a new caller is not permitted to start a call. Because this user policy will not be applied to
voice traffic, it is unnecessary to set this.
Policing Rate Limit a/b/g mode (0-54000 Kbps): 2000
Policing Rate Limit 11n mode (0-2000000 Kbps): 2000
The maximum traffic policing rate for the entire user profile is the same as that for an individual
user. By keeping the two rates the same, a single online user is not restricted to a smaller rate than
that of the profile to which he or she belongs. (These rates can be the same as or greater than the
individual user rates.)
Setting a rate limit of 2000 Kbps provides guests with a basic amount of available bandwidth
without interfering with the bandwidth usage of other users, such as employees.
Scheduling Weight: 5
The weight defines a preference for forwarding traffic. It does not specify a percentage or an
amount. Its value is relative to the weights of QoS schedules in other user profiles in the same
WLAN policy.
Because wireless access for guests is mainly a convenience and not a necessity, you assign it a
weight that is low in comparison to the weights of other user profiles to give guests the lowest
priority. In this example, 5 is used. Because this setting is a relative weight, modify it as necessary
based on the weights of the other user profiles present.
Note:
Although HiveAPs apply policing at all times, they only apply scheduling weights when
usage is at maximum capacity.
Содержание access point
Страница 1: ...Aerohive Deployment Guide ...
Страница 7: ...HiveAP Compliance Information 6 Aerohive ...
Страница 13: ...Contents 12 Aerohive ...
Страница 37: ...Chapter 2 The HiveAP 20 ag Platform 36 Aerohive ...
Страница 71: ...Chapter 4 The HiveAP 340 Platform 70 Aerohive ...
Страница 81: ...Chapter 5 The HiveAP 320 Platform 80 Aerohive ...
Страница 105: ...Chapter 8 The High Capacity HiveManager Platform 104 Aerohive ...
Страница 123: ...Chapter 10 Using HiveManager 122 Aerohive ...
Страница 209: ...Chapter 14 Deployment Examples CLI 208 Aerohive ...
Страница 217: ...Appenidix A Country Codes 216 Aerohive ...