Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • IS-IS Maximum LSP Size (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 23.1R1, you can configure the maximum LSP size for IS-IS in the range 512 through 9192 bytes to support advertisement of a higher number of prefixes.

    [See max-lsp-size.]

  • Support for blocking the redistribution from a specific protocol into IS-IS (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 23.1R1, you can block the export policy from redistributing the routes from other protocols into IS-IS. You can block the redistribution using the set protocol isis no-external-export protocol statement at the [set protocols isis] hierarchy level.

    [See no-external-export (Protocols IS-IS).]

  • Support for preventing IS-IS from entering overload state on reaching prefix limit (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 23.1R1, you can prevent IS-IS from entering the overload state even after reaching the set prefix limit. You can configure the set protocols isis dynamic-overload no-overload-on-prefix-export-limit statement at the [set protocols isis] hierarchy level.

    [See no-overload-on-prefix-export-limit (Protocols IS-IS).]

  • Support for auto-recovery from IS-IS overload state (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 23.1R1, you can set up IS-IS to automatically exit an overload state. The command prevents IS-IS from flushing all the LSP fragments on overload so that when the fragment space is available, IS-IS automatically exits from the overload. You can configure the auto-recovery using the set protocols isis dynamic-overload auto-recovery statement at the [set protocols isis] hierarchy level.

    [See auto-recovery (Protocols IS-IS).]

  • Support for S-BFD over EPE SIDs (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.1R1, seamless BFD (S-BFD) running between ingress devices and autonomous system boundary routers (ASBRs) can also track BGP egress peer engineering (EPE) segment identifiers (SIDs). This action helps prevent null-route filtering if a BGP EPE SID goes down.

    [See sbfd.]

  • CLI support for BFD echo and echo-lite modes (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.1R1, you can configure BFD echo mode and echo-lite mode through the Junos OS Evolved CLI. When BFD echo mode is active, BFD echo packets are transmitted and looped back from a neighboring device to ensure that a forwarding path is available. BFD echo mode requires both the local device and neighbor device to support the full BFD protocol, but BFD echo-lite mode can function even if the neighbor device doesn't support BFD.

    You can use the following new CLI configuration statements to configure BFD echo mode and echo-lite mode:

    • Echo mode: set routing-options static route address bfd-liveness-detection echo minimum-interval interval

    • Echo-lite mode: set routing-options static route address bfd-liveness-detection echo-lite minimum-interval interval

    [See bfd-liveness-detection.]

  • Support for NDP proxy and DAD proxy for multiple interfaces (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.1R1, we support Neighbor Discovery Protocol (NDP) and Duplicate Address Detection (DAD) for interface-restricted mode and interface-unrestricted mode. You use existing CLI commands to enable and disable NDP proxy and DAD proxy for interface-restricted mode and interface-unrestricted mode. Note that you cannot configure interface-unrestricted and interface-restricted options on the same interface simultaneously.

    [See NDP Proxy and DAD Proxy, dad-proxy, and ndp-proxy.]

  • Support for policy-based ORR (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5700, and QFX5220)—Starting in Junos OS Evolved Release 23.1R1, the policy-based ORR helps you select the paths to advertise to achieve your traffic-engineering requirements. You can specify a subset of the paths as candidate paths for path selection. The existing path-selection algorithms select the best paths, and you can modify the attributes of the selected paths or reject the selected paths. The policy-based ORR can work alone or with IGP-based ORR and add-path.

    To enable this feature in BGP peer groups, configure export <policy> at the [protocols bgp group <name> optimal-route-reflection] hierarchy level.

    [See export (Protocols BGP), optimal-route-reflection, and show bgp group.]