Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Support for accepting BGP routes with accept-own community (MX480 and MX960)—Starting in Junos OS Release 21.4R1, MX480 and MX960 routers accept BGP routes with the accept-owncommunity, defined by RFC 7611, BGP ACCEPT_OWN Community Attribute.

    The feature enhances the interoperability of a Juniper router by enabling it to accept routes whose ORIGINATOR_ID or NEXT_HOP value matches that of the receiving BGP speaker. For example, when a provider edge (PE) device advertises routes with the route distinguisher of a source VRF, the route reflector attaches the accept-own community and re-advertises the routes back to the originator. The provider edge (PE) device can then import the routes into the other destination VRFs, excluding its own.

    [See BGP accept-own Community and accept-own.]

  • Higher DDoS bandwidth for Layer 2 and Layer 3 protocols (PTX1000, PTX10002, PTX10008, QFX10002, QFX10002-60C, QFX10008, and QFX10016)—Starting in Junos OS Release 21.4R1, we support higher distributed denial-of-service (DDoS) bandwidth for many Layer 2 and Layer 3 protocols.

    [See protocols (DDoS) (ACX Series, PTX Series, and QFX Series).]

  • Remote LFA support for LDP in IS-IS (QFX10000 line of switches) —Starting in Junos OS Release 21.4R1, you can configure a remote loop-free alternate (LFA) path to extend the backup provided by the LFA route in an IS-IS or OSPF network. This feature is especially useful for Layer 1 metro rings where the remote LFA is not directly connected to the point of local repair (PLR). You can reuse the existing LDP implementation for the MPLS tunnel setup for the protection of IS-IS and OSPF networks and subsequent LDP destinations. By doing this, you eliminate the need for RSVP-TE backup tunnels for backup coverage.

    [See Understanding Remote LFA over LDP Tunnels in IS-IS Networks and Remote LFA over LDP Tunnels in OSPF Networks Overview.

  • OSPF link delay measurement and advertising (ACX Series, MX Series, PTX Series, and QFX Series)—Starting in Junos OS Release 21.4R1, you can measure and advertise various performance metrics in IP networks with scalability through probe messages that are sent by Two-Way Active Measurement Protocol (TWAMP) Light. OSPF receives probe messages and the measured values from TWAMP Light. OSPF advertises these messages as TLVs in packets. You can use these metrics to make path-selection decisions based on the network performance.

    [See How to Enable Link Delay Measurement and Advertising in OSPF.]

  • Support for multiple update threads to service a peer group (MX Series, PTX Series, and QFX Series)—Starting in Junos OS Release 21.4R1, you can configure multiple update threads to service a peer group to improve the performance of BGP. You can use the group-split-size configuration statement at the [edit system processes routing bgp update-threading] hierarchy level and configure a threshold value (0 through 2000).

    [See update-threading.]

  • Enhanced support to handle S flag, D flag and A flags in IS-IS (MX Series and PTX Series)—Starting in Junos OS Release 21.4R1, you can set the S flag to allow the label binding type, length and values (TLV) to leak through the IS-IS level (Level 1 or Level 2). You can set the A flag to program the penultimate-hop popping (PHP). You can set the D flag to prevent the leaking of the label binding TLV from Level 2 back to Level 1. Use the no-binding configuration statement at the [edit protocols isis source-packet-routing no-binding-sid-leaking] hierarchy level to disable label binding TLV leaks.

    [See Handling of the IS-IS Binding SID 'S' Flag and RFC 7794 Prefix Attribute Flags.]

  • Support for ICMP extension (QFX5100)—Starting in Junos OS Release 21.4R1, we've implemented RFC 5837, Extending ICMP for Interface and Next-Hop Identification, for both numbered and unnumbered aggregated Ethernet interfaces. We can now append additional fields to the following ICMP (IPv4 and IPv6) messages:

    • ICMPv4 Time Exceeded

    • ICMPv4 Destination Unreachable

    • ICMPv6 Time Exceeded

    • ICMPv6 Destination Unreachable

    Use the set system allow-icmp4-extension command to enable ICMP extension.

    [See Configure ICMP Features.]

  • Support for FAD and FAPM on traffic engineering database and BGP-LS (ACX Series, MX Series, and PTX Series)—Starting in Junos OS Release 21.4R1, we support FlexAlgo Definition (FAD) and FlexAlgo Prefix Metric (FAPM) on the traffic engineering database and BGP Link State (BGP-LS). You can store FAD and FAPM entries in the traffic engineering database and BGP-LS. You can also store multiple prefix segment identifiers (SIDs) for a prefix in BGP-LS. You can import the FAD and FAPM entries from the traffic engineering database to BGP-LS and export the FAD entries from BGP-LS to the traffic engineering database.

    [See What is Flexible Algorithm Definition (FAD).]