Per-Path or Per-Segment-List Traffic Statistics
The Segment Routing Traffic Engineering (SRTE) Traffic Statistics Collection feature enables you to gather traffic statistics for both ingress IP traffic and transit MPLS traffic traversing SRTE tunnels. This functionality allows you to configure statistics at both the tunnel level and the per-path level, providing granular insights into traffic flow. This section describes about the applied per-path or per-segment-list traffic statistics that is unique for each sub candidate path of a SRTE tunnel.
You can configure per-segment-list to enable SRTE to generate a sensor ID and statistics handler. The statistics handler, including the sensor ID, is downloaded as part of SRTE route gateways. It is used in the gateway during route programming, pushing sensor information to the Packet Forwarding Engine (PFE) if the route is downloaded to the Forwarding Information Base (FIB). To collect traffic statistics from the PFE, two optional path-level sensors are available: Ingress and Transit.
Sensor name generation varies for colored and uncolored tunnels.
-
For colored tunnels, the sensor name format remains unchanged. The segment ID, previously filled with the sub-candidate path ID, is now filled with the segment-list ID.
-
For uncolored tunnels, reuse the last component of the sensor name (lsp-name) to fill the segment-list ID instead of the sub-candidate path name. The segment ID is filled in hexadecimal format for both tunnel types.
The sample for sensor name format and the change in sensor name format are highlighted.
Tunnel Type | Sensor Type | Current Format | Format after the change |
Colored | Ingress | 4.4.4.4-2-1e-0-0.0.0.0-0-80 | 4.4.4.4-2-1e-0-0.0.0.0-0-80 |
Transit | 4.4.4.4-2-1e-0-0.0.0.0-0-80-f4241 | 4.4.4.4-2-1e-0-0.0.0.0-0-80-f4241 | |
Uncolored | Ingress | i;st;0;f;tunnel-1;SCpath1 | i;st;0;f;tunnel-1;80 |
Transit | t;st;0;f;tunnel-1;SCpath1 | t;st;0;f;tunnel-1;80 |
Configuring Per-Path Traffic Statistics
Configuration
By configuring per-segment-list sensor, a unique telemetry sensor is created for each segment-list.
user@host# show protocols source-packet-routing telemetry statistics { per-source { per-segment-list; } } user@host# show protocols source-packet-routing segment-list SCpath2 hop1 label 400300; hop2 label 400400; {master}[edit] user@host# show protocols source-packet-routing segment-list SCpath1 hop1 label 400400; user@host# show protocols source-packet-routing source-routing-path tunnel-1 to 4.4.4.4; binding-sid 1000010; primary { SCpath1; SCpath2; } user@host# show spring-traffic-engineering lsp name tunnel-1 detail
Name: tunnel-1 Tunnel-source: Static configuration Tunnel Forward Type: SRMPLS To: 4.4.4.4-10<c> Binding SID Label:1000010 20 Bit MPLS Label, State: Allocated State: Up Path: SCpath1 Path Status: Up Outgoing interface: NA Auto-translate status: Disabled Auto-translate result: N/A Compute Status:Enabled , Compute Result:success , Compute-Profile Name:pro1 Total number of computed paths: 2 Segment ID : 128 Telemetry Ingress statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-80, Id: 3758096417 Telemetry transit statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-80-f424a, Id: 3758096418 Computed-path-index: 1 BFD status: N/A BFD name: N/A BFD remote-discriminator: N/A TE metric: 30, IGP metric: 30 Delay metrics: Min: 50331645, Max: 50331645, Avg: 50331645 Metric optimized by type: TE computed segments count: 3 computed segment : 1 (computed-adjacency-segment): label: 400103 source router-id: 1.1.1.1, destination router-id: 2.2.2.2 source interface-address: 11.2.1.1, destination interface-address: 11.2.1.2 computed segment : 2 (computed-adjacency-segment): label: 400202 source router-id: 2.2.2.2, destination router-id: 3.3.3.3 source interface-address: 22.1.1.2, destination interface-address: 22.1.1.3 computed segment : 3 (computed-adjacency-segment): label: 400301 source router-id: 3.3.3.3, destination router-id: 4.4.4.4 source interface-address: 33.1.1.3, destination interface-address: 33.1.1.4 Segment ID : 129 Telemetry Ingress statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-81, Id: 3758096419 Telemetry transit statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-81-f424a, Id: 3758096420 Computed-path-index: 2 BFD status: N/A BFD name: N/A BFD remote-discriminator: N/A TE metric: 30, IGP metric: 30 Delay metrics: Min: 50331645, Max: 50331645, Avg: 50331645 Metric optimized by type: TE computed segments count: 3 computed segment : 1 (computed-adjacency-segment): label: 400105 source router-id: 1.1.1.1, destination router-id: 2.2.2.2 source interface-address: 11.4.1.1, destination interface-address: 11.4.1.2 computed segment : 2 (computed-adjacency-segment): label: 400202 source router-id: 2.2.2.2, destination router-id: 3.3.3.3 source interface-address: 22.1.1.2, destination interface-address: 22.1.1.3 computed segment : 3 (computed-adjacency-segment): label: 400301 source router-id: 3.3.3.3, destination router-id: 4.4.4.4 source interface-address: 33.1.1.3, destination interface-address: 33.1.1.4 Path: SCpath2 Path Status: Up Outgoing interface: NA Auto-translate status: Disabled Auto-translate result: N/A Compute Status:Enabled , Compute Result:success , Compute-Profile Name:pro2 Total number of computed paths: 2 Segment ID : 256 Telemetry Ingress statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-100, Id: 3758096421 Telemetry transit statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-100-f424a, Id: 3758096422 Computed-path-index: 1 BFD status: N/A BFD name: N/A BFD remote-discriminator: N/A TE metric: 30, IGP metric: 30 Delay metrics: Min: 50331645, Max: 50331645, Avg: 50331645 Metric optimized by type: Minimum-Delay computed segments count: 3 computed segment : 1 (computed-adjacency-segment): label: 400103 source router-id: 1.1.1.1, destination router-id: 2.2.2.2 source interface-address: 11.2.1.1, destination interface-address: 11.2.1.2 computed segment : 2 (computed-adjacency-segment): label: 400202 source router-id: 2.2.2.2, destination router-id: 3.3.3.3 source interface-address: 22.1.1.2, destination interface-address: 22.1.1.3 computed segment : 3 (computed-adjacency-segment): label: 400301 source router-id: 3.3.3.3, destination router-id: 4.4.4.4 source interface-address: 33.1.1.3, destination interface-address: 33.1.1.4 Segment ID : 257 Telemetry Ingress statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-101, Id: 3758096423 Telemetry transit statistics: Sensor-name: 4.4.4.4-a-1e-0-0.0.0.0-0-101-f424a, Id: 3758096424 Computed-path-index: 2 BFD status: N/A BFD name: N/A BFD remote-discriminator: N/A TE metric: 30, IGP metric: 30 Delay metrics: Min: 50331645, Max: 50331645, Avg: 50331645 Metric optimized by type: Minimum-Delay computed segments count: 3 computed segment : 1 (computed-adjacency-segment): label: 400105 source router-id: 1.1.1.1, destination router-id: 2.2.2.2 source interface-address: 11.4.1.1, destination interface-address: 11.4.1.2 computed segment : 2 (computed-adjacency-segment): label: 400202 source router-id: 2.2.2.2, destination router-id: 3.3.3.3 source interface-address: 22.1.1.2, destination interface-address: 22.1.1.3 computed segment : 3 (computed-adjacency-segment): label: 400301 source router-id: 3.3.3.3, destination router-id: 4.4.4.4 source interface-address: 33.1.1.3, destination interface-address: 33.1.1.4