Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Understand Inline Active Flow Monitoring

Inline active flow monitoring is implemented on the Packet Forwarding Engine. The Packet Forwarding Engine performs functions such as creating flows, updating flows, and exporting flow records to a flow collector. The flow records are sent out in industry-standard IPFIX or version 9 format. IPFIX and version 9 templates use UDP as the transport protocol.

You can configure inline active flow monitoring for IPv4, IPv6, MPLS, MPLS-IPv4, VPLS, and bridge traffic. See the change history table at the end of this topic for details about particular platform support.

For PTX Series, starting with Junos OS Evolved Release 21.2R1 and Junos OS Release 21.3R1, no flows are maintained. For ACX Series running Junos OS Evolved, no flows are maintained either. Every sampled packet is considered to be a flow. When the sampled packet is received, the flow is created and immediately timed out as inactive, and the software exports a record to the collector. Therefore, the number of records sent to the collector is higher than before. See Table 1. The IPFIX and version 9 Options Template Data Record now contains 0 in the Flow Active Timeout (Element ID 36) and Flow Inactive Timeout (Element ID 37) fields. Therefore, the Options Template Data Record is not compliant with IPFIX RFC 7011. The show services accounting flow inline-jflow fpc-slot slot operational mode command now displays 0 for all of the Active Flows and Timed Out fields. The various Total Flows fields are now equal to their respective Flow Packets fields. The various Flows Inactive Timed Out fields are now equal to their respective Flow Packets fields. The effect of the nexthop-learning statement at the [edit services flow-monitoring version version template template-name] hierarchy level on this no-flow behavior varies depending upon the operating system. For Junos OS Evolved, we do not recommend that you configure the nexthop-learning statement, as it reduces the number of packets that can be processed. For Junos OS, you can configure the nexthop-learning statement to change this default no-flow behavior and once again create and maintain flows, then attach the template to all sampling instances associated with FPCs that require the previous behavior.

Table 1: Inline Active Flow Monitoring Behavior Comparison for PTX Series
Actions Prior to Junos OS Evolved Release 21.2R1 and Junos OS Release 21.3R1 Starting in Junos OS Evolved Release 21.2R1 and Junos OS Release 21.3R1
Flow creation Flows are created and maintained. No flows are created. Every packet is considered as a new flow for accounting purposes.
Active timeout Active timeout configuration is honored. Active flows are timed out if the traffic is continuous. An export record is created for the timed-out flow and exported to the collector. Active timeout configuration is ignored. No flows are timed out.
Inactive timeout Inactive timeout configuration is honored. Inactive flows are timed out and are deleted at that time. An export record is created for the timed-out flow and exported to the collector. Inactive timeout configuration is ignored. All flows are inactively timed out immediately.
Export records creation Export records are created only during timeouts. Export records are created for every sampled packet.
Packet export to collector The configured active and Inactive timeouts determine the packet export rates to the collector. The packet export rate to the collector is directly proportional to sampling rate (in packets per second) at that given point in time. Because each packet results in an export record, the number of packets sent out to the collector does increase in comparison to what it was before.

Benefits of Inline Active Flow Monitoring

Inline active flow monitoring is implemented on the Packet Forwarding Engine rather than on a services card. This enables:

  • Lower cost—You do not need to invest in additional hardware.

  • Higher scalability—You do not need to dedicate a PIC slot for a services PIC, so you can make full use of the available slots for handling traffic on the device.

  • Better performance—Inline flow monitoring performance is not dependent on the capacity of a services card.

Inline Active Flow Monitoring Configuration Overview

The inline active flow monitoring configuration can be broadly classified into four categories:

  1. Configurations at the [edit services flow-monitoring] hierarchy level—At this level, you configure the template properties for inline flow monitoring.

  2. Configurations at the [edit forwarding-options] hierarchy level—At this level, you configure a sampling instance and associate the template (configured at the [edit services flow-monitoring] hierarchy level) with the sampling instance. At this level, you also configure the flow-server IP address and port number as well as the flow export rate, and specify the collectors.

    You cannot change the source IP address for collectors under the same family. Also, the template mapped across collectors under a family should be the same.

  3. Configurations at the [edit chassis] hierarchy level—At this level, you associate the sampling instance with the FPC on which the media interface is present. If you are configuring sampling of IPv4 flows, IPv6 flows, or VPLS flows, you can configure the flow hash table size for each family.

  4. Configurations at the [edit firewall] hierarchy level—At this level you configure a firewall filter for the family of traffic to be sampled. You must attach this filter to the interface on which you want to sample the traffic.

Before you configure inline active flow monitoring, ensure that you have adequately-sized hash tables for IPv4, IPv6, MPLS, and VPLS flow sampling. (VPLS flow sampling is Junos OS only.) These tables can use from one up to fifteen 256K areas. Starting with Junos OS Release 16.1R1 and 15.1F2, the IPv4 table is assigned a default value of 1024. Prior to Junos OS Release 16.1 and 15.1F2, the IPv4 table is assigned a default value of fifteen 256K areas. The IPv6 table is assigned a default value of 1024, and the VPLS table is assigned a default value of 1024. Allocate larger tables when anticipated traffic volume makes it necessary.

For Junos OS, you can configure flow collectors to be reachable through non-default VPN routing and forwarding (VRF) instances by including the routing-instance instance-name statement at the [edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls) output flow-server hostname] hierarchy level for inline flow monitoring. For Junos OS Evolved, you can only configure flow collectors that are reachable through the default VRF. You cannot configure a flow collector to be reachable through non-default VRF instances for version 5 and version 8 flows. You must configure the routing instance to be a VRF instance by including the instance-type vrf statement at the [edit routing-instances instance-name] hierarchy level.

Starting in Junos OS Release 15.1F7 for certain MX Series routers, you can configure the report-zero-oif-gw-on-discard at the [edit chassis fpc slot-number inline-services] hierarchy level to set the flow record value to 0 (zero) for the IPFIX information elements ipNextHopIPv6Address (Element ID 62), egressInterface (Element ID 14), and ipNextHopIPv4Address (Element ID 15) for only the flow records for rejected, discarded, and policed flows. You configure this statement to help you track what traffic is being dropped.

Inline Active Flow Monitoring Limitations and Restrictions

The following limitations and restrictions apply to the inline active flow monitoring feature:

  • Inline active flow monitoring is not supported for input or output traffic on MS-MPC or MS-MIC-16G interfaces.

  • Configuring both sFlow and inline active flow monitoring on the same interface leads to unexpected behavior. Therefore, configure these features on separate interfaces.

  • Configuring both egress port mirroring and inline active flow monitoring on the same interface leads to unexpected behavior. Therefore, configure these features on separate interfaces.

  • Ingress and egress sampling are sent to the same host-path queue. The packet rate in the queue is shared across ingress and egress sampled packets.

  • Forwarding class configuration is not effective. Export record packets are always considered to be control frames and as such are pushed to the network-control queue.

  • If multiple inline active flow monitoring firewall filters match to a flow, only the actions of the first filter are taken.

  • In ingress sampling, if the destination port is on an aggregated Ethernet interface, the output interface is invalid.

  • In Junos OS release 15.1 and earlier, you can apply version 9 flow templates to IPv4 traffic. Starting in Junos OS Release 16.1, you can also apply version 9 flow templates to MPLS and MPLS-IPv4 traffic. Starting in Junos OS Release 18.1R1, you can also apply version 9 flow templates to IPv6 traffic.

  • In Junos OS Release 15.1 and earlier, you can apply IPFIX flow templates to IPv4, IPv6, and VPLS traffic. Starting in Junos OS release 16.1, you can also apply IPFIX flow templates to MPLS and MPLS-IPv4 traffic.

  • Starting with Junos OS Release 17.2R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10002 switches. Starting with Junos OS Release 17.4R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10008 and QFX10016 switches.

  • Inline active flow monitoring is not supported when you enable Next Gen Services on an MX Series router.

  • You can configure only one sampling instance on a Flexible PIC Concentrator (FPC). For the ACX7509, you can configure a sampling instance only on FPC0.

  • For Junos OS Evolved ACX routers only, a maximum of 40,000 samples/second is supported. Sampled packets have an additional FTMH header that causes an increase in the packet size.

  • You can configure only one type of sampling—either services-card-based sampling or inline sampling—per family in a sampling instance. However, you can configure services-card-based and inline sampling for different families in a sampling instance.

  • The following considerations apply to the inline sampling instance configuration:

    • Sampling run-length and clip-size are not supported.

    • In Junos OS Release 16.2 and in Junos OS Release 16.1R3 and earlier, you can configure only one collector under a family for inline active flow monitoring. Starting with Junos OS Release 16.1R4 and 17.2R1, you can configure up to four collectors under a family for inline active flow monitoring. Starting with Junos OS Evolved 20.3R1, for the PTX10003 and PTX10008 (with the JNP10K-LC1201 line card and the JNP10008-SF3) routers, you can configure up to four collectors for inline active flow monitoring. Starting with Junos OS Evolved 20.4R1, for the PTX10001-36MR and the PTX10008 (with the JNP10K-LC1202 line card and the JNP10008-SF3) routers, you can configure up to four collectors for inline active flow monitoring. Starting with Junos OS Evolved 21.1R1, for the PTX10004 router, you can configure up to four collectors for inline active flow monitoring. To configure a collector under a family for inline active flow monitoring, configure the flow-server statement at the edit forwarding-options sampling-instance instance-name family (inet | inet6) output hierarchy level. To specify up to four collectors, include up to four flow-server statements.

    • The user-defined sampling instance gets precedence over the global instance. When a user-defined sampling instance is attached to the FPC, the global instance is removed from the FPC and the user-defined sampling instance is applied to the FPC.

  • Flow records and templates cannot be exported if the flow collector is reachable through any management interface.

  • If the destination of the sampled flow is reachable through multiple paths, the IP_NEXT_HOP (Element ID 15) and OUTPUT_SNMP (Element ID 14) in the IPv4 and IPv6 flow records are not reported correctly unless you enable learning of next hop addresses by using the nexthop-learning enable statement. (Starting in Junos OS Evolved Release 21.2R1 for PTX Series, we do not recommend that you enable learning of next-hop addresses, as it reduces the number of packets that can be processed. However, starting in Junos OS Release 21.3R1 for PTX Series, you can configure the nexthop-learning statement to change the default no-flow behavior and once again create and maintain flows, then attach the template to all sampling instances associated with FPCs that require the previous behavior.) If you do not configure nexthop-learning enable:

    • For IPv4 flow records, the IP_NEXT_HOP and OUTPUT_SNMP are set to the Gateway Address and SNMP Index of the first path seen in the forwarding table.

    • For IPv6 flow records, the IP_NEXT_HOP and OUTPUT_SNMP are set to 0.

  • The Incoming Interface (IIF) and Outgoing Interface (OIF) should be part of the same VRF. If OIF is in a different VRF, DST_MASK (Element ID 13), DST_AS (Element ID 17), IP_NEXT_HOP (Element ID 15), and OUTPUT_SNMP (Element ID 14) are set to 0 in the flow records.

  • Each lookup chip maintains and exports flows independent of other lookup chips. Traffic received on a media interface is distributed across all lookup chips in a multi-lookup chip platform. It is likely that a single flow is processed by multiple lookup chips. Therefore, each lookup chip creates a unique flow and exports it to the flow collector. This can cause duplicate flow records to go to the flow collector. The flow collector should aggregate PKTS_COUNT and BYTES_COUNT for duplicate flow records to derive a single flow record.

IPFIX and Version 9 Templates

Fields Included in the IPFIX Bridge Template for MX Series

Table 2 shows the fields that are included in the IPFIX Bridge template. The fields are shown in the order in which they appear in the template.

Table 2: IPFIX Bridge Template Fields for MX, M, and T Series

Field

Element ID

Destination MAC

80

Source MAC

56

Ethernet Type

256

Input SNMP

10

Output SNMP

14

Flow End Reason

136

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX IPv4 Template for MX, M, and T Series

Table 3 shows the fields that are included in the IPFIX IPv4 template. The fields are shown in the order in which they appear in the template.

Table 3: IPFIX IPv4 Template Fields for MX, M, and T Series

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

VLAN ID

58

IPv4 Source Mask

9

IPv4 Destination Mask

13

Source AS

16

Destination AS

17

IPv4 Next Hop Address

15

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

IP Protocol Version

60

BGP IPv4 Next Hop Address

18

Flow Direction (Starting in Junos OS Release 16.1)

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX IPv4 Template for PTX3000 Series, PTX5000 Series, and the PTX10001-20C Router

Table 4 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 4: IPFIX IPv4 Template Fields for PTX3000 Series, PTX5000 Series, and the PTX10001-20C Router

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Fields Included in the IPFIX IPv4 Template for PTX1000, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), and PTX10016 Series

Table 5 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 5: IPFIX IPv4 Template Fields for PTX1000, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), and PTX10016 Series

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX IPv4 Template for PTX10001-36MR, PTX10003-160C, PTX10003-80C, PTX10004, and PTX10008 (with JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3) Routers

Table 6 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 6: IPFIX IPv4 Template Fields for PTX10001-36MR, PTX10003-160C, PTX10003-80C, PTX10004, and PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3) Routers

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

Source Port

7

Destination Port

11

ICMP Type and Code

32

Input SNMP Index

10

Source AS

16

Destination AS

17

BGP Next Hop Address

18

Output SNMP Index

14

Number of Bytes

1

Number of Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Source AS Path List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

16 (list of this type)

Destination AS Path List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

17 (list of this type)

BGP Source Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

484

BGP Destination Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

485

BGP Source Extended Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

487

BGP Destination Extended Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

488

BGP Source Large Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

490

BGP Destination Large Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

491

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX IPv4 Template for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100 Routers

Table 7 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 7: IPFIX IPv4 Template Fields for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100 Routers

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

Source Port

7

Destination Port

11

ICMP Type and Code

32

Input SNMP Index

10

Source AS

16

Destination AS

17

BGP Next Hop Address

18

Output SNMP Index

14

Number of Bytes

1

Number of Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX IPv6 Template for MX, M, and T Series

Table 8 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 8: IPFIX IPv6 Template Fields for MX, M, and T Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

139

Input Interface

10

VLAN ID

58

IPv6 Source Mask

29

IPv6 Destination Mask

30

Source AS

16

Destination AS

17

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

Output Interface

14

Minimum Hop Limits

52

Maximum Hop Limits

53

Flow End Reason

136

Flow Direction (Starting in Junos OS Release 16.1)

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

IPv6 Option Headers

64

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX IPv6 Template for PTX3000 Series, PTX5000 Series, and the PTX10001-20C Router

Table 9 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 9: IPFIX IPv6 Template Fields for PTX3000 Series, PTX5000 Series, and the PTX10001-20C Router

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

IPv6 BGP NextHop Address

63

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Fields Included in the IPFIX IPv6 Template for PTX1000, PTX10002-60C, QFX10002-60C,PTX10008 (without the JNP10008-SF3), and PTX10016 Series

Table 10 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 10: IPFIX IPv6 Template Fields for PTX1000, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), and PTX10016 Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX IPv6 Template for PTX10001-36MR, PTX10003-160C, PTX10003-80C, PTX10004, and PTX10008 (with JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3) Routers

Table 11 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 11: IPFIX IPv6 Template Fields for PTX10001-36MR, PTX10003-160C, PTX10003-80C, PTX10004, and PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3) Routers

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input SNMP Index

10

Source AS

16

Destination AS

17

IPv6 BGP Next Hop Address

63

Output SNMP Index

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

IP Protocol Version

60

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Source AS Path List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

16 (list of this type)

Destination AS Path List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

17 (list of this type)

BGP Source Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

484

BGP Destination Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

485

BGP Source Extended Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

487

BGP Destination Extended Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

488

BGP Source Large Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

490

BGP Destination Large Community List (when configured on the data-record-fields statement at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level)

491

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX IPv6 Template for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100

Table 12 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 12: IPFIX IPv6 Template Fields for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100 Routers

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

IP Protocol Version

60

Source AS

16

Destination AS

17

IPv6 BGP Next Hop Address

63

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

The type of interface where packets are being received. This field can have the following values:

  • 1—Other (default value)

  • 131—De-encapsulated GRE traffic is reported as tunnel

368

Forwarding Class Name (first two bytes)

32767

Packet Loss Priority; this field can have the following values:

  • 0x00: Low

  • 0x01: Medium-low

  • 0x02: Medium-high

  • 0x03: High

  • 0xFF: Unknown

32766

Fields Included in the IPFIX MPLS-IPv4 Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the IPFIX MPLS-IPv4 template is supported. Table 13 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 13: IPFIX MPLS-IPv4 Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IP Address

47

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

VLAN ID

58

IPv4 Source Mask

9

IPv4 Destination Mask

13

Source AS

16

Destination AS

17

IPv4 Next Hop Address

15

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

IP Protocol Version

60

BGP IPv4 Next Hop Address

18

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS-IPv4 Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), and PTX10016 Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv4 template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-IPv4 template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-IPv4 template is supported for the QFX10002-60C switch.Table 14 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 14: IPFIX MPLS-IPv4 Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Ingress Interface Type

368

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IPv6 Address

140

Fields Included in the IPFIX MPLS-IPv4 Template for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Table 15 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 15: IPFIX MPLS-IPv4 Template Fields for PTX Series, for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IPv6 Address

140

Fields Included in the IPFIX MPLS-IPv6 Template for MX, M, and T Series

Starting in Junos OS Release 18.4R1, the IPFIX MPLS-IPv6 template is supported for the MX Series. Table 16 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 16: IPFIX MPLS-IPv6 Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IP Address (Only IPv4 top label addresses are exported. IPv6 top label addresses report a value of zero.)

47

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

VLAN ID

58

IPv6 Source Mask

29

IPv6 Destination Mask

30

Source AS

16

Destination AS

17

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

IPv6 Option Headers

64

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS-IPv6 Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv6 template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-IPv6 template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-IPv6 template is supported for the QFX10002-60C switch. Table 17 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 17: IPFIX MPLS-IPv6 Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

IPv6 Source Mask

29

IPv6 Destination Mask

30

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

IP protocol version of IP payload on MPLS VPN

60

Ingress Interface Type

368

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

MPLS Label 3

72

MPLS Top Label IPv6 Address

140

Fields Included in the IPFIX MPLS-IPv6 Template for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Table 18 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 18: IPFIX MPLS-IPv6 Template Fields for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

IPv6 Source Mask

29

IPv6 Destination Mask

30

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

IP protocol version of IP payload on MPLS VPN

60

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

MPLS Label 3

72

MPLS Top Label IPv6 Address

140

Fields Included in the IPFIX MPLS Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the IPFIX MPLS template is supported. Table 19 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 19: IPFIX MPLS Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

Input Interface

10

Output Interface

14

Flow End Reason

136

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS template is supported for the QFX10002-60C switch. Table 20 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 20: IPFIX MPLS Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Field

Element ID

Input Interface

10

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Ingress Interface Type

368

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

Fields Included in the IPFIX MPLS Template for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Table 21 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 21: IPFIX MPLS Template Fields for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Field

Element ID

Input Interface

10

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

Fields Included in the IPFIX MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Within an IP Network and Having an IPv4 Payload

Starting in Junos OS Release 18.1R1, the IPFIX MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 22 shows the fields that are available in the IPFIX template for MPLS-over-UDP flows that are within an IP network and have an IPv4 payload. The fields are shown in the order in which they appear in the template.

Table 22: IPFIX MPLS-over-UDP Carried on IP Network Template Fields (IPv4 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP IPv4 next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv4 source address of tunnel payload

8

IPv4 destination address of tunnel payload

12

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Encapsulated in an RSVP-TE LSP and Having an IPv4 Payload

Starting in Junos OS Release 18.1R1, the IPFIX MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 23 shows the fields that are available in the IPFIX template for MPLS-over-UDP flows that are encapsulated in an RSVP-TE LSP in the inner MPLS network and have an IPv4 payload. The fields are shown in the order in which they appear in the template.

Table 23: IPFIX MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv4 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP IPv4 next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv4 source address of tunnel payload

8

IPv4 destination address of tunnel payload

12

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Within an IP Network Having an IPv6 Payload

Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 24 shows the fields that are available in the IPFIX template for MPLS-over-UDP flows that are within an IP network and have an IPv6 payload. The fields are shown in the order in which they appear in the template.

Table 24: IPFIX MPLS-over-UDP Carried on IP Network Template Fields (IPv6 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv6 source address of tunnel payload

27

IPv6 destination address of tunnel payload

28

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type V6

139

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Encapsulated in an RSVP-TE LSP and Having an IPv6 Payload

Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 25 shows the fields that are available in the IPFIX template for MPLS-over-UDP flows that are encapsulated in an RSVP-TE LSP in the inner MPLS network and have an IPv6 payload. The fields are shown in the order in which they appear in the template.

Table 25: IPFIX MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv6 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv6 source address of tunnel payload

27

IPv6 destination address of tunnel payload

28

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type V6

139

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the IPFIX VPLS Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the IPFIX VPLS template is supported. Table 26 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 26: IPFIX VPLS Template Fields for MX, M, and T Series

Field

Element ID

Destination MAC

80

Source MAC

56

Ethernet Type

256

Input Interface

10

Output Interface

14

Flow End Reason

136

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

152

Time the flow ended with respect to Epoch time

153

Fields Included in the Version 9 Bridge Template for MX Series

Table 27 shows the fields that are included in the version 9 Bridge template. The fields are shown in the order in which they appear in the template.

Table 27: Version 9 Bridge Template Fields for MX

Field

Element ID

Destination MAC

80

Source MAC

56

Ethernet Type

256

Input SNMP

10

Output SNMP

14

Flow End Reason

136

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to Epoch time

22

Time the flow ended with respect to Epoch time

21

Fields Included in the Version 9 IPv4 Template for MX, M, and T Series

Table 28 shows the fields that are included in the version 9 IPv4 template. The fields are shown in the order in which they appear in the template.

Table 28: Version 9 IPv4 Template Fields for MX, M, and T Series

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

VLAN ID

58

IPv4 Source Mask

9

IPv4 Destination Mask

13

Source AS

16

Destination AS

17

IPv4 Next Hop Address

15

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

Internet Protocol Version

60

BGP IPv4 Next Hop Address

18

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 IPv4 Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Table 29 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 29: Version 9 IPv4 Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Fields Included in the Version 9 IPv4 Template for PTX10003-160C, PTX10003-80C, PTX10004, PTX10008 (with the JNP10008-SF3), and PTX10001-36MR Routers

Table 30 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 30: Version 9 IPv4 Template Fields for PTX10003-160C, PTX10003-80C, PTX10004, PTX10008 (with the JNP10008-SF3), and PTX10001-36MR Routers

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input SNMP Index

10

IPv4 Source Mask

9

IPv4 Destination Mask

13

Source AS

16

Destination AS

17

IPv4 Next Hop Address

15

BGP IPv4 Next Hop Address

18

TCP Flags

6

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IP Protocol Version

60

Output SNMP Index

14

Fields Included in the Version 9 IPv4 Template for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100 Routers

Table 31 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 31: Version 9 IPv4 Template Fields for ACX7024X, ACX7332, and ACX7348, ACX7509, and ACX7100 Routers

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 TOS

5

IPv4 Protocol

4

Source Port

7

Destination Port

11

ICMP Type and Code

32

Input SNMP Index

10

Source AS

16

Destination AS

17

BGP Next Hop Address

18

Output SNMP Index

14

Number of Bytes

1

Number of Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

IP Protocol Version

60

Fields Included in the Version 9 IPv6 Template for MX, M, and T Series

Starting in Junos OS Release 18.1R1, the version 9 IPv6 template is supported. Table 32 shows the fields in the template. The fields are shown in the order in which they appear in the template.

Table 32: Version 9 IPv6 Template Fields for MX, M, and T Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

139

Input Interface

10

VLAN ID

58

IPv6 Source Mask

29

IPv6 Destination Mask

30

Source AS

16

Destination AS

17

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

IPv6 Option Headers

64

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 IPv6 Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Table 33 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 33: IPv6 Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3SIB), PTX10016 Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

IPv6 BGP NextHop Address

63

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

IP Protocol Version

60

Fields Included in the Version 9 IPv6 Template for PTX10003-160C, PTX10003-80C, PTX10004, PTX10008 (with the JNP10008-SF3), and PTX10001-36MR routers

Table 34 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 34: IPv6 Template Fields for PTX10003-160C, PTX10003-80C, PTX10004, PTX10008 (with the JNP10008-SF3), and PTX10001-36MR routers

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input SNMP Index

10

Output SNMP Index

14

IPv6 Source Mask

29

IPv6 DestinationMask

30

Source AS

16

Destination AS

17

IPv6 Next Hop Address

62

TCP Flags

6

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IP Protocol Version

60

Fields Included in the Version 9 IPv6 Template for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100

Table 35 shows the fields that are available in the template. The fields are shown in the order in which they appear in the template.

Table 35: Version 9 IPv6 Template Fields for ACX7024X, ACX7332, ACX7348, ACX7509, and ACX7100 Routers

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 TOS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

IPv6 Source Mask

29

IPv6 Destination Mask

30

TCP Flags

6

IP Protocol Version

60

Source AS

16

Destination AS

17

IPv6 BGP Next Hop Address

63

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Next Hop Address

62

Fields Included in the Version 9 MPLS-IPv4 Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the version 9 MPLS-IPv4 template is supported. Table 36 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 36: Version 9 MPLS-IPv4 Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IP Address

47

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

VLAN ID

58

IPv4 Source Mask

9

IPv4 Destination Mask

13

Source AS

16

Destination AS

17

IPv4 Next Hop Address

15

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

IP Protocol Version

60

BGP IPv4 Next Hop Address

18

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS-IPv4 Template for PTX Series and the QFX10002-60C Switch

Starting in Junos OS Release 18.2R1, the version 9 MPLS-IPv4 template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the version 9 MPLS-IPv4 template is supported for the PTX1002-60C router. Starting in Junos OS Release 21.2R1, the version 9 MPLS-IPv4 template is supported for the QFX10002-60C switch. Table 37 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 37: Version 9 MPLS-IPv4 Template Fields for PTX Series and the QFX10002-60C Switch

Field

Element ID

IPv4 Source Address

8

IPv4 Destination Address

12

IPv4 ToS

5

IPv4 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code

32

Input Interface

10

Source AS

16

Destination AS

17

BGP IPv4 Next Hop Address

18

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv4 Next Hop Address

15

IPv4 Source Mask

9

IPv4 Destination Mask

13

TCP Flags

6

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IP Address

47

Fields Included in the Version 9 MPLS-IPv6 Template for MX, M, and T Series

Starting in Junos OS Release 18.4R1, the version 9 MPLS-IPv6 template is supported for the MX Series. Table 38 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 38: Version 9 MPLS-IPv6 Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

MPLS Top Label IP Address (Only IPv4 top label addresses are exported. IPv6 top label addresses report a value of zero.)

47

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

139

Input Interface

10

VLAN ID

58

IPv6 Source Mask

29

IPv6 Destination Mask

30

Source AS

16

Destination AS

17

IPv6 Next Hop Address

62

IPv6 BGP Next Hop Address

63

TCP Flags

6

Output Interface

14

Minimum TTL

52

Maximum TTL

53

Flow End Reason

136

Flow Direction

61

802.1Q VLAN identifier (dot1qVlanId)

243

802.1Q Customer VLAN identifier (dot1qCustomerVlanId)

245

IP Identifier

54

IPv6 Option Headers

64

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS-IPv6 Template for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Starting in Junos OS Release 18.2R1, the version 9 MPLS-IPv6 template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the version 9 MPLS-IPv6 template is supported for the PTX1002-60C router. Starting in Junos OS Release 21.2R1, the version 9 MPLS-IPv6 template is supported for the QFX10002-60C switch. Table 39 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 39: Version 9 MPLS-IPv6 Template Fields for PTX3000, PTX5000, PTX1000, PTX10001-20C, PTX10002-60C, QFX10002-60C, PTX10008 (without the JNP10008-SF3), PTX10016 Series

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

32

Input Interface

10

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Source Mask

29

IPv6 Destination Mask

30

IPv6 Next Hop Address

62

IPv6 BGP NextHop Address

63

TCP Flags

6

IP protocol version of IP payload on MPLS VPN

60

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

MPLS Label 3

72

MPLS Top Label IP Address

47

Fields Included in the Version 9 MPLS-IPv6 Template for PTX10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-LC1202 line card and the JNP10008-SF3), and PTX10001-36MR

Table 40 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 40: Version 9 MPLS-IPv6 Template Fields for PTX 10003, PTX10004, PTX10008 (with the JNP10K-LC1201 or JNP10K-1202-36MR line card and the JNP10008-SF3), and PTX10001-36MR Routers

Field

Element ID

IPv6 Source Address

27

IPv6 Destination Address

28

IPv6 ToS

5

IPv6 Protocol

4

L4 Source Port

7

L4 Destination Port

11

ICMP Type and Code (IPv6)

32

Input Interface

10

Source AS

16

Destination AS

17

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

IPv6 Source Mask

29

IPv6 Destination Mask

30

IPv6 Next Hop Address

62

TCP Flags

6

IP protocol version of IP payload on MPLS VPN

60

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

MPLS Label 3

72

MPLS Top Label IP Address

47

Fields Included in the Version 9 MPLS Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the version 9 MPLS template is supported. Table 41 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 41: Version 9 MPLS Template Fields for MX, M, and T Series

Field

Element ID

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

Input Interface

10

Output Interface

14

Flow End Reason

136

Number of Flow Bytes

1

Number of Flow Packets

2

First Switched

ww

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS Template for PTX Series and the QFX10002-60C Switch

Starting in Junos OS Release 18.2R1, the version 9 MPLS template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS template is supported for the QFX10002-60C switch. Table 42 shows the fields that are included in the template.

Table 42: Version 9 MPLS Template Fields for PTX Series and the QFX10002-60C Switch

Field

Element ID

Input Interface

10

Output Interface

14

Number of Flow Bytes

1

Number of Flow Packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

MPLS Label 1

70

MPLS Label 2

71

MPLS Label 3

72

Fields Included in the Version 9 MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Within an IP Network Having an IPv4 Payload

Starting in Junos OS Release 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 43 shows the fields that are available in the Version 9 template for MPLS-over-UDP flows that are within an IP network and have an IPv4 payload. The fields are shown in the order in which they appear in the template.

Table 43: Version 9 MPLS-over-UDP Carried on IP Network Template Fields (IPv4 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP IPv4 next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv4 source address of tunnel payload

8

IPv4 destination address of tunnel payload

12

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Encapsulated in an RSVP-TE LSP and Having an IPv4 Payload

Starting in Junos OS Release 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 44 shows the fields that are available in the Version 9 template for MPLS-over-UDP flows that are encapsulated in an RSVP-TE LSP in the inner MPLS network and have an IPv4 payload. The fields are shown in the order in which they appear in the template.

Table 44: Version 9 MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv4 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP IPv4 next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv4 source address of tunnel payload

8

IPv4 destination address of tunnel payload

12

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Within an IP Network Having an IPv6 Payload

Starting in Junos OS Release 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 45 shows the fields that are available in the Version 9 template for MPLS-over-UDP flows that are within an IP network and have an IPv6 payload. The fields are shown in the order in which they appear in the template.

Table 45: Version 9 MPLS-over-UDP Carried on IP Network Template Fields (IPv6 Payload) for PTX Series and the QFX10002-60C Switch

Field

Element ID

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv6 source address of tunnel payload

27

IPv6 destination address of tunnel payload

28

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type V6

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Fields Included in the Version 9 MPLS-over-UDP Template for PTX Series and the QFX10002-60C Switch for Flows Encapsulated in an RSVP-TE LSP and Having an IPv6 Payload

Starting in Junos OS Release 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series. Starting in Junos OS Release 19.4R1, the IPFIX MPLS-over-UDP template is supported for the PTX10002-60C router. Starting in Junos OS Release 21.2R1, the IPFIX MPLS-over-UDP template is supported for the QFX10002-60C switch.

Inline active flow monitoring for MPLS-over-UDP traffic is not supported on the PTX10001-36MR, PTX10003, PTX10004, and PTX10008 (with the JNP10008-SF3) routers.

Table 46 shows the fields that are available in the Version 9 template for MPLS-over-UDP flows that are encapsulated in an RSVP-TE LSP in the inner MPLS network and have an IPv6 payload. The fields are shown in the order in which they appear in the template.

Table 46: Version 9 MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv6 Payload) for PTX Series and QFX10002-60C Switch

Field

Element ID

RSVP label (top MPLS label stack entry) for MPLS tunnel

70

RSVP label pushed before top label

71

IPv4 source address for tunnel endpoint

8

IPv4 destination address for tunnel endpoint

12

UDP source port for tunnel endpoint

7

Tunnel endpoint destination transport port

11

IPv4 source mask for tunnel source IP address

9

IPv4 destination mask for tunnel destination IP address

13

Source AS for tunnel

16

Destination AS for tunnel

17

IPv4 next hop address—gateway for tunnel destination IP address

15

BGP next hop address—tunnel destination IP BGP peer

18

Input SNMP index

10

Output SNMP index

14

MPLS label 1—VPN bottom of stack label

70

IP protocol version of IP payload on MPLS VPN

60

IPv6 source address of tunnel payload

27

IPv6 destination address of tunnel payload

28

IP protocol of tunnel payload

4

IP TOS

5

Source transport port

7

Destination transport port

11

ICMP type

32

TCP flags

6

Number of flow bytes

1

Number of flow packets

2

Time the flow started with respect to system up time (FPC up time)

22

Time the flow ended with respect to system up time (FPC up time)

21

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
23.4R1-EVO
Starting in Junos OS Evolved 23.4R1 for the ACX7024X, ACX7332, and ACX7348 routers, we support ingress and egress sampling of IPv4 and IPv6 traffic on aggregated Ethernet and IRB interfaces and interfaces mapped to non-default VRFs, for both the IPFIX and version 9 export formats. You can configure up to four IPv4 collectors for inline active flow monitoring.
23.1R1-EVO
Starting in Junos OS Evolved Release 23.1R1, for the PTX10001-36MR, PTX10003, and PTX10004 routers, as well as the PTX10008 and PTX10016 routers (with the JNP10K-LC1201 or the JNP10K-LC1202 line card and the JNP10008-SF3) routers, we support IPv6 addresses for IPFIX and version 9 collectors. You can configure either IPv4 or IPv6 collectors for each family within a sampling instance; you cannot specify both for the same family. You can specify up to four collectors for each family. You specify the destination server address with the flow-server address statement and the source address with the inline-jflow source-address address statement at the [edit forwarding-options sampling instance name family (inet | inet6 | mpls) output] hierarchy level.
23.1R1-EVO
Starting in Junos OS Evolved 23.1R1 for the ACX7100 and ACX7509 routers, we support ingress and egress sampling of IPv4 and IPv6 traffic on aggregated Ethernet and IRB interfaces and interfaces mapped to non-default VRFs, for both the IPFIX and version 9 export formats. You can configure up to four IPv4 collectors for inline active flow monitoring.
22.4R1
Starting in Junos OS Release 22.4R1 for the MX240, MX480, MX960, MX10004, MX10008, MX2008, MX2010, and MX2020 routers, we support ingress and egress sampling of IPv4, IPv6, and MPLS traffic on abstracted fabric (af) interfaces between guest network functions (GNFs) in a node slicing scenario, for both the IPFIX and version 9 export formats.
22.2R1-EVO
Starting in Junos OS Evolved 22.2R1 for PTX Series routers, two more information elements have been added to the IPFIX IPv4 and IPv6 templates. These elements carry the packet loss priority (PLP) values and the first two characters of the configured forwarding class name that the sampled packet carries. The collector uses these elements to derive the DiffServ code point (DSCP) bits that the packet would contain while exiting the router.
22.2R1-EVO
Starting in Junos OS Evolved Release 22.2R1 for the PTX10003 router, Information Element 63, IPv6 BGP NextHop Address, is available in both the IPv6 template and the MPLS-IPv6 template for the IPFIX and version 9 export formats.
21.4R1-EVO
Starting in Junos OS Evolved Release 21.4R1 for PTX Series, you can export BGP community and AS path information using IP Flow Information Export (IPFIX) information elements 483 through 491, 16, and 17, per RFCs 8549 and 6313. Content providers can use this information to identify a transit service provider degrading the quality of the service. You configure these elements with the statement data-record-fields at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level.
21.3R1-EVO
Starting in Junos OS Evolved Release 21.3R1 for the PTX10001-36MR, PTX10004, and PTX10008 routers, Information Element 63, IPv6 BGP NextHop Address, is available in both the IPv6 template and the MPLS-IPv6 template for the IPFIX and version 9 export formats.
21.3R1
Starting with Junos OS Release 21.3R1 for PTX Series routers, no flows are maintained. Every sampled packet is considered to be a flow. When the sampled packet is received, the flow is created and immediately timed out as inactive, and the software exports a record to the collector. Therefore, the number of records sent to the collector is higher than before.
21.2R1-Evo
Starting with Junos OS Evolved 21.2R1, no flows are maintained. Every sampled packet is considered to be a flow. When the sampled packet is received, the flow is created and immediately timed out as inactive, and the software exports a record to the collector. Therefore, the number of records sent to the collector is higher than before.
21.2R1
Starting with Junos OS Release 21.2R1 on the QFX10002-60C switch, you can perform inline active flow monitoring for MPLS-over-UDP flows to look past the tunnel header to sample and report on the inner payload at both the transit and egress nodes of the tunnel. MPLS IPv4 and IPv6 payloads and IPFIX and version 9 templates are supported. Only ingress sampling is supported.
21.1R1-EVO
Starting with Junos OS Evolved 21.1R1, for the PTX10004 router, you can configure up to four collectors for inline active flow monitoring.
20.4R1-EVO
Starting with Junos OS Evolved 20.4R1, for the PTX10001-36MR and the PTX10008 (with the JNP10K-LC1202 line card and the JNP10008-SF3) routers, you can configure up to four collectors for inline active flow monitoring.
20.3R1-EVO
Starting with Junos OS Evolved 20.3R1, for the PTX10003 and PTX10008 (with the JNP10K-LC1201 line card and the JNP10008-SF3) routers, you can configure up to four collectors for inline active flow monitoring.
20.3R1
Starting in Junos OS Release 20.3R1 for PTX1000, PTX10008 (without the JNP10008-SF3), and PTX10016), two more information elements have been added to the IPFIX IPv4 and IPv6 templates. These elements carry the packet loss priority (PLP) values and the first two characters of the configured forwarding class name that the sampled packet carries. The collector uses these elements to derive the DiffServ code point (DSCP) bits that the packet would contain while exiting the router. To use these elements, you must configure the next-hop-learning enable statement at the [edit services flow-monitoring version-ipfix template name] hierarchy level.
19.4R1
Starting with Junos OS Release 19.4R1 on the PTX10002-60C router, you can perform flow monitoring for MPLS-over-UDP flows to look past the tunnel header to sample and report on the inner payload at both the transit and egress nodes of the tunnel. MPLS IPv4 and IPv6 payloads and IPFIX and version 9 templates are supported. Only ingress sampling is supported.
19.3R2
Inline active flow monitoring is not supported when you enable Next Gen Services on an MX Series router.
19.2R1
Starting in Junos OS Release 19.2R1 for MX and PTX Series routers, Information Element 63, IPv6 BGP NextHop Address, is available in both the IPv6 template and the MPLS-IPv6 template for the IPFIX and version 9 export formats.
18.4R1
Starting in Junos OS Release 18.4R1, you can configure inline active flow monitoring for MPLS-IPv6 traffic for MX Series routers.
18.4R1
Starting in Junos OS Release 18.4R1, the IPFIX and version 9 MPLS-IPv6 templates are supported for the MX Series.
18.2R1
Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for MPLS, MPLS-IPv4, and MPLS-IPv6 traffic for PTX3000 and PTX5000 Series routers.
18.2R1
Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for bridge traffic for MX Series routers.
18.2R1
Starting in Junos OS Release 18.2R1, the IPFIX and version 9 MPLS templates are supported for the PTX Series.
18.2R1
Starting in Junos OS Release 18.2R1, the IPFIX and version 9 MPLS-IPv4 templates are supported for the PTX Series.
18.2R1
Starting in Junos OS Release 18.2R1, the IPFIX and version 9 MPLS-IPv6 templates are supported for the PTX Series.
18.1R1
Starting in Junos OS Release 18.1R1, you can also apply version 9 flow templates to IPv6 traffic.
18.1R1
Starting in Junos OS Release 18.1R1, you can configure inline active flow monitoring for MPLS-over-UDP traffic for PTX3000 and PTX5000 Series routers.
18.1R1
Starting in Junos OS Release 18.1R1, the IPFIX and version 9 MPLS-over-UDP templates are supported for the PTX Series.
17.4R1
Starting with Junos OS Release 17.4R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10008 and QFX10016 switches.
17.2R1
Starting with Junos OS Release 17.2R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10002 switches.
16.1R4
In Junos OS Release 16.2 and in Junos OS Release 16.1R3 and earlier, you can configure only one collector under a family for inline active flow monitoring. Starting with Junos OS Release 16.1R4 and 17.2R1, you can configure up to four collectors under a family for inline active flow monitoring.
16.1R1
Starting in 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, you can also apply IPFIX and version 9 flow templates to MPLS and MPLS-IPv4 traffic.
16.1R1
Flow Direction (Starting in Junos OS Release 16.1R1)
16.1R1
Starting in Junos OS Release 16.1R1, the IPFIX VPLS template is supported.
15.1F7
Starting in Junos OS Release 15.1F7 for the MX5, MX10, MX40, MX80, MX104, MX240, MX480, MX960, MX2010, and MX2020 routers, you can configure the report-zero-oif-gw-on-discard at the [edit chassis fpc slot-number inline-services] hierarchy level to set the flow record value to 0 (zero) for the IPFIX information elements ipNextHopIPv6Address (Element ID 62), egressInterface (Element ID 14), and ipNextHopIPv4Address (Element ID 15) for only the flow records for rejected, discarded, and policed flows. You configure this statement to help you track what traffic is being dropped.