Example: Configuring Flow Monitoring - Juniper EX9200 Features Manual

Example: Configuring Flow Monitoring

Copyright © 2017, Juniper Networks, Inc.
enables the router or switch to purge flows that have become inactive and that can waste
tracking resources.
NOTE: The router must contain an Adaptive Services, Multiservices, or
Monitoring Services PIC for the
statements to take effect.
The following is an example of flow-monitoring properties configured to support input
SONET/SDH interfaces, output monitoring services interfaces, and export to cflowd for
flow analysis. To complete the configuration, you also need to configure the interfaces
and set up a virtual private network (VPN) routing and forwarding (VRF) instance. For
information on cflowd, see Enabling Flow Aggregation.
[edit forwarding-options]
monitoring group1 {
family inet {
output {
cflowd 192.168.245.2 port 2055;
export-format cflowd-version-5;
flow-active-timeout 60;
flow-inactive-timeout 30;
interface mo-4/0/0.1 {
engine-id 1;
engine-type 1;
input-interface-index 44;
output-interface-index 54;
source-address 192.168.245.1;
}
interface mo-4/1/0.1 {
engine-id 2;
engine-type 1;
input-interface-index 45;
output-interface-index 55;
source-address 192.168.245.1;
}
interface mo-4/2/0.1 {
engine-id 3;
engine-type 1;
input-interface-index 46;
output-interface-index 56;
source-address 192.168.245.1;
}
interface mo-4/3/0.1 {
engine-id 4;
engine-type 1;
input-interface-index 47;
output-interface-index 57;
source-address 192.168.245.1;
}
}
Chapter 2: Configuring Basic Flow Monitoring
flow-active-timeout and flow-inactive-timeout
13