Statement introduced in Junos OS Release 18.3R1.
Option per-source per-segment-list is introduced in Junos OS Release 20,1R1 for MX Series and PTX Series routers.
Statement supported in Junos OS Release 20.2R1 for MX240. MX480, MX960, MX2010, and MX2020 with MPC-10E or MPC-11E routers.
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:
For gRPC streaming:
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:
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.
Required Privilege Level