Extreme Networks ExtremeWare 7.0.0, Command Reference Manual, Page: 509 / 1598

config flowstats filter ports
ExtremeWare Software 7.0.0 Command Reference Guide 509
config flowstats filter ports
config flowstats filter <filter#> {aggregation} {export <group#>} ports
<portlist> [ingress | egress] <filterspec>
Description
Configures a flow record filter for the specified ports.
Syntax Description
Default
N/A.
Usage Guidelines
Configuring a filter specification enables that filter for the specified ports. To specify all ports, you can
use specify them as the range of all ports (such as 1-32 or 7:1-7:4) or in the form <slot>:* on a modular
switch.
filter# The
filter#
parameter is an integer in the range from 1 to 8 that identifies the filter being
defined.
<group#> Specifies the group number that identifies the set of flow collector devices to which records
for flows matching the filter are to be exported. If Group is not specified , then group # 1 will
be used as default export group.
aggregation To reduce the volume of exported data, use this optional keyword to maintain a single set
of statistics for all the flows that match the specified filter.
filterspec Specifies a set of five parameters (four are value/mask pairs) that define the criteria by
which a flow is evaluated to determine if it should be exported. The parameters are:
[{dest-ip <ipaddress_value/mask ipaddress_filtermask>} {source-ip
<ipaddress_value/mask ipaddress_filtermask> } {dest-port
<port_value/port_filtermask> } {source-port
<port_value/port_filtermask> } {protocol
<tcp/udp/ip/protocol_value/protocol_filtermask>} | match-all-flows
|match-no-flows ]
All five specifications must be included in the order specified.
The range for port/port_mask is calculated using the following formula:
(minport = port, maxport = 2^(32-port_mask)-1).
Conceptually, the filters work by ANDing the contents of each of the five components of a
forwarded flow with the associated masks from the first defined filter (filter #1). Statistics are
maintained if the results of the AND operations match the configured filter values for all
fields of the sequence. If there is no match, then the operation is repeated for filter #2, and
so on. If there is no match for any of the filters, then statistics are not maintained for the
flow. Filters for any or all of the sequence components can be configured with a single
command.
match-all-flows Specifies that the filter should match any flow.
match-no-flows Specifies that the filter should discard all flow. This option is not valid for Ethernet blades.
egress Specifies that the filter should capture only egress traffic. This option is not valid for
Ethernet blades.
ingress Specifies that the filter should capture only ingress traffic.