CLEAR-Flow
ExtremeWare XOS 11.3 Concepts Guide
378
CLEAR-Flow Rule Match Conditions
In a CLEAR-Flow rule, the
<match-conditions>
portion consists of one to four expressions, an optional
global-rule
statement, and an optional
period
statement:
entry <CLFrulename> <match-type> {
if { <expression>;
<expression>;
<expression>;
<expression>;
global-rule;
period <interval>;
}
then {
<actions>;
} else {
<actions>;
}
}
In the following example, the CLEAR-Flow rule
cflow_count_rule_example
will be evaluated every ten
seconds. The actions statements will be triggered if the value of counter1 (defined earlier in the ACL
policy file) is greater than 1,000,000:
entry cflow_count_rule_example {
if { count counter1 > 1000000 ;
period 10 ;
}
then {
<actions>;
}
}
The global-rule statement is optional and affects how the counters are treated. An ACL that defines
counters can be applied to more than one interface. In the original release of CLEAR-Flow, however, any
counters used in an expression were only evaluated for that particular interface that the CLEAR-Flow
rule was applied to. Beginning with the ExtremeWare XOS 11.2 release, you can specify the global-rule
statement so that counters are evaluated for all the applied interfaces. For example, if a policy that
defines a counter is applied to port 1:1 and 2:1, a CLEAR-Flow rule that used the global-rule statement
would sum up the counts from both ports. Without the global-rule statement, the CLEAR-Flow rule
would only look at the counts received on one port at a time.
The
period <interval>
statement is optional and sets the sampling interval, in seconds. This
statement specifies how often the rule is evaluated by the CLEAR-Flow agent. If not specified, the
default value is 5 seconds.
NOTE
In ExtremeWare XOS 11.1 only one expression was allowed per CLEAR-Flow rule.
There are five CLEAR-Flow rule expressions: count, delta, ratio, delta-ratio, and rule. All of these
expressions check the values of counters to evaluate if an action should be taken. The counters are
either defined in the ACL entries that are defined on the switch, or are the pre-defined CLEAR-Flow
Summary of Contents for ExtremeWare XOS 11.3
Page 20: ...Contents ExtremeWare XOS 11 3 Concepts Guide 20...
Page 25: ...1 Using ExtremeWare XOS...
Page 26: ......
Page 38: ...ExtremeWare XOS Overview ExtremeWare XOS 11 3 Concepts Guide 38...
Page 58: ...Accessing the Switch ExtremeWare XOS 11 3 Concepts Guide 58...
Page 146: ...Configuring Slots and Ports on a Switch ExtremeWare XOS 11 3 Concepts Guide 146...
Page 218: ...Status Monitoring and Statistics ExtremeWare XOS 11 3 Concepts Guide 218...
Page 240: ...Virtual LANs ExtremeWare XOS 11 3 Concepts Guide 240...
Page 248: ...Virtual Routers ExtremeWare XOS 11 3 Concepts Guide 248...
Page 278: ...Access Lists ACLs ExtremeWare XOS 11 3 Concepts Guide 278...
Page 288: ...Routing Policies ExtremeWare XOS 11 3 Concepts Guide 288 entry deny_rest if then deny...
Page 344: ...Security ExtremeWare XOS 11 3 Concepts Guide 344...
Page 393: ...2 Using Switching and Routing Protocols...
Page 394: ......
Page 454: ...Spanning Tree Protocol ExtremeWare XOS 11 3 Concepts Guide 454...
Page 484: ...Extreme Standby Router Protocol ExtremeWare XOS 11 3 Concepts Guide 484...
Page 514: ...IPv4 Unicast Routing ExtremeWare XOS 11 3 Concepts Guide 514...
Page 530: ...IPv6 Unicast Routing ExtremeWare XOS 11 3 Concepts Guide 530...
Page 538: ...RIP ExtremeWare XOS 11 3 Concepts Guide 538...
Page 556: ...OSPF ExtremeWare XOS 11 3 Concepts Guide 556...
Page 566: ...OSPFv3 ExtremeWare XOS 11 3 Concepts Guide 566...
Page 589: ...3 Appendixes...
Page 590: ......
Page 640: ...CNA Agent ExtremeWare XOS 11 3 Concepts Guide 640...
Page 670: ...Glossary ExtremeWare XOS 11 3 Concepts Guide 670...
Page 698: ...Index ExtremeWare XOS 11 3 Concepts Guide 698...