Technical Documentation

Configuring the Dynamic Flow Capture Interface

You specify the interface that interacts with the control sources configured in the same dynamic flow capture group. A Monitoring Services III PIC can belong to only one capture group, and you can configure only one PIC for each group.

To configure a dynamic flow capture interface, include the interfaces statement at the [edit services dynamic-flow-capture] hierarchy level:

[edit services dynamic-flow-capture capture-group client-name]
interfaces interface-name;

You specify dynamic flow capture interfaces using the dfc- identifier at the [edit interfaces] hierarchy level. Three logical units are required on each dynamic flow capture interface, numbered 0, 1, and 2. You cannot configure any other logical interfaces.

  • unit 0 processes control protocol requests and responses.
  • unit 1 receives monitored data.
  • unit 2 transmits the matched packets to the destination address.

The following example shows the configuration necessary to set up a dynamic flow capture interface:

[edit interfaces dfc-0/0/0]
unit 0 {
family inet {
address 10.1.0.0/32 { # Address of the Routing Engine for the DFC PIC.
destination 10.36.100.1; # Address of DFC PIC; used by the
# control source to correspond with the monitoring station.
}
}
}
unit 1 { # Receives data packets on this logical interface.
family inet;
}
unit 2 { # Sends copies of matched packets from this logical interface.
family inet;
}

In addition, you must configure the dynamic flow capture application to run on the DFC PIC in the correct chassis location. The following example shows this configuration at the [edit chassis] hierarchy level:

[edit chassis]
fpc 0 {
pic 0 {
monitoring-services application dynamic-flow-capture;
}
}

For more information on configuring chassis properties, see the JUNOS System Basics Configuration Guide.

Published: 2009-10-08