Alcatel-Lucent 6850-48 Guida Di Rete

Pagina di 1162
Configuring QoS
Creating Policies
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
page 40-37
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 
.
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 
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 
th
 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 
 command) and saved to the working directory (using the 
command 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
To reconfigure the rule as saved, use the policy rule command with the save option. For example:
-> policy rule rule5 save
For more information about the configuration snapshotwrite memory, and copy running-config 
working
 commands, see the OmniSwitch AOS Release 6 Switch Management Guide and the OmniSwitch 
CLI Reference Guide.
For more information about applying rules, see 
.