Technical data

254 Meru System Director Configuration Guide © 2012 Meru Networks, Inc.
More QoS Rule Examples
ID : 23
ID Class flow class : on
Destination IP : 10.11.31.115 (this is the client to be rate limited)
Destination IP match : on
Destination IP flow class : on
Destination Netmask : 255.255.255.255
Destination Port : 0
Destination Port match : none
Destination Port flow class : none
Source IP : 0.0.0.0
Source Netmask : 0.0.0.0
Source Port : 0
Source Port match : none
Source Port flow class : none
Network Protocol : 6
Network Protocol match : on
Network Protocol flow class : on
Firewall Filter ID :
Filter Id match : none
Filter Id Flow Class : none
Packet minimum length : 0
Packet Length match : none
Packet Length flow class : none
Packet maximum length : 0
QoS Protocol : other
Average Packet Rate : 0
Action : forward
Drop Policy : head
Token Bucket Rate : 46875
Priority : 0
Traffic Control : on
DiffServ Codepoint : disabled
Qos Rule Logging : on
Qos Rule Logging Frequency : 60
3. Configure Chariot to send a TCP downstream to the client (10.11.31.115) using
the throughput script.
You should see throughput averaging around 3Mbps on Chariot. As a result of this QoS
rule, when the client 10.11.31.115 receives traffic, it will be rate-limited to approx-
imately 3mbps.
Wireless Peer-to-Peer Qos Rules
In general, to create a priority QoS rule for a particular protocol between two IP
addresses, specify the network protocol and then select the match flow for the
protocol. This creates QoS priority for a particular protocol between the IP's.
Prioritize Peer-to-Peer
This particular IP-Based QoS rule prioritizes peer-to-peer traffic generated from
172.18.85.11 and destined to 172.18.85.12.
Testing# show qosrule 11