Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Source Packet Routing in Networking (SPRING) or Segment Routing

  • Static route resolution over SR-TE tunnel (PTX10001-36MR, PTX10003, and PTX10008)—Starting in Junos OS Release 21.2R1, we support static route resolution over segment routing–traffic engineered (SR-TE) colored and uncolored label-switched paths (LSPs). To enable this feature, configure the spring-te-lsp-next-hop statement at the [edit routing-options static destination] and [edit routing-options rib rib name static destination] hierarchy levels. The feature support extends towards static, DTM, BGP-SR-TE, and PCEP source types that are currently supported by Source Packet Routing in Networking–Traffic Engineering (SPRING-TE). If a source is not configured, by default, it takes the next hop as static.

    You must configure the tunnel-tracking statement at the [edit protocols source-packet-routing] hierarchy level to enable this feature. This feature enhances the accuracy of first-hop label-based tunnel status for SR-TE tunnels according to their route resolution.

    [See spring-te-lsp-next-hop and source-packet-routing.]

  • Distributed Constrained Shortest Path First (CSPF) for Segment Routing Traffic Engineering (SR-TE) paths (PTX10004, PTX10008)—Starting in Junos OS Evolved release 21.2R1 we support distributed CSPF for segment routing LSPs. With distributed CSPF for segment routing, LSPs are optimized by the ingress device based on the configured constraints and metric type (traffic-engineering or IGP). The LSPs are computed to utilize the available ECMP paths to the destination with segment routing label stack compression enabled or disabled.

    [See Enabling Distributed CSPF for Segment Routing LSPs.]