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

  • Application-specific link attribute support in OSPFv2 for segment routing–traffic engineering (SR-TE) (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, and ACX7348)—Advertise traffic engineering (TE) attributes such as TE-metric, delay-metric, or admin-groups for RSVP and flexible algorithms on the same link using the application-specific link attribute as defined in RFC 8920, OSPF Application-Specific Link Attributes. Optimize network paths based on specific application requirementsto enhance traffic management and efficiency.

    Configure the flexible algorithm application-specific traffic engineering attribute by including the application-specific statement at the [edit protocols ospf area interface] hierarchy level and the strict-asla-based-flex-algorithm statement at the [edit protocols ospf source-packet-routing] hierarchy level.

    [See Understanding OSPF Flexible Algorithm for Segment Routing.]

  • Multi-instance OSPF with SR (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—Configure and run multiple independent interior gateway protocol (IGP) instances of OSPFv2 with segment routing (SR) on a router. Use this feature to create two or more OSPF instances and apply SR-MPLS on each instance. Multiple instances of OSPF can advertise different prefix-segment IDs (SIDs), and other instances can use these SIDs for routing decisions.

    Multi-instance OSPF combined with SR enhances network flexibility, scalability, and control over traffic engineering, especially in large and complex networks.

    Note:

    Junos OS does not support the configuration of the same logical interface in multiple IGP instances of OSPFv2.

    [See Multiple Independent IGP Instances of OSPFv2 Overview and Example: Configure Multiple Independent Instances of OSPFv2 with Segment Routing.]

  • NSR Support for SRv6 IS-IS and SRv6 BGP (ACX7332, ACX7348, and ACX7509)—Use IS-IS Nonstop Active Routing (NSR) for dynamic micro adjacency segment identifiers (SIDs) and dynamic classic adjacency End-x SIDs. Junos OS allocates the same dynamic SID on both the active and backup RE after a switch-over, ensuring that dynamically-allocated SIDs on the primaryRE are not repurposed. You can also use BGP NSR for dynamic DT SIDs. Note that Junos OS currently does not support NSR for classic dynamic End SIDs.

    [See How to Enable SRv6 Network Programming in IS-IS Networks.]