Configure SR-TE for Uncolored Ingress LSPs
Enable SR-TE telemetry statistics by first configuring SR-TE on a device.
Supporting Uncolored Sensor Paths
Segment routing uses a segment list to enable static segment routing LSPs to steer traffic based on segment routing policies. When a segment list is used by a protocol, the protocol validates these segment identifiers and selects valid segments for traffic engineering.
When configured, the segment-list of a segment routing traffic
engineering (SR-TE) LSP accepts both IP addresses and labels. There are two models
based on these options:
- Direct resolution- In this model, LSP accepts the IP address as the first hop.
- Indirect resolution- This model uses only labels.
Table 1 shows the segment routing traffic engineering (SR-TE) ingress sensors that would be installed on the packet forwarding engine In order to view the statistics that are being enabled in an SR-TE configuration.
|
Path |
Sensor |
Sensor Name |
Sensor Subtype |
Description |
|---|---|---|---|---|
|
2 |
/junos/services/segment-routing/traffic-engineering/tunnel/ingress/usage/ |
ingress-lsp1 |
SRTE TUNNEL INGRESS |
Streams uncolored SR-TE tunnel statistics. |
|
3 |
/junos/services/segment-routing/traffic-engineering/tunnel/lsp/ingress/usage/ |
i;st;0;f;lsp1;path1 i;st;0;f;lsp1;path2 |
SRTE PER-TUNNEL PER-LSP INGRESS |
Streams uncolored SR-TE per-tunnel statistics. |
In order to stream statistics for these sensors, you must configure SR-TE for each path and enable statistics in order to collect data that can be streamed through a sensor subscription from a device to a collector. See the sections below for sample configurations and operational mode output.
Configure SR-TE for Uncolored SR-TE Tunnel Statistics
To stream uncolored SR-TE tunnel statistics, refer to the uncolored SR-TE configuration below to create a segment list and enable static segment routing LSPs to steer traffic based on segment routing policies.
Configure Path 2
[edit] set protocols source-packet-routing segment-list path1 hop1 label 50100 set protocols source-packet-routing segment-list path2 hop1 label 50100 set protocols source-packet-routing source-routing-path lsp1 to 100.100.100.100 set protocols source-packet-routing source-routing-path lsp1 primary path1 set protocols source-packet-routing source-routing-path lsp1 primary path2 set protocols source-packet-routing telemetry statistics
Use the show agent sensors detail operational mode command to
display ingress-lsp1 sensor details.
user@host> show agent sensors detail SID Name Type Subtype Packets Bytes Requests Replies Count CounterTokens[updates] 281478734807051 ingress-lsp1 SR srte-uncolored-ingress 10 920 12 12 1 1615[36],
Configure SR-TE for Uncolored SR-TE Per-tunnel Statistics
To stream uncolored SR-TE per-tunnel statistics, refer to the uncolored SR-TE configuration below to create a segment list and enable static segment routing LSPs to steer traffic based on segment routing policies.
Configure Path 3
[edit] set protocols source-packet-routing segment-list path1 hop1 label 50100 set protocols source-packet-routing segment-list path2 hop1 label 50100 set protocols source-packet-routing source-routing-path lsp1 to 100.100.100.100 set protocols source-packet-routing source-routing-path lsp1 primary path1 set protocols source-packet-routing source-routing-path lsp1 primary path2 set protocols source-packet-routing telemetry statistics per-source per-segment-list
Use the show agent sensors detail operational mode command to
display sensor i;st;0;f;lsp1;path1 and sensor
i;st;0;f;lsp1;path2 details.
user@host> show agent sensors detail SID Name Type Subtype Packets Bytes Requests Replies Count CounterTokens[updates] 281478734807049 i;st;0;f;lsp1;path1 SR srte-per-lsp-ingress 6 552 24 24 1 1611[18514], 281478734807050 i;st;0;f;lsp1;path2 SR srte-per-lsp-ingress 0 0 24 0 1 1 1615[36],