Filter
Top Products
Configuring QoS Creating Policies
OmniSwitch 6600 Family Network Configuration Guide April 2006 page 24-25
Note. You cannot remove all parameters from a policy condition. A condition must be configured with at
least one parameter.
Deleting Policy Conditions
To remove a policy condition, use the no form of the command. For example:
-> no policy condition c3
The condition (c3) cannot be deleted if it is currently being used by a policy rule. If a rule is using the
condition, the switch will display an error message. For example:
ERROR: c3 is being used by rule ‘my_rule’
In this case, the condition will not be deleted. The condition (c3) must first be removed from the policy
rule (my_rule). See “Creating Policy Rules” on page 24-26 for more information about setting up rules.
If c3 is not used by a policy rule, it will be deleted after the next qos apply.
Creating Policy Actions
This section describes how to configure policy actions in general. Creating policy actions for particular
types of network situations is described later in this chapter.
To create or modify a policy action, use the policy action command with the desired action parameter. A
policy action should specify the way traffic should be treated. For example, it might specify a priority for
the flow, a source address to rewrite in the IP header, or it may specify that the flow may simply be
dropped. For example:
-> policy action Block disposition drop
In this example, the action (Block) has a disposition of drop (disposition determines whether a flow is
allowed or dropped on the switch). This action may be used in a policy rule to deny a particular type of
traffic specified by a policy condition.
Note. Policy action configuration is not active until the qos apply command is entered. See “Applying the
Configuration” on page 24-46.
More than one action parameter may be specified. Some parameters may be mutually exclusive. In addi-
tion, some action parameters are only supported with particular condition parameters. For information
about supported combinations of condition and action parameters, see “Condition/Action Combinations”
on page 24-7. See the OmniSwitch CLI Reference Guide for details about command syntax.
policy action keywords
disposition
priority
minimum bandwidth
maximum bandwidth
maximum depth
maximum buffers
tos
map