Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • BGP triggered dynamic IP encapsulation (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016)—Starting in Junos OS Evolved Release 23.4R1, you can configure the new attributes for GRE and UDP tunnel types:

    • IPv4 and IPv6 payload support for UDP tunnels

    • GRE tunnels

    We’ve added the following configuration statements at the [edit routing-options tunnel-attributes] hierarchy level:

    • dynamic-tunnel-ttl statement to set the set the tunnel TTL value (the default value is 0)

    • dynamic-tunnel-payload-port-profile statement to set the global UDP port profile

    • dynamic-tunnel-forwarding-class-name statement to set the forwarding class name

    We’ve also added the gre configuration statement at the [edit routing-options dynamic-tunnels] hierarchy level to set the encapsulation as GRE.

  • Support for EIBGP multipath ECMP for defined prefixes (PTX Series)—Junos OS Evolved Release 23.4R1 supports EBGP and IBGP (EIBGP) multipath. In the existing BGP multipath, EBGP routes take priority over IBGP routes because both have different metrics. After you enable EIBGP multipath and there is equal load sharing between the EBGP and IBGP routes, Junos OS Evolved initiates ECMP using a blend of both EBGP and IBGP.

    Feature-specific policies specify prefixes that support EIBGP multipath. You can configure the policy to choose the prefixes based on any match condition.

    To enable EIBGP multipath, configure the allow-external-internal option at the [edit protocols bgp multipath] or [edit logical-systems logical-system-name protocols bgp multipath] hierarchy level.

    [See multipath (Protocols BGP). ]

  • Support for micro-SIDs in TI-LFA, microloop avoidance, flex algo, and IS-IS MT (ACX Series)—Starting in Junos OS Evolved Release 23.4R1, we extend the support of compressing SRv6 addresses into a single IPv6 address (micro-SID) in topology-independent loop-free alternate (TI-LFA), microloop avoidance, and Flexible Algorithm (flex algo) path computations. From this release onward, you can also configure algorithms for micro-segment identifiers (micro-SIDs) to facilitate the new extended feature. We also support IPv6 unicast topology (part of IS-IS MT) in TI-LFA, microloop avoidance, and flex algo computations.

    To enable flex algo to install the ingress routes in transport class routing information bases (RIBs), configure the use-transport-class statement at the [edit routing-options flex-algorithm id] hierarchy level.

    [See How to Enable SRv6 Network Programming in IS-IS Networks .]

  • Support for OSPFv2 HMAC SHA-1 keychain authentication and optimization for multi-active MD5 keys (ACX7024, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.4R1, you can enable OSPFv2 HMAC-SHA1 authentication with keychain to authenticate packets reaching or originating from an OSPF interface. This feature ensures a smooth transition from one key to another for OSPFv2 with enhanced security.

    You can enable OSPFv2 to send packets authenticated with only the latest MD5 key after all the neighbors switch to the latest configured key. In Junos OS Evolved releases earlier than Release 23.4R1, we support advertising authenticated OSPF packets always with multiple active MD5 keys with a maximum limit of two keys per interface.

    To enable OSPFv2 HMAC-SHA1 authentication, configure the authentication keychain <keychain name> option at the [edit protocols ospf area area-id interface interface_name hierarchy level. To enable optimization of multiple active MD5 keys, configure the delete-if-not-inuse option at the [edit protocols ospf area area-id interface interface_name authentication multi-active-md5] hierarchy level.

    [See Understanding OSPFv2 Authentication.]

  • Support for Next-Hop Dependent Capability Attribute (ACX7100-32C and PTX10001-36MR)—Starting in Junos OS Evolved Release 23.4R1, we use the Entropy Label Capability (ELCv3) attribute defined within the IETF Next-Hop Dependent Capability Attribute for load balancing. This attribute replaces the existing ELCv2 attribute. To operate the ELCv2 attribute along with ELCv3, explicitly configure the elc-v2-compatible statement at the labeled-unicast entropy-label hierarchy level.

    [See Understanding Entropy Label for BGP Labeled Unicast LSP.]

  • Support for EIBGP multipath (PTX Series)

    Starting in Junos OS Release 23.4R1, we support EIBGP multipath. To enable this feature, use the allow-external-internal prefix-policy policy-name statement under global BGP multipath configuration hierarchies.

    [See multipath (Protocols BGP).

  • Support for limiting the number of BGP sessions belonging to a subnet (ACX7100-32C and PTX10001-36MR)—Starting in Junos OS Evolved Release 23.4R1, we support limiting the number of BGP sessions belonging to a given subnet that is configured using the ‘allow statement. You can use this feature to configure wider subnets by limiting the number of BGP sessions over them. You can set this limit using the peer-limit value statement at the [edit protocols bgp group group-name dynamic-neighbor] hierarchy level.

    [See peer-limit.]

  • Deterministic ordering of qualified next-hops ( PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 23.4R1, a new CLI configuration option order is introduced to ensure that multiple paths in the static routes maintain the order and do not get re-ordered on RPD restart or RPD switchover. The order of the path is maintained even if one of the links goes down and comes back again.

    To configure deterministic ordering of static route next-hops, include the order number configuration statement at the [edit routing-options static route prefix qualified-next-hop nh-address] hierarchy level.

    [See qualified-next-hop (Static Routes).]