Policy Framework Configuration Guide - Juniper Networks

Chapter 14: Introduction to Traffic Sampling Configuration
Example: Configuring Active Flow Monitoring Using Version 9
Traffic Sampling Examples
In this example, you enable active flow monitoring using version 9. You specify a template
mpls that you configure at the [edit services monitoring] hierarchy level. You also configure
the traffic family mpls to sample MPLS packets.
[edit forwarding-options]
sampling {
input {
rate 1;
run-length;
}
family inet {
output {
flow-server 10.60.2.1 { # The IP address and port of the host
port 2055; # that collects the sampled traffic flows.
source-address 3.3.3.1;
version9 {
template mpls; # Version 9 records are sent
} # using the template named mpls
}
}
The following sections provide examples of configuring traffic sampling:
• Example: Sampling a Single SONET/SDH Interface on page 355
• Example: Sampling All Traffic from a Single IP Address on page 356
• Example: Sampling All FTP Traffic on page 357
Example: Sampling a Single SONET/SDH Interface
The following configuration gathers statistical sampling information from a small
percentage of all traffic on a single SONET/SDH interface and collects it in a file named
sonet-samples.txt.
Create the filter:
[edit firewall family inet]
filter {
sample-sonet {
then {
sample;
accept;
}
}
}
Apply the filter to the SONET/SDH interface:
[edit interfaces]
Copyright © 2010, Juniper Networks, Inc.
355