Aerohive HiveAP 20 ag, Руководство по развертыванию

Страница: 84 / 90

Chapter 6 Deployment Examples (CLI)
84 Aerohive
2. Associate the classifier profiles with the wifi0.1 subinterface and the eth0 interface so that HiveAP-1 can
classify incoming traffic arriving at these two interfaces.
interface wifi0.1 qos-classifier wifi0.1-voice
interface eth0 qos-classifier eth0-voice
By creating two QoS classifiers and associating them with the wifi0.1 and eth0 interfaces, HiveAP-1 can
classify traffic flowing in both directions for subsequent QoS processing; that is, it can classify traffic
flowing from the wireless LAN to the wired LAN, and from the wired LAN to the wireless LAN.
Step 3 Apply QoS on HiveAP-1
1. Create a QoS policy.
qos policy voice qos 5 wrr 20000 90
qos policy voice qos 3 wrr 54000 60
By default, a newly created QoS policy attempts to forward traffic mapped to classes 6 and 7
immediately upon receipt. This immediate forwarding of received traffic is called "strict" forwarding. To
assign strict forwarding to VoIP traffic from phones whose MAC OUI is mapped to class 6, you simply
retain the default (top priority) settings for class 6 traffic. For classes 5 and 3, you limit the rate of
traffic and set WRR (weighted round robin) weights so that the HiveAP can control how to put the
rate-limited traffic into forwarding queues. You use the default settings for class 2 traffic.
When you enter any one of the above commands, the HiveAP automatically sets the maximum
bandwidth for all members of the user group to which you later apply this policy and the bandwidth for
any individual group member. You leave the maximum traffic rate at the default 54,000 Kbps for the
user group. You also leave the maximum bandwidth for a single user at 54,000 Kbps, so that if a single
user needs all the bandwidth and there is no competition for it, that user can use it all.
Also by default, the traffic rate for this policy has a weight of 10. At this point, because this is the only
QoS policy, the weight is inconsequential. If there were other QoS policies, then their weights would
help determine how the HiveAP would allocate the available bandwidth.
The QoS policy that you define is shown in Figure 5 on page 85 . Note that although you did not configure
settings for Aerohive QoS classes 0, 1, 2, 4, and 7, the policy applies default settings to them. The HiveAP
assigns all traffic that you do not specifically map to an Aerohive class to class 2, which uses WRR with a weight
of 30 and a rate of 54,000 Kbps by default. Because nothing is mapped to classes 0, 1, 4, and 7, their settings
are irrelevant.
Note: If the surrounding network employs the IEEE 802.11p QoS classification system (for wired network
traffic) or 802.11e (for wireless network traffic), you can ensure that HiveAP-1 checks for them by
entering these commands:
qos classifier-profile eth0-voice 8021p
qos classifier-profile wifi0.1-voice 80211e