Description

This article explains the alternative way of checking Metric for SR LSPs configured statically or via SR-TE Policy.

Solution

Below is the command used to check Metric configured for any SR-TE LSP

root@r0-RE0-re0> show spring-traffic-engineering route extensive
To : 12035<c>
Distinguisher : 0
Tunnel-source : Static configuration
Route Nexthop Type: Composite Indirect
Route Metric2 : 20
Route Forward Type : SRMPLS, Encap Mode : N/A
  LSP Name: POLICY_465035_IPV4
  SR Preference : 100, SR Preference Override : 100
  Metric : 10000
  State : Up
  LSP ID : 6
  Telemetry statistics:
  Sensor-name: 0.0.0.0-2f03, Id: 3758096388
  Sensor-name: 7fee1-0.0.0.0-2f03, Id: 3758096389
    LSP Path Name: SL_400625
    LSP Path Bandwidth: 10
    Weight: 1, Balance: Primary
      SR-ERO hop count: 1
        Hop 1 (Loose):
          NAI: None
          SID type: 20-bit label, Value: 400104

This command was introduced via below PR and is available in later Junos/EVO releases.

1502646 [Confidential]-RLI 43384 Tracking PR: Godzilla: SR-TE Re engineering catch all (show spring-traffic-engineering route and SRTE ATF fixes)
 
 

Modification History

2024-07-26 : Article Created