Extreme Networks ExtremeWare XOS 11.3, Manual

Page: 377 / 698

Adding CLEAR-Flow Rules to ACLs
ExtremeWare XOS 11.3 Concepts Guide
377
}
then {
<actions>;
}
}
Or you can specify an optional
else
clause:
entry <CLFrulename> <match-type> {
if { <match-conditions>;
}
then {
<actions>;
} else {
<actions>;
}
}
In the CLEAR-Flow rule syntax, the <CLFrulename> is the name of the rule (maximum of 31
characters). The <match-type> specifies whether the rule is triggered when any of the expressions that
make up the conditions are true (logical OR), or only when all of the expressions are true (logical AND).
The <match-type> is an optional element. The <match-conditions> specifies the conditions that will
trigger the rule, and how often to evaluate the rule. The <actions> in the
then
clause is the list of
actions to take when the rule is triggered, and the optional
else
clause <actions> is the list of actions to
take after the rule is triggered, and when the <match-conditions> later become false.
NOTE
When you create an ACL policy file that contains CLEAR-Flow rules, the CLEAR-Flow rules do not have any
precedence, unlike the ACL entries. Each CLEAR-Flow rule specifies how often it should be evaluated. The order of
evaluation depends on the sampling time and when the CLEAR-Flow agent receives the counter statistics. The order
of the CLEAR-Flow rules in the policy file does not have any significance.
The rule match type, rule match conditions, and rule actions are discussed in these sections:
●
CLEAR-Flow Rule Match Type on page 377
●
CLEAR-Flow Rule Match Conditions on page 378
●
CLEAR-Flow Rule Actions on page 384
CLEAR-Flow Rule Match Type
The match type is optional. There are two possible choices for the match type:
●
match all—All the match expressions must be true for a match to occur. This is the default.
●
match any—If any match expression is true, then a match occurs.
NOTE
The match type was first available for CLEAR-Flow in ExtremeWare XOS 11.2.