Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • BFD for VXLAN (MX2020)—Starting in Junos OS Release 23.1R1, we support BFD for VXLANs.

    [See Understanding BFD.]

  • IS-IS maximum LSP size (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, you can configure the maximum LSP size for IS-IS in the range 512 through 9192 bytes to support advertising a higher number of prefixes.

    [See max-lsp-size.]

  • Block route redistribution from a specific protocol into IS-IS (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, you can block the export policy from redistributing the routes from other non-desired 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).]

  • Prevent IS-IS from entering overload state on reaching prefix limit (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, you can prevent IS-IS from entering the overload state even after the prefixes reach the configured 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).]

  • Autorecovery from IS-IS overload state (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, you can configure IS-IS to automatically exit from an overload state. The configuration prevents IS-IS from flushing all the fragments on overload so that when the fragment space is available, IS-IS automatically exits from the overload state. You can configure the autorecovery using the set protocols isis dynamic-overload auto-recovery command.

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

  • Support for BGP-LS NLRI to carry confederation ID (ACX710, ACX5448, MX10003, QFX5120-48YM, QFX5200, and QFX5210, and vRR)—Starting in Junos OS Release 23.1R1, Junos OS 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 Release 23.1R1, 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 for Policy based ORR (MX Series)—The policy based ORR helps you to 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 choose to 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.]