Extreme Networks ExtremeWare XOS Guide Manual page 386

CLEAR-Flow
If a keyword is not supported, or a counter name is not found, a string of
"unknownKeyword[$keyword]" will be substituted
For the $vlanName and $port keyword, the keyword
wildcard ACL Some CLI commands do not support the
commands that use this feature.
A maximum of 10 different counter substitutions can be used per rule, including counters used in
expressions. For example, if a rule uses four counters in its expressions, then we can use six more
different counters in keyword substitutions, for a total of 10.
Table 55: Keyword Substitutions
Keyword
$policyName
$ruleName
$<counterName>
$ruleValue
$ruleThreshold
$ruleInterval
$vlanName
$port
Predefined CLEAR-Flow Counters
There are a number of packet statistics gathered by the XOS kernel. In order to allow you to use these
statistics in CLEAR-Flow expressions, these kernel counters are now available for use with CLEAR-
Flow. Most of the counter names are based directly on well known names from common kernel
structures and MIBs. The names are modified from their familiar form by prepending the characters
sys_ to the counter names.
Table 56: Predefined CLEAR-Flow Counters
Counter Name
sys_IpInReceives
sys_IpInHdrErrors
sys_IpInAddrErrors
sys_IpForwDatagrams
sys_IpInUnknownProtos
386
Substitution
Replace with the policy name.
Replace with the CLEAR-Flow rule name.
Replace with counter value for the indicated counter name.
Replace with the current expression value.
Replace with the expression threshold value.
Replace with the rule sampling/evaluation interval.
Replace with the interface VLAN name.
Replace with the interface port number.
1
Description
The total number of input IP packets received from interfaces, including those
received in error.
The number of input IP packets discarded due to errors in their IP headers,
including bad checksums, version number mismatch, other format errors, time-
to-live exceeded, errors discovered in processing their IP options, etc.
The number of input IP packets discarded because the IP address in their IP
header's destination field was not a valid address to be received at this entity.
This count includes invalid addresses (e.g., 0.0.0.0) and addresses of
unsupported Classes (e.g., Class E).
The number of input IP packets for which this entity was not their final IP
destination, as a result of which an attempt was made to find a route to forward
them to that final destination.
The number of locally-addressed IP packets received successfully but discarded
because of an unknown or unsupported protocol.
will be substituted for those rules in the
all
keyword, so caution must be used with CLI
all
ExtremeWare XOS 11.3 Concepts Guide