Routing Protocols

SSH host-key algorithm configuration enhancements (MX960)—Starting in Junos OS Release 22.3R1, we've replaced the system services ssh hostkey-algorithm configuration statement with the system services ssh hostkey-algorithm-list statement. When you use the hosykey-algorithm-list statement, Junos OS uses only the specified host-key algorithms and automatically disables the rest of the algorithms.

If you do not specify any host-key algorithms, Junos OS uses the default algorithms RSA, ECDSA, and ED25519.

[See hostkey-algorithm-list.]

Fast lookup of origin and neighbor ASs (MX480, MX960, MX10008, PTX1000, PTX10002, PTX10008, PTX10016, QFX10008, and vRR)—Starting in Junos OS Release 22.3R1, you can use the new asregex-optimize configuration statement at the [edit policy-options defaults] hierarchy level to perform a fast lookup of origin and neighbor autonomous systems (ASs). This optimization supports very large AS-Path regular expressions (typically as-path-group configuration) when the objective is to match neighboring ASes, or origin ASes.

[See Improve the Performance of AS Path Lookup in BGP Policy.]

IS-IS flood optimization (MX960, MX2008, MX2010, MX2020, PTX10002, PTX10008, and PTX10016)—Starting in Junos OS Release 22.3R1, you can rate-limit the IS-IS link-state PDUs that are retransmitted on parallel interfaces toward the same peer. This feature optimization prevents frequent drops in IS-IS hello protocol data units (PDUs) and subsequent adjacency reset. The optimizations also involve changes to the LSP transmission queues to avoid longer delays for frequently updated LSPs.

Sharding support for condition route manager (MX204 and MX480)—Starting in Junos OS Release 22.3R1, we have added sharding support for the condition manager to fetch active route information from the main thread for conditions. The condition manager on a shard interacts with the route target Proxy client to get active route information, and the condition manager on the main thread interacts with the route target proxy server to send details to the shards. The condition manager on each shard stores active route information that is true or false for any condition and evaluates the policy (having condition) based on that information. The condition manager on the main thread continues to perform route lookup, flash mechanism operations, and the dependent route operations, such as addition or deletion, according to the existing process.

We've updated the following command outputs:

• show policy condition

• show policy condition detail

• show policy condition condition-name

• show policy condition condition-name detail

• show policy condition rib-sharding shard-name

• show policy condition detail rib-sharding shard-name

• show policy condition condition-name rib-sharding shard-name

• show policy condition condition-name detail rib-sharding shard-name

[See Routing Policy Match Conditions, rib-sharding, and show policy conditions.]

Strip and replace BGP private-AS path (ACX710, JRR200, MX480, PTX10001, QFX5220, and QFX10003)—In Junos OS Release 22.3R1, we have introduced the strip-as-path policy option that removes the incoming autonomous system (AS) path as part of the import policy for a BGP session and replaces the received autonomous system (AS) path with the receiving router's local AS number for the receiving session. Note that the local AS number may be different from the number configured under autonomous system in the [edit routing-options] hierarchy.

If you need to normalize externally injected routes, you can use this policy option for the incoming autonomous system (AS) path so that it may be used similarly to routes that originate solely within the fabric. The new strip-as-path policy option has no impact on the BGP export policy.

You can configure the strip-as-path option under policy-options then clause:

set policy-options policy-statement do-strip term a then strip-as-path

[See Autonomous Systems for BGP Sessions.]