Saving Rules - Alcatel OmniSwitch 6800 Series Network Configuration Manual

Configuring QoS
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
Rules With Compatible Actions
More than one rule may have the same condition. For example, two Layer 3 rules may have the same IP
address condition but different actions. If the actions are compatible, both rules will be applied to the flow,
regardless of the precedence settings. In this example, the rules are created with the default precedence (0)
value.
-> policy condition X source ip 10.10.2.3
-> policy action Y priority 7
-> policy action Z maximum bandwidth 10m
-> policy rule Rule1 condition X action Y
-> policy rule Rule2 condition X action Z
In this example, when a flow comes into the switch and matches source IP address 10.10.2.3, the switch
will apply both policies (Rule1 and Rule2) to the flow. On the OmniSwitch 6800, a source IP address may
be combined with priority and maximum bandwidth actions at the same time, so both rules are used. See
the "Policy Action Combinations Table" on page 21-7
Rules With Conflicting Actions
If the actions are in conflict, however, the switch will apply only the rule with the highest precedence. For
example:
-> policy condition X source ip 10.10.2.3
-> policy action W priority 5
-> policy action Z minimum bandwidth 10m
-> policy rule Rule1 condition X action W
-> policy rule Rule2 condition X action Z
In this case, a source IP address condition may be combined with a priority action or a minimum band-
width action but not both at the same time. Since these actions are in conflict, the rule with the highest
precedence will be applied instead. In this case, both rules have the same precedence value (the default,
since no precedence is specifically configured). The rule that was configured first (Rule1) is considered to
have the highest precedence and will be used for the flow. See the
page 21-7 to identify conflicting actions.

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 or copy running-config working
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
OmniSwitch 6800 Series Network Configuration Guide
command) and saved to the working directory (using the
command). By default, rules are saved.
to identify compatible actions.
"Policy Action Combinations Table" on
November 2004
Creating Policies
write memory
page 21-29