Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Enhancements to show ospf spring and show ospf database commands (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—In Junos OS Evolved Release 23.2R1, we've enhanced the show ospf spring and show ospf database commands to display the following additional segment-routing information:

    • show ospf spring sid-database—Displays the segment identifier (SID) database with the prefix and index of native segment routing nodes.

    • show ospf spring prefix-sid-map—Displays segment routing mapping server (SRMS) advertisements.

    • show ospf database opaque-area ext-link link-addr <link-address>—Displays the specific extended-link link-state advertisements (LSAs) based on the link address.

    • show ospf database opaque-area ext-prefix prefix <prefix/len>—Displays the specific extended-prefix LSA based on the prefix.

    [See show ospf database, show-ospf-spring-sid-database, show-ospf-spring-prefix-sid-map].

  • Support for BGP-LS NLRI to carry confederation ID (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10008, and QFX5700)—Starting in Junos OS Evolved Release 23.2R1, Junos OS Evolved enables BGP Link State (BGP-LS) network layer reachability information (NLRI) to carry the confederation ID in TLV 512 when BGP confederation is enabled. The NLRI carries the confederation ID along with the member autonomous system number (AS number) in TLV 517 as defined in RFC 9086. In releases before Junos OS Evolved Release 23.2R1, BGP-LS NLRI carries only the member AS number in TLV 512 and the confederation ID is not encoded in the lsdist.0 routing table.

    [See Link-State Distribution Using BGP Overview.]

  • Support to activate BFD strict mode for BGP peer sessions (PTX10003, PTX10004, PTX10008, PTX10016, and QFX5700)—Starting in Junos OS Evolved Release 23.2R1, you can activate BFD strict mode for BGP peer sessions. Activating BFD strict mode disallows BGP to establish a session until the BFD session is successfully established and has stabilized. BFD strict mode helps avoid situations that result in routing churn. You can also use BFD strict mode to minimize the impact of a network interruption.

    To activate BFD strict mode for BGP peer sessions, include the strict-mode [bfd-wait-timeout <10-255 seconds> CLI statement under bfd-liveness-detection at the [edit protocols bgp group group-name neighbor address] hierarchy level.

    For example, use the following command to activate BFD strict mode for BGP peer sessions:

    set protocol bgp group group-name neighbor address bfd-liveness-detection [strict-mode [bfd-wait-timeout 10-255 seconds]]

    [See Understanding BFD for BGP, bfd-liveness-detection (BGP).]

  • BGP NSR keepalive prioritization (PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, we support replication of hold-timers for a BGP session configured with a very low (3 seconds or less) hold timer. We've introduced mechanisms to mitigate the tear-down of BGP sessions for the negotiated hold-down time interval. These mitigation mechanisms ensure that the nonstop active routing (NSR)-enabled BGP Transmission Control Protocol (TCP) sessions with BGP neighbors are not timed out at the BGP neighbors due to the scale of BGP neighbors and high volume of BGP route advertisements.

    [See Nonstop Active Routing Conceptshold-time (Protocols BGP).]