Juniper EX9200 Features Manual page 31

Copyright © 2017, Juniper Networks, Inc.
[edit services flow-monitoring]
user@host# set (version-ipfix | version9) template template-name
b. (Optional) Configure the interval after which an active flow is exported.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set flow-active-timeout
c. (Optional) Configure the interval of activity that marks a flow as inactive.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set flow-inactive-timeout
d. (Optional) Configure the template refresh rate in either number of packets or
number of seconds.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set template-refresh-rate packets packets seconds seconds
e. (Optional) Configure the refresh rate in either number of packets or number of
seconds.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set option-refresh-rate packets packets seconds seconds
f. Specify the type of record that the template is used for.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set (ipv4-template |ipv6-template | mpls-ipv4-template |
mpls-template | peer-as-billing-template | vpls-template)
The is for version 10 templates only.
vpls-template
g. (Optional) Include the flow direction value in the template.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set flow-key flow-direction
The data field contains 0x00 (ingress) or 0x01 (egress). If you do not include the
flow-key flow-direction
value 0xFF.
h. (Optional) Include VLAN IDs in both the ingress and egress directions in the flow
key.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set flow-key vlan-id
The data field contains 0x00 (ingress) or 0x01 (egress). If you do not include the
flow-key flow-direction
value 0xFF.
i. (Optional) Include VLAN IDs in both the ingress and egress directions in the flow
key.
[edit services flow-monitoring (version-ipfix | version9) template template-name]
user@host# set flow-key vlan-id
This statement is not required for ingress and egress VLAN ID reporting on interfaces.
The following example shows the sampling configuration for an instance that supports
inline active flow monitoring on
Chapter 3: Configuring Active Flow Monitoring
seconds
seconds
statement, the flow direction data field contains the invalid
statement, the flow direction data field contains the invalid
family inet and PIC-based sampling on family inet6 :
17