Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Routing Protocols

  • Distribution of segment routing–traffic engineering (SR-TE) policies and state in the TED by using BGP link-state (MX10004)—Starting in Junos OS 22.4R1 Release, you can export the traffic engineering policies that originate from the segment routing protocol to the traffic engineering database (TED)and in the BGP link-state. After the export, you can use the BGP link-state to collect the information about traffic engineering policies. External controllers can then perform actions such as path computation, reoptimization, and network visualization within and across domains.

    To import the Source Packet Routing in Networking (SPRING) policy information to the TED, we now have the spring-te-policy statement at the [edit protocols source-packet-routing] hierarchy level.

    [See Link-State Distribution Using BGP, source-routing-path, and show ted spring-te-policy.]

  • MD5 authentication key rotation with overlap for key transition for OSPF (MX204, MX480, MX10003, PTX1000, and QFX10002)—Starting in Junos OS Release 22.4R1, we support advertising OSPF MD5 authentication with multiple active keys to send packets with a maximum limit of two keys per interface. Having multiple keys active at any one time at the interface enables the smooth transition from one key to another for OSPF. You can delete old keys without any impact on the OSPF session.

    [See Understanding OSPFv2 Authentication authentication.]

    [See show (ospf | ospf3) interface.]

  • ICMP TTL expiry with source address (MX240, MX480, MX960, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 22.4R1, you can configure your device to use an IPv4 address as the source address for ICMP time-to-live (TTL) expiry error messages. This means you can configure the loopback address as the source address in response to ICMP error packets. Doing this is useful when you cannot use the device address for traceroute purposes because you have duplicate IPv4 addresses in your network.

    Specify the address using the ttl-expired-source-address source-address option at the [edit system icmp] hierarchy level. The source address must be an IPv4 address. This configuration applies only to ICMP TTL expiry messages. Other ICMP error reply messages continue to use the address of the ingress interface as the source address.

    [See icmp (System) and ICMP Features.]

  • OSPF FAPM and interarea support (ACX5448, MX204, MX240, MX480, MX960, MX10003, MX10008, MX2008, MX2010, MX2020, PTX1000, and QFX10002)—Starting with Junos OS Release 22.4R1, the Flexible Algorithm Prefix Metric (FAPM) is defined to allow an optimal end-to-end path for an inter-area prefix. The Area Border Router (ABR) must include the FAPM when advertising the prefix between areas that areas reachable in that given Flex-Algorithm. When a prefix is unreachable, the ABR must not include that prefix in the Flex-Algorithm when advertising between areas. The defined FAPM provides inter-area support.

    [See Understanding OSPF Flexible Algorithm for Segment Routing.]

    [See show ospf database, show route table, show ted database

  • Flex aIgo and FAPM leaking across IS-IS multi-instance (ACX5448, MX480, MX960, MX2010)—Starting in Junos OS Release 22.4R1, we've added support to readvertise flexible algorithm (flex algo) prefix-segment identifiers (SIDs) and Flexible Algorithm Prefix Metrics (FAPMs) across interior gateway protocol (IGP) instances. We have also added support to readvertise other protocol prefixes and assign flex algo prefix-SIDs via policy to those prefixes.

  • Support for bootstrapping route-validation database from a local file (cRPD, JRR200, MX204, PTX10008, and QFX10008)—Starting in Junos OS Release 22.4R1, we support the ability to read validation records from a local binary file and install into the specified named route-validation databases within RPD. This feature implements syntactic and semantic checks on the content of the file to ensure that it is a well-specified set of validation records. If the syntactic and semantic checks fail, the entire file is rejected as a source of validation records. Use the source-file statement at the [edit routing-options validation] hierarchy level to source route-validation records from a local file source. You can use the show validation source-file command to display the properties of a local validation source file.

    [See validation.]

  • Support for BGP RIB sharding and update threading features (MX304, MX10003, MX10004, MX10008, MX10016, PTX10008, and PTX10016)—Starting in Junos OS Release 22.4R1, you can use a new CLI option to override the sharding and update-threading configuration that might be present either through platform defaults or through explicit configuration. To override the configuration, use the no-rib-sharding and no-update-threading options at the [edit system processes routing bgp] hierarchy level.

    [See bgp.]

  • MVPN feature support with sharding (cRPD, JRR200, MX2020, PTX5000, and QFX10002)—Starting in Junos OS Release 22.4R1, we support the following features:

    • Multicast virtual private network (MVPN) inactive route query from the main thread to shards

    • Extranet and auto-export support with sharding

    • Interact functions with RT-proxy client and server

    • New data structure to store the inactive route data on the main thread

    • Asynchronous route processing on the main thread

    You can use show mvpn c-multicast to display the inactive route data stored on the main thread.

    [See rib-sharding and show mvpn c-multicast .]