Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Understanding 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. Starting in Junos OS Release 18.1R1, you can configure inline active flow monitoring for MPLS-over-UDP traffic for PTX Series routers. Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for MPLS, MPLS-IPv4, and MPLS-IPv6 traffic for PTX Series routers. Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for bridge traffic for MX Series routers.

Starting in Junos OS Release 18.4R1, you can configure inline active flow monitoring for MPLS-IPv6 traffic for MX Series routers.

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 scalabilty—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. 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.

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

Inline Active Flow Monitoring Limitations and Restrictions

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

  • In Junos OS Release 14.1 and earlier, you can configure inline active flow monitoring on MX Series routers with MPCs/MICs. Starting in Junos OS Release 14.2, you can also configure inline active flow monitoring on T4000 routers with Type 5 FPCs.

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

  • You can configure only one sampling instance on a Flexible PIC Concentrator (FPC).

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

    • 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. If you do not use 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 multilookup 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

The following sections list the fields included in IPFIX and version 9 templates.

Fields Included in the IPFIX Bridge Template for MX Series

Table 1 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 1: 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 2 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 2: 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 PTX Series

Table 3 shows the fields that are available in the IPFIX IPv4 template.

Table 3: IPFIX IPv4 Template Fields for PTX 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

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

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

Table 4: 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 NextHop 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 PTX Series

Table 9 shows the fields that are available in the IPv6 templates.

Table 5: IPFIX IPv6 Template Fields for PTX 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 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 MPLS-IPv4 Template for MX, M, and T Series

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

Table 6: 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-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 7 shows the fields that are included in the template.

Table 7: 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 NextHop 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-IPv4 Template for PTX Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv4 template is supported for the PTX Series. Table 8 shows the fields that are included in the template.

Table 8: IPFIX MPLS-IPv4 Template Fields for PTX 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-IPv6 Template for PTX Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv6 template is supported for the PTX Series. Table 9 shows the fields that are included in the IPFIX MPLS-IPv6 template.

Table 9: IPFIX MPLS-IPv6 Template Fields for PTX 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 NextHop 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 Template for MX, M, and T Series

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

Table 10: 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 PTX Series

Starting in Junos OS Release 18.2R1, the IPFIX MPLS template is supported for the PTX Series. Table 11 shows the fields that are included in the template.

Table 11: IPFIX MPLS Template Fields for PTX 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-over-UDP Template for PTX Series 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. Table 12 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.

Table 12: IPFIX MPLS-over-UDP Carried on IP Network Template Fields (IPv4 Payload) for PTX Series

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 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. Table 13 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.

Table 13: IPFIX MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv4 Payload) for PTX Series

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 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. Table 14 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.

Table 14: IPFIX MPLS-over-UDP Carried on IP Network Template Fields (IPv6 Payload) for PTX Series

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 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. Table 15 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.

Table 15: IPFIX MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv6 Payload) for PTX Series

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 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 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 17 shows the fields that are included in the version 9Bridge template. The fields are shown in the order in which they appear in the template.

Table 17: 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 18 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 18: 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 PTX Series

Table 19 shows the fields that are available in the IPv4 templates.

Table 19: Version 9 IPv4 Template Fields for PTX 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 IPv6 Template for MX, M, and T Series

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

Table 20: 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 NextHop 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 PTX Series

Table 21 shows the fields that are available in the IPv6 templates.

Table 21: IPv6 Template Fields for PTX 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 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 22 shows the fields that are included in the template. The fields are shown in the order in which they appear in the template.

Table 22: 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-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 23 shows the fields that are included in the template.

Table 23: 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 NextHop 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-IPv4 Template for PTX Series

Starting in Junos OS Release 18.2R1, the version 9 MPLS-IPv4 template is supported for the PTX Series. Table 24 shows the fields that are included in the template.

Table 24: Version 9 MPLS-IPv4 Template Fields for PTX 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

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 PTX Series

Starting in Junos OS Release 18.2R1, the version 9 MPLS-IPv6 template is supported for the PTX Series. Table 25 shows the fields that are included in the version 9 MPLS-IPv6 template.

Table 25: Version 9 MPLS-IPv6 Template Fields for PTX 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 Template for MX, M, and T Series

Starting in Junos OS Release 16.1, the version 9 MPLS 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: 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

Starting in Junos OS Release 18.2R1, the version 9 MPLS template is supported for the PTX Series. Table 27 shows the fields that are included in the template.

Table 27: Version 9 MPLS Template Fields for PTX 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

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 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. Table 28 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.

Table 28: Version 9 MPLS-over-UDP Carried on IP Network Template Fields (IPv4 Payload) for PTX Series

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 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. Table 29 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.

Table 29: Version 9 MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv4 Payload) for PTX Series

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 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. Table 30 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.

Table 30: Version 9 MPLS-over-UDP Carried on IP Network Template Fields (IPv6 Payload) for PTX Series

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 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. Table 31 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.

Table 31: Version 9 MPLS-over-UDP Encapsulated in RSVP-TE LSP Template Fields (IPv6 Payload) for PTX Series

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

Release History Table
Release
Description
Starting in Junos OS Release 18.4R1, you can configure inline active flow monitoring for MPLS-IPv6 traffic for MX Series routers.
Starting in Junos OS Release 18.4R1, the IPFIX MPLS-IPv6 template is supported for the MX Series.
Starting in Junos OS Release 18.4R1, the version 9 MPLS-IPv6 template is supported for the MX Series.
Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for MPLS, MPLS-IPv4, and MPLS-IPv6 traffic for PTX Series routers.
Starting in Junos OS Release 18.2R1, you can configure inline active flow monitoring for bridge traffic for MX Series routers.
Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv4 template is supported for the PTX Series.
Starting in Junos OS Release 18.2R1, the IPFIX MPLS-IPv6 template is supported for the PTX Series.
Starting in Junos OS Release 18.2R1, the IPFIX MPLS template is supported for the PTX Series.
Starting in Junos OS Release 18.2R1, the version 9 MPLS-IPv4 template is supported for the PTX 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 18.2R1, the version 9 MPLS template is supported for the PTX Series.
Starting in Junos OS Release 18.1R1, you can configure inline active flow monitoring for MPLS-over-UDP traffic for PTX Series routers.
Starting in Junos OS Release 18.1R1, you can also apply version 9 flow templates to IPv6 traffic.
Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series.
Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series.
Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series.
Starting in Junos OS Release 18.1R1, the IPFIX MPLS-Over-UDP template is supported for the PTX Series.
Starting with Junos OS Release 17.4R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10008 and QFX10016 switches.
Starting with Junos OS Release 17.2R1, you can apply IPFIX flow templates to unicast IPv4 and IPv6 traffic on QFX10002 switches.
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 Release 16.1R1 and 15.1F2, the IPv4 table is assigned a default value of 1024.
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 16.1, you can also apply IPFIX flow templates to MPLS and MPLS-IPv4 traffic.
Flow Direction (Starting in Junos OS Release 16.1)
Flow Direction (Starting in Junos OS Release 16.1)
Starting in Junos OS Release 16.1, the IPFIX MPLS-IPv4 template is supported.
Starting in Junos OS Release 16.1, the IPFIX MPLS template is supported.
Starting in Junos OS Release 16.1, the IPFIX VPLS template is supported.
Starting in Junos OS Release 18.1R1, the version 9 IPv6 template is supported.
Starting in Junos OS Release 16.1, the version 9 MPLS-IPv4 template is supported.
Starting in Junos OS Release 16.1, the version 9 MPLS template is supported.
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 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series.
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 18.1R1, the version 9 MPLS-over-UDP template is supported for the PTX Series.
Starting in Junos OS Release 14.2, you can also configure inline active flow monitoring on T4000 routers with Type 5 FPCs.