source-packet-routing (Junos Telemetry Interface)
Syntax
source-packet-routing {
telemetry {
statistics {
per-source per-segment-list
no-transit;
no-ingress;
}
}
source-routing-path {
use-for-shortcut;
}
}
Hierarchy Level
[edit protocols]
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.
Enabling the parameter per-segment-list will disable tunnel
sensors. For example, configuring per-souorce per-segment-list
will disable the sensor
/junos/services/segment-routing/traffic-engineering/tunnel/ingress/usage/.
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-ingressis issued, ingress sensors are not created.If the statement
set protocols source-packet-routing telemetry statistics no-transitis 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
| statistics | Create 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-list | Create 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-transit | Enable 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-ingress | Enable sensors only for Binding-SID transit routes. |
| source-routing-path | Specify the name of the source routing path. |
| use-for-shortcut | Enable to allow the LSP to be used as a shortcut tunnel. |
Required Privilege Level
routing
Release Information
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.
Statement supported in Junos OS Evolved Release 21.4R1 for PTX10001-36MR, PTX10004, PTX10008, and PTX10016 routers.