Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

source-packet-routing (Segment Routing Traffic Engineering)

date_range 20-Aug-24

Syntax

content_copy zoom_out_map
source-packet-routing {
    inherit-label-nexthops;
    lsp-external-controller name;
    maximum-segment-list-depth maximum-segment-list-depth
    maximum-srv6-te-segment-list-depth maximum-srv6-segment-list-depth;
    preference preference;
    preserve-nexthop-hierarchy;
    retry-timer seconds;
    sbfd-frr;
    segment-list;
    source-routing-path name;
    sr-preference sr-preference;
    sr-preference-override sr-preference-override;
    telemetry;
    srv6;
    traceoptions;
    traffic-engineering (SR-TE import policy)
    tunnel-tracking;
}

Hierarchy Level

content_copy zoom_out_map
[edit logical-systems name protocols],
[edit protocols]

Description

Enable Source Packet Routing in Networking (SPRING) or segment routing for traffic engineering packets for protocols that support segment routing. For example, you can configure segment routing capability for a BGP address family to steer traffic according to network requirements.

To enable segment routing traffic engineering for a BGP family, configure segment-routing-te at the [edit protocols bgp family inet|inet6] and [edit protocols bgp group group-name neighbor neighborfamily inet|inet6] hierarchy levels. Also, configure sr-preference-override at the [edit protocols bgp family inet|inet6 source-packet-routing] hierarchy level. This allows BGP to support segment routing policies and to steer traffic based on the segment list.

Note:

sr-preference-override is not applicable for static SR-TE SRv6 LSPs.

A policy action color: color-mode:color-value is configured at the [edit policy-options community namemembers] hierarchy level to categorize segment routing traffic. The color value is attached to BGP communities when exporting prefixes from inet-unicast and inet6-unicast address families, which associates a BGP community with a segment routing policy path definition.

Options

inherit-label-nexthops

Inherit label next hops for first hop in all the segment lists.

When the inherit-label-nexthops is configured at the [edit protocols source-packet-routing] hierarchy, it is applied globally, and takes precedence over individual segment-list level configuration.

For dynamic non-colored static LSPs, that is the PCEP-driven segment routing LSPs, the inherit-label-nexthops statement must be enabled globally, as the segment-level configuration is not applied.

lsp-external-controller name

Specify an external path computing entity, typically the network controller.

maximum-segment-list-depth

Specify a maximum segment list depth for segment routing traffic engineering policies.

  • Default: The default value is 5.

  • Range: 1 through 16.

maximum-srv6-segment-list-depth

Specify a maximum srv6 segment list depth for segment routing traffic engineering policies.

  • Default: For reduced SRH, the default value is 6.

  • Range: 1 through 6.

  • Default: For non-reduced SRH, the default value is 5.

  • Range: 1 through 5.

Note:

When no-reduced-srh is configured under the [edit routing-options source-packet-routing srv6] hierarchy level, ensure that the segment-list has a maximum of 5 SIDs, else configure maximum-srv6-segment-list-depth to have a commit constraint.

preference

Route preference for segment routing traffic engineering routes.

retry-timer

Number of seconds to wait before trying to reconnect to the auto-translate service if the previous attempt failed. Connections may fail if there is no link, or node, for a given IP address, or if the link or node does not have a SID.

  • Default: 30 seconds

  • Range: 1 through 600

sbfd-frr

Enable seamless BFD (S-BFD) fast re-route (FRR), a feature designed to enhance the resilience of SR-TE tunnels by monitoring end-to-end paths and initiating local repair mechanisms when failures are detected, rerouting traffic to alternate paths to minimize disruption.

sr-preference

Specify a preference for static segment routing policies. BGP chooses a segment routing policy with a higher value over policies with lower values.

  • Range: 0 through 4,294,967,295

sr-preference-override

Specify a preference override for static segment routing policies that BGP uses to select a segment routing policy. BGP chooses a policy with a higher value over policies with lower values.

  • Default: The default value is 100

  • Range: 0 through4,294,967,295

traffic-engineering

Enable import of all Spring-TE policies into TED

tunnel-tracking

When the tunnel-tracking option is enabled, it does a first-hop validation for SR-TE tunnels according to their route resolution. Status of each path will also be displayed when this option is enabled.

srv6 Specify SRv6 support for SR-TE policies. Enable the srv6 option to enable the SRv6 data plane support for statically configured SR-TE policies.
preserve-nexthop-hierarchy Specify preserve nexthop hierarchy support for SR-TE routes.

The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 17.4R1 for the MX Series and PTX Series with FPC-PTX-P1-A.

telemetry option introduced in Junos OS Release 18.3R1 for the MX Series and PTX Series with FPC-PTX-P1-A.

inherit-label-nexthops and retry-timer statements introduced in Junos OS Release 19.1R1 on MX Series routers.

tunnel-tracking option introduced in Junos OS Release 21.2R1.

srv6 option introduced in Junos OS Release 21.3R1.

footer-navigation