Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

source-packet-routing

 

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 18.3R1 for MX Series and PTX Series routers.

Option per-source per-segment-list is introduced in Junos OS Release 20,1R1 for MX Series and PTX Series routers.

Description

Enable BGP and statically configured Segment Routing Traffic Engineering (SR-TE) traffic statistics sensor support for Junos Telemetry Interface (JTI).

Export JTI statistics using either remote procedure call (gRPC) services or UDP native sensors to stream statistics. The following resource paths are supported. For UDP native sensors:

  • /junos/services/segment-routing/traffic-engineering/ingress/usage/

  • /junos/services/segment-routing/traffic-engineering/transit/usage

For gRPC streaming:

  • /mpls/signaling-protocols/segment-routing/

Export SR-TE per Label Switched Path (LSP) route statistics using JTI and gRPC services. Using JTI and gRPC services. You can stream SR-TE telemetry statistics for uncolored SR-TE policies statistics to an outside collector. Ingress statistics include statistics for all traffic steered by means of an SR-TE LSP. Transit statistics include statistics for traffic to the Binding SID (BSID) of the SR-TE policy.

To enable these statistics, include the per-source per-segment-list option at the [edit protocols source-packet-routing telemetry statistics] hierarchy level. When configuring:

  • If the statement set protocols source-packet-routing telemetry statistics no-ingress is issued, ingress sensors are not created.

  • If the statement set protocols source-packet-routing telemetry statistics no-transit is issued, transit sensors are not created. Otherwise, if BSID is configured for a tunnel, transit statistics are created.

The following resource paths (sensors) are supported:

  • /junos/services/segment-routing/traffic-engineering/tunnel/lsp/ingress/usage/

  • /junos/services/segment-routing/traffic-engineering/tunnel/lsp/transit/usage/

For exporting statistics using UDP native sensors, configure parameters at the [edit services analytics] hierarchy level. To provision sensors to export data through gRPC streaming, use the telemetrySubscribe RPC to specify telemetry parameters.

Default

Disabled.

Options

statisticsCreate sensors for both the SR-TE policy nexthop and the binding SID that are installed in the forwarding plane. For the SR-TE policy nexthop, the sensors collect traffic statistics steered by all routes that use the SR-TE policy as a nexthop. For the binding SID, the sensors collect statistics on labeled traffic that is steered by the binding-SID route.
per-source per-segment-listCreate sensors to export SR-TE per LSP route statistics for uncolored SR-TE policies. Ingress statistics include statistics for all traffic steered by means of an SR-TE LSP. Transit statistics include statistics for traffic to the BSID of the SR-TE policy.
no-transitEnable sensors only for SR-TE policy nexthops. The sensor will collect statistics on all steering routes that use the SR-TE policy as a nexthop.
no-ingressEnable sensors only for Binding-SID transit routes.

Required Privilege Level

routing