Technical data

Configuring QoS Rules With the Web UI

More About the Match Checkbox and Flow Class Checkbox

The two checkboxes Match and Flow Class operate independently from each other;

they perform two different functions. Match will almost always be used because

checking this box indicates that the setting on the left must match - this sets the

matching criteria for the QoS rule. You can check more than one matching criteria.

Matching is the first phase of QoS rule execution - see the green box in Figure 35.

After criteria are matched, the action phase of the QoS rule is executed. This phase

is enclosed in the orange box in Figure 35. Here are the directions that describe what

to do with the matched packet from phase 1, Matching. For example, the rule can

capture the packet from a named source and drop it. Action is phase 2 of QoS rule

execution.

The Flow Class column is all about rate limiting. If a rule involves rate limiting, the

actions Traffic Control and Token Bucket Rate must have been turned on. When the

QoS rule executes traffic control, it looks at the check marks in the flow class

column. If there are no check marks at all, the rate limiting is applied to everything.

If Destination, Source, or Network Protocol have Flow Class checked, the following

happens:

 Destination Flow Class - Each destination flow is limited to the rate.

 Source Flow Class - All source flows combined must be less than or equal to the

rate.

 Network Protocol Flow Class - Any data transported using this protocol is limited

to the rate.