[Contents][Prev][Next][Index][Report an Error]

Configuring the Version 9 Template Properties

To define the version 9 templates, include the following statements at the [edit services flow-monitoring version9] hierarchy level:



[edit services flow-monitoring version9]

template name {

flow-active-timeout seconds;

flow-inactive-timeout seconds;

option-refresh-rate packets packets seconds seconds;

template-refresh-rate packets packets seconds seconds;


(ipv4-template | ipv6-template | mpls-ipv4-template | mpls-template) {

label-position [ label ];
}


}

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, mpls-ipv4-template, or mpls-template statement.
If the template is used for MPLS traffic, you can also specify up to three label positions for the MPLS 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 cflowd] hierarchy level.

Note: In active flow monitoring, the cflowd 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 cflowd records are exported at 120-second intervals. If the active timeout value is 150 seconds, the cflowd 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 inet6 { sampling { input; output; } } } }

[Contents][Prev][Next][Index][Report an Error]