Junos OS Interfaces Configuration Guide for ... - Juniper Networks

Junos OS Interfaces Configuration Guide for Security Devices
22
The following details apply to the configuration statements:
• You assign each template a unique name by including the template name statement.
• You then specify each template for the appropriate type of traffic by including the
ipv4-template, ipv6–template, inet-ipv4-template, inet-template, or
peer-as-billing-template.
• If the template is used for inet traffic, you can also specify up to three label positions
for the inet header label data by including the label-position statement; the default
values are [1 2 3].
• Within the template definition, you can optionally include values for the
flow-active-timeout and flow-inactive-timeout statements. These statements have
specific default and range values when they are used in template definitions; the default
is 60 seconds and the range is from 10 through 600 seconds. Values you specify in
template definitions override the global timeout values configured at the [edit
forwarding-options sampling output flow-server] hierarchy level.
NOTE: In active flow monitoring, the flow-server records are exported after
a time period that is a multiple of 60 seconds and greater than or equal to
the configured active timeout value. For example, if the active timeout
value is 90 seconds, the flow-server records are exported at 120-second
intervals. If the active timeout value is 150 seconds, the flow-server records
are exported at 180-second intervals, and so forth.
• You can also include settings for the option-refresh-rate and template-refresh-rate
statements within a template definition. For both of these properties, you can include
a timer value (in seconds) or a packet count (in number of packets). For the seconds
option, the default value is 60 and the range is from 10 through 600. For the packets
option, the default value is 4800 and the range is from 1 through 480,000.
• To filter IPV6 traffic on a media interface, the following configuration is supported:
interfaces interface-name {
unit 0 {
family inet {
sampling {
input;
output;
}
}
}
}
Copyright © 2011, Juniper Networks, Inc.