Specifications

Services Interfaces Configuration Guide
•
In the Lines of Sample DTCP Parameter File table in the “Flow-Tap Filter Operation”
topic, the description for the Seq:10 command contained in the DTCP file incorrectly
states that the router looks for a newer sequence number before accepting and
implementing new parameters, and that any configuration attempt with an older
sequence number is rejected by the dynamic flow capture process.
The following guideline correctly describes the processing of the Seq:10 command in
the DTCP file:
The router does not validate the sequence number attribute during any configuration
changes that are performed for a DTCP parameter file sent to the router from the
mediation device. Regardless of whether the sequence number conflicts with a previous
sequence number or is unique, it is disregarded and not considered.
The following additional fields are missing from the Lines of Sample DTCP Parameter
File table:
DescriptionCommand
This indicates the DTCP version to be used. DTCP/0.6 should be used for all versions of Junos OS up
to and including Junos OS 8.5. DTCP/0.7 should be used for Junos OS 9.0 and later. However, Junos
OS 9.5R2 and later also accept previous versions of DTCP.
If any unsupported parameters are received for a particular DTCP version, the request is rejected.
NOTE: The notification responses from Junos OS contains the same DTCP version that the control
source has communicated to Junos OS. For notifications being sent even before the control source
has contacted Junos OS, the DTCP version 0.7 will be used.
DELETE DTCP/0.6
This line denotes the ID that DTCP assigns for the mirrored session when you create a DTCP ADD
message. Use this ID in your DELETE messages to disable the intercept for a specific subscriber. To
view the ID, use the DTCP LIST message. The CRITERIA-ID and the Cdest-ID are mutually exclusive in
DELETE messages.
CRITERIA-ID:
criteria-id
[See Flow-Tap Filter Operation.]
•
The following additional information applies to the sample configuration described in
the “Example: Flow-Tap Configuration” topic of the “Flow Monitoring” chapter.
NOTE: The described example applies only to M Series and T Series routers,
except M160 and TX Matrix routers. For MX Series routers, because the
flow-tap application resides in the Packet Forwarding Engine rather than
a service PIC or Dense Port Concentrator (DPC), the Packet Forwarding
Engine must send the packet to a tunnel logical (vt-) interface to
encapsulate the intercepted packet. In such a scenario, you need to allocate
a tunnel interface and assign it to the dynamic flow capture process for
FlowTapLite to use.
147Copyright © 2015, Juniper Networks, Inc.
Documentation Updates