Enabling Export of Transit SPRING Statistics
Understanding Enabling Export of Transit SPRING Statistics
Source Packet Routing in Networking (SPRING), also known as segment routing, is a control-plane architecture that enables an ingress router to steer a packet through a specific set of nodes and links in the network. Starting in Junos OS Release 19.1R1, Junos telemetry interface (JTI) supports the export of transit SPRING statistics on PTX3000 routers and PTX5000 routers with FPC2. Use these statistics to monitor traffic, model engineering, and plan capacity.
- About Transit Spring Statistics
- Use a Valid SPRING Configuration
- Enabling Export of Statistics
- Exporting Statistics
About Transit Spring Statistics
Exported statistics are for SPRING traffic and exclude RSVP and LDP-signaled traffic. Family MPLS statistics per interface is accounted for separately. The segment routing statistics also include SPRING traffic statistics per link aggregation group (LAG) member and per segment identifier (SID).
Use a Valid SPRING Configuration
Statistics are not collected without the appropriate SPRING configuration in place. Before you enable SPRING statistics, verify your SPRING configuration on the device from which you will export statistics. Below is a sample Junos OS SPRING configuration.
Ingress Device
user@host# set groups isis protocols isis traffic-engineering family inet shortcuts user@host# set groups isis protocols isis source-packet-routing sensor-based-stats per-sid ingress user@host# set groups isis protocols isis source-packet-routing srgb start-label 400 user@host# set groups isis protocols isis source-packet-routing srgb index-range 20000 user@host# set groups isis protocols isis source-packet-routing node-segment ipv4-index 1 user@host# set groups isis protocols mpls traffic-engineering bgp-igp-both-ribs user@host# set groups isis protocols isis traffic-engineering family inet shortcuts user@host# set groups isis protocols isis traffic-engineering family inet-mpls shortcuts
Transit Device
user@host# set groups isis protocols isis traffic-engineering family inet shortcuts user@host# set groups isis protocols isis source-packet-routing sensor-based-stats per-sid ingress user@host# set groups isis protocols isis source-packet-routing srgb start-label 400 user@host# set groups isis protocols isis source-packet-routing srgb index-range 20000 user@host# set groups isis protocols isis source-packet-routing node-segment ipv4-index 2 user@host# set groups isis system services extension-service request-response grpc clear-text port 32767 user@host# set groups isis system services extension-service request-response grpc max-connections 8 user@host# set groups isis system services extension-service request-response grpc skip-authentication
Egress Device
user@host# set groups isis protocols isis traffic-engineering family inet shortcuts user@host# set groups isis protocols isis source-packet-routing sensor-based-stats per-sid ingress user@host# set groups isis protocols isis source-packet-routing srgb start-label 400 user@host# set groups isis protocols isis source-packet-routing srgb index-range 20000 user@host# set groups isis protocols isis source-packet-routing node-segment ipv4-index 3
For more information about configuring SPRING, see Understanding Source Packet Routing in Networking (SPRING).
Enabling Export of Statistics
To receive statistics, you enable statistical data for export on your Juniper device through the Junos OS. To enable export, configure per-sid-ingress at the [edit protocols isis source-packet-routing] hierarchy level. For an example of how to configure this, see Enabling Collection of SPRING Statistics and Exporting Them.
Exporting Statistics
After you enable telemetry export for transit SPRING statistics, you can stream statistics to an outside collector using either remote procedure call (gRPC) services or a native sensor that exports statistics in UDP-format and requires a Junos OS configuration on the device.
See Also
Enabling Collection of SPRING Statistics and Exporting Them
You can export through Junos telemetry interface (JTI) transit Source Packet Routing in Networking (SPRING) statistics, also known as segment routing statistics.
Before statistics can be exported, they need to be enabled for collection. After statistics are enabled for collection, you choose how they should be exported to an outside collector: gRPC services or a UDP-format using a native sensor.
To enable the export of transit SPRING statistics:
[edit protocols isis source-packet-routing] user@host# set sensor-based-stats per-sid ingress
To export transit SPRING statistics using gRPC services:
Start gRPC services for the device by including the configuration below:
system { services { extension-service { request-response { grpc { clear-text { port 32767; } skip-authentication; } } } } }Create a subscription using the telemetrySubcribe remote procedure call. The subscription must contain telemetry parameters, including the resource path /junos/services/segment-routing/sid/usage/. For more information about configuring gRPC streaming and creating a subscription for statistics to be delivered to an outside collector, see Understanding OpenConfig and gRPC on Junos Telemetry Interface, gRPC Services for Junos Telemetry Interface, and Configure a NETCONF Proxy Telemetry Sensor in Junos.
To export transit SPRING statistics in UDP-format using a native sensor:
Configure the sensor statement at the [
edit services analytics] hierarchy level on the device. Include the sensor path (/junos/services/segment-routing/sid/usage/), an export profile name, a resource identifier string that enables monitoring and streaming of data for the specified system resource, and a server name to collect the data.
For more information about configuring a native sensor, see Configuring a Junos Telemetry Interface Sensor (CLI Procedure).
See Also
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.