Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Routing Protocols

  • Enhancements to RFC 7775 performance (MX Series) - RFC 7775 compliance can be achieved with a single CLI command: set protocols isis rfc7775-compliance. This command can be used for both single instance and multi-instance configurations. When this command is enabled, the following configurations are started automatically:

    • IS-IS protocol begins originating the "IPv4/IPv6 Extended Reachability Attribute Flags" sub-TLV for applicable TLVs 135, 235, 236, and 237.

    • LSP size is increased by 3 bytes for each of the prefixes containing the attribute sub-TLV.

    • Any Layer 2 LSP with the Down bit set is ignored and treated as if it is not set while route preference calculations are made.

    • Route preference is determined by the rules defined in RFC 7775 for best prefix selection.

    • Up/Down bit and Prefix Attribute flag values are in compliance with the definitions in RFC 7775.

    [See Supported Standards for IS-IS and rfc7775-compliance.]

  • Supports a set of BGP self-diagnostics CLI commands (EX Series, MX Series, and SRX Series)–A set of BGP self-diagnostics CLI commands are now available that help users to streamline the root cause of common BGP issues automatically. This includes troubleshooting commands for BGP global state overview, BGP running state warnings, BGP neighbor down and flap diagnostics, BGP CPU hogging diagnostics, BGP missing route diagnostics, and BGP dropped route diagnostics. These set of commands are available for show bgp diagnostics command.

    [See show-bgp-diagnostics.]

  • Minimum ECMP (MX960)—We support conditional advertising and withdrawal of BGP routes based on certain constraints such as bandwidth and minimum available next-hop ECMP. When a BGP receiver learns the same route from multiple BGP peers, BGP updates the active BGP path and the routing information base (RIB), also known as the routing table. The BGP export policy determines whether to advertise the BGP route to these next hops based on the number of ECMP BGP peers it receives the prefix from. A BGP route that has multiple ECMP BGP peers creates better resiliency in case of link failures. You can configure a BGP export policy to withdraw a BGP route unless it receives the BGP route prefix from a minimum number of ECMP BGP peers.

  • Enhanced Routing Policies and Multi-Instance IS-IS Support (MX204, MX240, MX304, MX480, MX960, MX10004, MX10008,and MX10016)—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.