Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers

Use of IPFIX allows you to define a flow record template suitable for IPv4 traffic or IPv6 traffic. Templates are transmitted to the collector periodically, and the collector is not aware of the router configuration. You can define template refresh rate, flow active timeout and inactive timeout.

If flow records are being sent for multiple protocol families (for example, for IPv4 and IPv6), each protocol family flow will have a unique Observation Domain ID.

To learn about the fields included in the templates, see Understanding Inline Active Flow Monitoring.

Configuring the IPFIX Template Properties

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

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 or ipv6–template.

  • 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.

  • 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 600 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:


The following restrictions apply to IPFIX templates:

  • Outbound Routing Engine traffic is not sampled. A firewall filter is applied as output on the egress interface, which samples packets and exports the data. For transit traffic, egress sampling works correctly. For internal traffic, the next hop is installed in the Packet Forwarding Engine but sampled packets are not exported.

  • Flows are created only after the route record resynchronization operation is complete, which takes 120 seconds.

Customizing Template ID, Observation Domain ID, and Source ID for IPFIX Flow Templates


For PTX Series routers with third generation FPCs installed, the FPC’s slot number is used for the observation domain ID.

Use of IPFIX flow templates allow you to define a flow record template suitable for IPv4 traffic, IPv6 traffic, MPLS traffic, a combination of IPv4 and MPLS traffic, or peer AS billing traffic. Templates and the fields included in the template are transmitted to the collector periodically, and the collector does not need to be aware of the router configuration. Template IDs 0 through 255 are reserved for template sets, options template sets, and other sets for future use. Template IDs of data sets are numbered from 256 through 65535. Typically, this information element or field in the template is used to define the characteristics or properties of other information elements in a template. After a restart of the export process of templates is performed, template IDs can be reassigned.

The corresponding data sets and option data sets contain the value of the template IDs and options template IDs respectively in the set ID field. This method enables the collector to match a data record with a template record.


The following show commands are supported for IPFIX:

  • show services accounting flow inline-jflow fpc-slot fpc-slot

  • show services accounting errors inline-jflow fpc-slot fpc-slot

  • show services accounting status inline-jflow fpc-slot fpc-slot

Example: Configuring an IPFIX Flow Template and Flow Sampling

The following is a sample IPFIX template configuration:

The following example applies the IPFIX template to enable sampling of traffic for billing: