Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • BGP multipath prioritization with configurable priority queues (MX304)—Use BGP multipath prioritization to prioritize critical routes in BGP multipath computations with queues of low, medium, and high priorities. This feature reduces multipath-calculation latency for operator-prioritized routes in overall route convergence during high load. Additionally, you can manage delayed forwarding information base (FIB) convergence that results from frequent routing changes.

    [See BGP Route Prioritization , multipath (Protocols BGP), and prioritization.]

  • BGP route leak prevention by using BGP roles and OTC attributes based on RFC 9234 (cRPD, MX204, MX240, MX301, MX304, MX480, MX960, MX10004, MX10008, MX2008, MX2010, and MX2020)—You can prevent route leaks in BGP routing by using BGP roles and OTC attributes as defined in RFC 9234. The feature ensures that routes from providers or peers are only propagated to customers, reducing misconfigurations and errors. The BGP speaker automatically sets the OTC based on its configured role, and then advertises a prefix based on the OTC presence in the BGP update message, making the configuration straightforward and minimizing manual intervention. With this feature, you can maintain intended routing policies and prevent network delays and denial-of-service (DoS) attacks.

  • Enhanced service route resolution for BGP multipath with list next hop (ACX5448, ACX5448-M, ACX5448-D, ACX710, MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)—This feature improves how service routes resolve over BGP multipath routes that use list-next hop structures. The resolver now tracks all contributing paths, not just the active one. When you configure service routes to rely on BGP multipath, RPD builds internal dependencies across each indirect next hop in the list. This ensures that your service route automatically re-resolves whenever any contributing path changes.

    Previously, inactive paths could change without triggering a re-resolution. To fix this issue, RPD now links multipath routes to their full set of contributing routes using a patricia tree structure. The resolver can now detect changes across the entire path set and update service routes as needed.

    You do not need to configure new CLI settings, but you must ensure that the BGP multipath list-nexthop command statement is enabled. You can use the updated show route resolution list-nh and show krt indirect-next-hop commands to inspect dependencies, contributing next hops, and the resulting forwarding decisions.

    This enhancement improves resolution accuracy, supports re-evaluation during inactive path changes, and strengthens overall routing consistency in hybrid internal BGP (iBGP) and external BGP (eBGP) environments.

    [See Understanding BGP Path Selection.]

  • IGP-Metric-Based AIGP Path Selection for Flex-Algo Topologies (MX Series)—You can now use IGP metrics for AIGP path selection in SR-MPLS networks with flex-algorithm topologies, ensuring consistent low-latency routing across domains with different metric types. You can enable IGP metric computation for a flex-algorithm topology using the compute-igp-metric statement and assign multiple colors to a flex-algorithm with the secondary-color statement, both configured under routing-options flex-algorithm <flex-algo-id>. For finer control over route resolution, import policies can be managed within resolution schemes by using import-policy-append to add policies or import-policy to replace existing ones, configured under routing-options resolution scheme <scheme-name>. Additionally, policy statements now support the actual-igp-cost metric expression keyword, which allows precise adjustment of IGP metrics during route selection and is configured within policy-options policy-statement <policy-name>.