Juniper EX9200 Features Manual page 33

Release History Table
Related
Documentation
Copyright © 2017, Juniper Networks, Inc.
seconds 10;
}
}
}
}
}
The following considerations apply to the inline flow-monitoring instance configuration:
Sampling run-length and clip-size are not supported.
For inline configurations, each family can support only one collector.
NOTE: On routers with MS-PICs or MS-DPCs, IPv4 and IPv6 fragments are
processed accurately. The flow monitoring application creates two flows for
every fragmented flow. The first fragment that has the complete Layer 4
information forms the first flow with 5-tuple data and subsequently, all the
fragmented packets related to this flow form another flow with the Layer 4
fields set to zero.
Release Description
16.1R1 Starting with Junos OS Release 16.1R1 and 15.1F2, the IPv4 table is assigned
a default value of 1024.
16.1R1 Starting in Junos OS Release 16.1R1 and 15.1F2, any change in the configured
size of flow hash table sizes does not initiate an automatic reboot of the
FPC.
Configuring Inline Active Flow Monitoring on MX80 Routers
inline-jflow
Chapter 3: Configuring Active Flow Monitoring
19