■
RPD_RA_DYN_CFG_SES_ID_MISMATCH
■
RPD_RT_CFG_BR_CONFLICT
The following system log messages are no longer documented:
■
DFWD_CONFIG_FW_UNSUPPORTED
■
LLDPD_PARSE_ARGS
■
LLDPD_PARSE_BAD_SWITCH
■
LLDPD_PARSE_CMD_ARG
■
LLDPD_PARSE_CMD_EXTRA
■
LLDPD_PARSE_USAGE
■
LPDFD_DYN_SDB_OPEN_FAILED
User Interface and Configuration
■
Enhanced support for up to 64 ECMP next hops for load balancing on M10i
routers with Enhanced CFEB, M320, M120, MX Series, and T Series Core
routers
—The JUNOS Software supports configurations of 16, 32, or 64 equal-cost
multipath (ECMP) next hops for RSVP and LDP LSPs on M10i routers with an
Enhanced CFEB, and M320, M120, MX Series, and T Series routers. For networks
with high-volume traffic, this provides more flexibility to load-balance the traffic
over as many as 64 LSPs.
To configure the maximum limit for ECMP next hops, include the
maximum-ecmp
next-hops
statement at the
[edit chassis]
hierarchy level:
[edit chassis]
maximum-ecmp
next-hops
;
You can configure a maximum ECMP next-hop limit of
16
,
32
, or
64
using this
statement. The default limit is
16
.
The following types of routes support the ECMP maximum next-hop configuration
for as many as
64
ECMP gateways:
■
Static IPv4 and IPv6 routes with direct and indirect next-hop ECMPs
■
LDP ingress and transit routes learned through associated IGP routes
■
RSVP ECMP next hops created for LSPs
■
OSPF IPv4 and IPv6 route ECMPs
■
ISIS IPv4 and IPv6 route ECMPs
■
EBGP IPv4 and IPv6 route ECMPs
■
IBGP (resolving over IGP routes) IPv4 and IPv6 route ECMPs
38
■
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
