Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

maximum-ecmp

 

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 10.1.

Description

(M10i routers with Enhanced CFEB, and M320, M120, MX Series, and T Series routers) Configure 16, 32, or 64 ECMP next hops for RSVP or LDP LSPs, or MPLS static LSPs that are configured using set protocols mpls static-label-switched-path.

This command is used to control the maximum number of ECMP legs in an NH. This command applies to all protocols, and the maximum configurable ECMP next hops are chassis dependent.

Note

MX Series routers with one or more Modular Port Concentrator (MPC) cards and with Junos OS 11.4 or earlier installed, support the configuration of the maximum-ecmp statement with only 16 next hops. You should not configure the maximum-ecmp statement with 32 or 64 next hops. When you commit the configuration with 32 or 64 next hops, the following warning message appears:

Error: Number of members in Unilist NH exceeds the maximum supported 16 on Trio.

Default

16

Options

next-hops—Specify the number of next hops (16, 32, or 64) for RSVP or LDP LSPs, or MPLS static LSPs.

The following types of routes support next hops with up to 64 ECMP gateways:

  • RSVP routes in inet tables where multiple RSVP LSPs are created to the same destination. In the case where LSP path protection or FRR is configured, the combination of active, backup and FRR next-hops is a maximum of 64.

  • LDP routes in inet.3 and mpls.0 where the associated IGP route contains 64 next-hop gateways.

  • ISIS, OSPF, iBGP, eBGP and Static routes in inet and inet6 tables.

Note

These routes also include routes in routing-instances (foo.inet.0).

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.