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 PTX 3000 routers and PTX 5000 routers with FPC2. Use these statistics to monitor traffic, model engineering, and plan capacity.

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).

Enabling Export of Statistics

To receive statistics, you enable statistical data for export on your Juniper device through the Junos CLI. To enable export, include the

Exporting Statistics

After you enable telemetry export for transit SPRING statistics, they are eligible to be streamed to one or more external collectors by creating a subscription using the telemetrySubcribe remote procedure call (gRPC). The subscription will contain telemetry parameters, including the resource path /junos/services/segment-routing/sid/usage/.

You also must start gRPC services for the device. To start gRPC services, include the configuration below:

For more information about configuring gRPC streaming, see Understanding OpenConfig and gRPC on Junos Telemetry Interface, gRPC Services for Junos Telemetry Interface, and Configure a Telemetry Sensor in Junos.

If you do not want to use gRPC services, you can export statistics by configuring the sensor in the Junos OS. Using this method (native or UDP sensor), you specify 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. To configure the sensor, include the sensor statement at the [edit services analytics] hierarchy level.

For more information about configuring a native sensor, see Configuring a Junos Telemetry Interface Sensor (CLI Procedure).

Enable Export of SPRING Statistics

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 can then export them by including the sensor statement at the [edit services analytics] hierarchy level or by streaming them to one or more external collectors using a remote procedure call (gRPC).

Statistics are not collected without the appropriate segment routing configuration in place. Below is a sample Junos OS segment routing configuration.

Ingress Device

Transit Device

Egress Device

To enable the export of transit SPRING statistics:

  1. Enable sensor-based statistics per segment identifier for the ingress direction:

After you enable telemetry export for transit SPRING statistics, they are eligible to be streamed to one or more external collectors using either a remote procedure call (gRPC) subscription or by configuring the sensor through the Junos OS.

Release History Table
Release
Description
Starting in Junos OS Release 19.1R1, Junos Telemetry Interface (JTI) supports the export of transit SPRING statistics on PTX 3000 routers and PTX 5000 routers with FPC2