This area will help fast track you in planning, setting up and managing NetFlow in your environment. NetFlow is an embedded instrumentation within Cisco IOS Software to characterize network operation.

Network specialists of various levels within an organization need to be able to report on traffic traversing sites, key links and data centers without deploying probes. They use NetFlow Auditor powered by DigiToll’s unique methods of collection to capture and analyze every NetFlow record with aggregation options and small footprint real-time and long-term storage. From Telco to SME you will recognize the superior reliability and performance of the DigiToll NetFlow Auditing solutions, as well as the management benefits offered.

Configure NetFlow - Juniper

Configuring Active Flow Monitoring Using Version 9

Beginning with JUNOS Release 8.3, you can collect a record of sampled flows using the version 9 format as defined in RFC 3954, Cisco Systems NetFlow Services Export Version 9. Version 9 uses templates to collect an set of sampled flows and send the record to a specified host.

You configure the version 9 template used to collect a record of sampled flows at the [edit services monitoring] hierarchy level. For more information, see the JUNOS Services Interfaces Configuration Guide and the JUNOS Feature Guide and Configuring J-Flow-Based Statistics Collection.

To enable the collection of traffic flows using the version 9 format, include the version9 statement at the [edit forwarding-options sampling output cflowd hostname] hierarchy level:

[edit forwarding-options sampling output cflowd hostname]
version9 {
template template-name;
}


template-name is the name of the version 9 template configured at the [edit services monitoring] hierarchy level.

You configure traffic sampling at the [edit forwarding-options sampling input] hierarchy level. Beginning with JUNOS Release 8.3, traffic sampling supports MPLS traffic as well as IPv4 traffic. You can define a version 9 flow record template suitable for IPv4 traffic, MPLS traffic, or a combination of the two. However, you can sample packets from only one type of family (inet or mpls) at the same time. For more information about how to configure traffic sampling, see Configuring Traffic Sampling.

The following restrictions apply to configuration of the version 9 format:

  • You can configure only one host to collect traffic flows using the version 9 format. Configure the host at the [edit forwarding-options sampling output cflowd hostname] hierarchy level.
  • You cannot specify both the version 9 format and cflowd versions 5 and 8 formats in the same configuration. For more information about how to configure flow monitoring using cflowd version 8, see Configuring Flow Aggregation (cflowd).
  • Any values for flow-active-timeout and flow-inactive-timeout that you configure at the [edit forwarding-options sampling output] hierarchy level are overridden by the values configured in the version 9 template.
  • Version 9 does not support Routing Engine-based sampling. You cannot configure version 9 to send traffic sampling result to a file in the /var/tmp directory

cron