Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Enhanced support to handle S flag, D flag and A flags in IS-IS (PTX10001, PTX10001-36MR, PTX10003, PTX10004, and PTX10008)—Starting in Junos OS Evolved 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.]

  • Service to correlate FPCs with P2MP sub-LSPs (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 21.4R1, you can correlate FPCs with point-to-multipoint (P2MP) sub-LSPs. An FPC can act as an ingress, egress, or transit point for more than one sub-LSP of the same P2MP LSP. If an FPC fails, then all the sub-LSPs that it serves are affected.

    You can configure a service that enables you to monitor the correlation between FPCs and the P2MP sub-LSPs—branch paths—that are on an LSR. This information helps you evaluate the effect a failed FPC has on the correlated sub-LSPs. When you enable tracing, the service also provides system log messages (during an FPC outage) that provide detailed information about the sub-LSPs affected.

    [See Configuring a Service to Correlate Point-to-Multipoint sub-LSPs with FPCs.]

  • Support for FAD and FAPM on the traffic engineering database and BGP-LS (PTX10001-36MR, PTX10003, PTX10004, and PTX10008)—Starting in Junos OS Evolved Release 21.4R1, we support Flex ALgo Definition (FAD) and Flex Algo Prefix Metric (FAPM) on traffic engineering database and BGP-LS. You can store FADs and FAPMs into TED and BGP Link-State and store multiple prefix-sids for a prefix into BGP Link-State. 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).]

  • Support for ICMP extension (QFX5100)—Starting in Junos OS Evolved Release 21.4R1, for both numbered and unnumbered aggregated Ethernet interfaces, we’ve implemented RFC5837 to enable us to 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 IPv6 ping, IPv6 traceroute, and ECMP traceroute for Labeled-IS-IS segment routing paths (PTX10001-36MR, PTX10003, PTX10004, and PTX10008)—Starting in Release 21.4R1, Junos OS Evolved supports IPv6 ping, IPv6 traceroute, and ECMP traceroute for Labeled-IS-IS segment routing paths. 

    [See ping and traceroute mpls segment-routing isis.]

  • Support for link delay measurement and advertising in IS-IS (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 21.4R1, you can measure and advertise various performance metrics in IP networks with scalability, by using several IS-IS probe messages. These metrics can then be used to make path-selection decisions based on network performance.

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