Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
Configuring Active Flow Monitoring Using Version 9
In Junos OS Release 8.3 and later, 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 OS Services
Interfaces Configuration Guide and the Junos OS Feature Guide.
To enable the collection of traffic flows using the version 9 format, include the version9
statement at the [edit forwarding-options sampling family family-name output flow-server
hostname] hierarchy level:
[edit forwarding-options sampling family family-name output flow-server 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. In Junos OS Release 8.3 and later, you can configure sampling for 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. In Junos OS Release 9.5 and later, you
can sample packets from both the inet and mpls protocol families at the same time. In
Junos Release 10.4 and later, you can configure sampling for peer AS billing traffic for
the inet and ipv6 protocols only. For more information about how to configure traffic
sampling, see “Configuring Traffic Sampling” on page 347.
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 family family-name output
flow-server 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)” on page 351.
• 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.
354
Copyright © 2010, Juniper Networks, Inc.