[an error occurred while processing this directive][an error occurred while processing this directive]

Collecting Flow Records with an Accounting Group

To perform discard accounting on specified traffic, you can collect flow records with the accounting statement at the [edit forwarding-options] hierarchy level. Like sampling, your topology must be simple (for example, one input interface and one export interface).

Again, you can collect flow records by specifying input and output interfaces. You can configure the input interface to perform discard accounting by applying a firewall filter that contains the then discard accounting statement. This match condition directs the filtered traffic to be converted into flow records and exported for analysis by the monitoring services or adaptive services interface. The original packets are then sent to the discard process. For the output, remember to specify the IP address and port of your flow server and the services interface you plan to use for processing flow records.

You must configure a source address, but the engine-id and engine-type output interface statements are added automatically. You can override these values manually to track different flows with a single flow collector. SNMP input and output interface index information is captured in flow records by default when you configure discard accounting.

[edit]forwarding-options {accounting counter1 {output {flow-inactive-timeout 65;flow-active-timeout 65;flow-server 10.60.2.1 {port 2055;version 8;aggregation {protocol-port;source-destination-prefix;}}interface sp-2/0/0 {engine-id 1;engine-type 11;source-address 10.60.2.2;}}}}

Published: 2010-04-15

[an error occurred while processing this directive]