policy action
Usage Guidelines
•
Any condition parameters that the hardware supports will be used to classify the traffic; any condition
parameters that are not supported by the hardware will not be used to classify traffic, and the event will
be logged in the QoS log.
•
Bandwidth parameters may be specified when the action is created or may be specified as separate
commands.
•
Use the
qos apply
•
Use the no form of the command to remove a QoS action from the configuration.
•
If the snapshot command is entered after the policy action command is configured, the resulting
ASCII file will include the following additional syntax for the policy action command:
from {cli | ldap | blt}
This syntax indicates how the action was created. The cli and ldap options may be changed by a user
modifying the ASCII file; however, changing this setting is not recommended. The blt option indicates
a built-in action, this setting is not configurable.
Examples
-> policy action action1 accept
Release History
Release 7.1.1; command was introduced.
Related Commands
policy condition
qos apply
show policy action
MIB Objects
alaQoSActionTable
alaQoSActionName
alaQoSActionSource
alaQoSAppliedActionTable
alaQoSAppliedActionName
alaQoSAppliedActionSource
page 26-118
command to activate configuration changes.
Configures a condition associated with the action.
Applies configured QoS and policy settings to the current configuration.
Displays information about policy actions.
QoS Policy Commands
OmniSwitch CLI Reference Guide
March 2011