Technical data

Configuring QoS Rules With the Web UI
© 2012 Meru Networks, Inc. Configuring Quality of Service 233
If you are also using a QoS protocol detector, you must match the network
protocol with the type of QoS protocol. Use the following network protocol and
QoS protocol matches:
— UDP: SIP
— TCP: H.323v1 or SIP
11. In the Firewall Filter ID field, enter the filter-ID to be used (per-user or per-ESS),
if Policy Enforcement Module configuration is enabled (optional feature). This ID
must be between 1 and 16 alphanumeric characters.
12. In the Packet minimum length field, specify the size of the minimum packet
length needed to match the rule. (Valid range: 0-1500.)
13. In the Packet maximum length field, specify the size of the maximum packet
length needed to match the rule. (Valid range: 0-1500.)
14. In the QoS Protocol list, select one of the following:
— SIP
— H.323v1
— Other
— None
For capture rules, the QoS protocol determines which QoS protocol detector
automatically derives the resources needed for the flow (implicitly). Select Other
if you want to specify the resource requirements for matched flows explicitly. The
QoS protocol value is ignored for non-capture rules.
15. In the Average Packet rate box, type the average flow packet rate. The rate can
be from 0 through 200 packets/second.
16. In the Action list, select the action the rule specifies:
— Forward: A flow is given an explicit resource request, bypassing the QoS
protocol detector and regardless of whether a QoS protocol was specified.
— Capture: The system, using a QoS protocol detector, analyzes the flow for its
resource requirements.
— Drop: The flow is dropped.
17. In the Drop Policy list, select one of the following:
— Head: New packets that arrive after the queue has reached its maximum length
are allowed in the queue, and old information in the queue is replaced with
the new information.
— Tail: New packets that arrive after the queue has reached its maximum length
are dropped.
18. In the Token Bucket Rate box, type the rate (in Kbps or Mbps, depending on the
option checked) at which tokens are placed into an imaginary token bucket. Each
flow has its own bucket, to which tokens are added at a fixed rate. To send a
packet, the system must remove the number of tokens equal to the size of the
packet from the bucket. If there are not enough tokens, the system waits until
enough tokens are in the bucket.