Extreme Networks ExtremeWare XOS 11.3, Manual

Page: 384 / 698

CLEAR-Flow
ExtremeWare XOS 11.3 Concepts Guide
384
CLEAR-Flow Rule Actions
CLEAR-Flow rules specify an action to take when the rule is triggered and can optionally specify an
action to take when the expression is false. Because more than one action can be taken in a single rule,
the collection of actions is referred to as an action list.
The actions that can be taken are:
●
Permit/Deny
●
QoS Profile
●
Mirror
●
SNMP Trap
●
Syslog
●
CLI
Additionally, the SNMP trap, syslog, and CLI rule actions can use keyword substitution to make the
rule actions more flexible. The keyword substitutions are described at the end of the rule action
descriptions. See the section,
“Keyword Substitution” on page 385 , for more information.
The following sections describe the different rule actions.
Permit/Deny
This action modifies an existing ACL rule to permit or block traffic that matches that rule.
To change an ACL to permit, use the following syntax:
permit <ACLRuleName>
To change an ACL to deny, use the following syntax:
deny <ACLRuleName>
QoS Profile
This action modifies an existing ACL rule to set the QoS profile for traffic that matches that rule.
To change the ACL to forward to QoS profile <QPx>, use the following syntax:
qosprofile <ACLRuleName> <QPx>
For example:
qosprofile acl_rule_1 QP3
Mirror
This action modifies an existing ACL rule to mirror traffic that matches that rule, or to stop mirroring
that traffic. The mirroring port must be enabled when mirroring on an ACL rule is turned on. This
could be configured earlier, or use the CLI action to execute CLI commands to configure mirroring at
the same time.
To change the ACL to mirror traffic, use the following syntax:
mirror [add|delete] <ACLRuleName>