Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Improved handling of Packet Forwarding Engine install errors (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016)

    We have extended the mechanism whereby the forwarding plane can inform the control plane of any errors in next hops. ​If a route error is received from the Packet Forwarding Engine, the route error is directly added to the route-error list. For next-hop errors, the error is propagated to the parent route and the parent route is added to the route-error list. Once the route pointing to the next hop with an error is determined, the protocols can then take corrective action. To enable this error checking, configure the pfe-install-error statement at the [edit routing-options forwarding-table]​ hierarchy level, then restart the rpd process. Two commands are available to check on these route errors after you have configured this feature:

  • Enhanced Routing Policies and Multi-Instance IS-IS Support (ACX-Series, QFX-series, and PTX-Series)—We’ve introduced enhancements to simplify routing policies and improve IS-IS multi-instance support. You can now tag local and direct routes with tag and tag2 values, match multiple tag2s in a single policy term, and set IS-IS Down bits during inter-instance route redistribution for precise control. Policy configurations support regex for dynamic matching of multiple IS-IS instances, while wildcard patterns streamline operational commands. Additionally, administrators can reuse the same Micro SID Locator and Node-SID across IS-IS instances, enhancing SRv6 scalability. These updates reduce complexity, improve flexibility, and provide greater control for efficient network management.