
Configuring QoS Creating Policies
OmniSwitch 6800/6850/9000 Network Configuration Guide June 2006 page 26-31
• Software and hardware resources are allocated for rules associated with a validity period even if the
validity period is not active. Pre-allocating the resources makes sure the rule can be enforced when the
validity period becomes active.
Disabling Rules
By default, rules are enabled. Rules may be disabled or re-enabled through the policy rule command using
the disable and enable options. For example:
-> policy rule rule5 disable
This command prevents rule5 from being used to classify traffic.
Note that if qos disable is entered, the rule will not be used to classify traffic even if the rule is enabled.
For more information about enabling/disabling QoS globally, see “Enabling/Disabling QoS” on
page 26-13.
Rule Precedence
The switch attempts to classify flows coming into the switch according to policy precedence. Only the rule
with the highest precedence will be applied to the flow. This is true even if the flow matches more than
one rule.
Precedence is particularly important for Access Control Lists (ACLs). For more details about precedence
and examples for using precedence, see Chapter 27, “Configuring ACLs.”
How Precedence is Determined
When there is a conflict between rules, precedence is determined using one of the following methods:
• Precedence value—Each policy has a precedence value. The value may be user-configured through
the policy rule command in the range from 0 (lowest) to 65535 (highest). (The range 30000 to 65535
is typically reserved for PolicyView.) By default, a policy rule has a precedence of 0.
• Configured rule order—If a flow matches more than one rule and both rules have the same prece-
dence value, the rule that was configured first in the list will take precedence.
Specifying Precedence for a Particular Rule
To specify a precedence value for a particular rule, use the policy rule command with the precedence
keyword. For example:
-> policy rule r1 precedence 200 condition c1 action a1
Saving Rules
The save option marks the policy rule so that the rule will be captured in an ASCII text file (using the
configuration snapshot command) and saved to the working directory (using the write memory
command or copy running-config working command). By default, rules are saved.
If the save option is removed from a rule, the qos apply command may activate the rule for the current
session, but the rule will not be saved over a reboot. Typically, the no save option is used for temporary
policies that you do not want saved in the switch configuration file.
To remove the save option from a policy rule, use no with the save keyword. For example:
-> policy rule rule5 no save
Comentarios a estos manuales