tunnel-observation

Syntax

Hierarchy Level

Description

Specify the types of MPLS flows on which to enable inline flow monitoring. If you do not configure a tunnel-observation type, then plain MPLS flow records are created.

You can configure multiple values for tunnel-observation. Flows are created for only the deepest match. For example, if you configure both ipv4 and mpls-over-udp and the traffic type is MPLS-over-UDP, flows are created for MPLS-over-UDP. If you configure ipv4 but do not configure mpls-over-udp and the traffic type is MPLS-over-UDP, flows are created for MPLS-IPv4.

If the MPLS traffic type does not match any of the tunnel-observation values, then plain MPLS flows are created.

If you do not configure tunnel-observation, plain MPLS flows are created.

If the tunnel-observation statement is added or deleted, or if the configured value is changed, all flows related to the old template will be deleted and replaced by new flows using the changed template.

Options

ipv4	Enable flow monitoring for MPLS-IPv4 traffic. You must also configure `mpls-template` at the `[edit services flow-monitoring (version9 \| version-ipfix) template template-name]` hierarchy level.
ipv6	Enable flow monitoring for MPLS-IPv6 traffic. You must also configure `mpls-template` at the `[edit services flow-monitoring (version9 \| version-ipfix) template template-name]` hierarchy level. If you are running inline flow monitoring on a Lookup (LU) card on an MX Series router, you must also configure `use-extended-flow-memory` at the `[edit chassis fpc slot-number inline-services]` hierarchy level to create MPLS-IPv6 flow records.
mpls-over-udp	(PTX Series only) Enable flow monitoring for MPLS-over-UDP traffic. Monitoring looks past the tunnel header to report the inner payload of the packets. For an MPLS-over-UDP flow that is carried between IPv4 endpoints, you must also configure `ipv4-template` at the `[edit services flow-monitoring (version9 \| version-ipfix) template template-name]` hierarchy level. For an MPLS-over-UDP flow that is encapsulated in an RSVP-TE LSP, you must also configure `mpls-ipvx-template` in Junos OS Release 18.1 or `mpls-template` starting in Junos OS 18.2R1 at the `[edit services flow-monitoring (version 9 \| version-ipfix) template template-name]` hierarchy level.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 18.1R1.

ipv4 and ipv6 options added in Junos OS Release 18.2R1.

Statement introduced in Junos OS Release 18.4R1 on MX Series routers.

ON THIS PAGE