Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Support for IS-IS flood-reflector interfaces (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.2R1, we support the IS-IS flood reflector that offers better scalability for a Level 2 topology. Flood reflectors enable the creation of topologies where Level 1 areas provide transit forwarding for Level 2 destinations within a Level 2 topology.

    You can configure a node to be either the reflector or the client. To enable the reflector, include the flood-reflector reflector cluster-id statement at the [edit protocols isis level level number]hierarchy level.

    To enable the flood reflector client, include the flood-reflector client statement at the [edit protocols isis level level number] hierarchy level.

    The flexible tunnel interfaces (FTIs) are designated as flood-reflector interfaces.

    • On a flood-reflector node:

      To enable the flood reflector on an FTI, include the flood-reflector statement at the [edit protocols isis interface interface name level level number hierarchy level.

    • On a flood-reflector client node:

      To enable the flood reflector on an FTI, include the flood-reflector cluster-id statement at the [edit protocols isis interface interface name level level number] hierarchy level.

    Note:

    You can configure the flood reflector on FTIs at Level 2 only.

    [See How to Configure Flood-Reflector Interfaces in IS-IS Networks.]

  • Migration to IS-IS flood reflector interfaces and RSVP Explicit Route Object (ERO) expansion (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.2R1, we support the migration of IS-IS flood reflector and RSVP-Traffic Engineering (TE) ERO in a CLOS fabric network. This feature allows the creation of IS-IS flood reflectors and RSVP TE label-switched paths (LSPs) with minimal traffic loss.

    [See How to Configure Flood-Reflector Interfaces in IS-IS Networks.]

  • Nonstop active routing (NSR) support with BGP RIP sharding and BGP UpdateIO features (PTX10008 and PTX10016)—Starting in Junos OS Evolved Release 22.2R1, we've enabled nonstop routing (NSR) for BGP RIP sharding and BGP UpdateIO features. With NSR enabled, the backup Routing Engine and backup routing protocol process (rpd) become the primary Routing Engine without negatively affecting the BGP peering sessions with the neighbors if the primary Routing Engine fails. The backup rpd processes the replicated BGP control-plane information and populates the route state in the same multithreaded manner as in the primary rpd.

    After you configure NSR, the show bgp neighbor and show bgp summary commands display the information about the specific shards in the backup Routing Engine. To display the replicated information for a specific shard in the show bgp replication command, use the rib-sharding shard-name option.

    See [show bgp neighbor, show bgp summary, show bgp replication, and BGP Overview.]

  • TCP authentication option (TCP-AO) for resource public key infrastructure (RPKI) validation sessions (ACX7100-32C, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5220)—Starting in Junos OS Evolved Release 22.2R1, you can use the TCP authentication option to authenticate RPKI validation sessions for securing the Internet's routing infrastructure, such as the BGP. Using RPKI, legitimate holders of Internet number resources can control the operation of Internet routing protocols to prevent route hijacking and other attacks.

    To enable a TCP authentication option chain to authenticate an RPKI validation session, use the configured authentication-algorithm ao and authentication-key-chain keychain at the [edit routing-options validation group group_name session address] and [edit routing-options validation group group_name] hierarchy level.

    [See TCP Authentication Option (TCP-AO)]

  • BGP extended route retention (PTX10001-36MR, PTX10003, PTX10008, PTX10016, QFX5130-32CD, and QFX5220)—Starting in Junos OS Evolved Release 22.2R1, we have enhanced the long-lived graceful restart (LLGR) capabilities for BGP Helper and introduced the new configuration statement extended-route-retention at [edit protocols bgp group neighbor graceful-restart long-lived] hierarchy level. When you enable this feature, extended-route-retention supports LLGR helper mode regardless of the BGP peer LLGR capabilities. We have also updated the output of the following existing operational commands:

    • show bgp neighbor
    • show route extensive

    [See graceful-restart-long-lived-edit-protocols-bgp.]

  • RPD Object Reference count Anomaly checker (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5220)— Starting in Junos OS Evolved Release 22.2R1, we introduce a generic reference count infrastructure that all the modules in the routing protocol process (rpd) can use. The module maintains lock and unlock statistics corresponding to each object type in use. Any application can call the refcount increment or decrement API when an object is referred or deferenced. The module also provides a mechanism to detect anomalies such as a leak or overflow in an object’s refcount.