If RSVP LSPs are configured with bandwidth allocation, for ECMP next hops with
more than 16 LSPs, traffic is not distributed optimally based on bandwidths
configured. Some LSPs with smaller allocated bandwidths receive more traffic
than the ones configured with higher bandwidths. Traffic distribution does not
strictly comply with the configured bandwidth allocation. This caveat is applicable
to the following routers:
■ T1600 and T640 routers with Enhanced Scaling FPC1, Enhanced Scaling
FPC2, Enhanced Scaling FPC3, Enhanced Scaling FPC 4, and all Type 4 FPCs
■ M320 routers with Enhanced III FPC1, Enhanced III FPC2, and Enhanced III
FPC3
■ MX Series routers with all types of FPCs and DPCs, excluding MPCs
NOTE: This caveat is not applicable to MX Series routers with line cards based on
the Junos Trio chipset.
■ M120 routers with Type 1, Type 2, and Type 3 FPCs
■ M10i routers with Enhanced CFEB
[System Basics]
■
On M Series, MX Series, and T Series routing platforms, the targeted-broadcast
statement that is used to forward direct broadcast packets to the targeted subnet
in a network is available in the CLI , but it is not functional for the above three
platforms in JUNOS Release 9.5 through 10.1.
Subscriber Access Management
The Subscriber Access Configuration Guide contains the following dynamic variable
errors:
■ The Configuring a Dynamic Profile for Client Access topic erroneously uses the
$junos-underlying-interface variable when a IGMP interface is configured in the
client access dynamic profile. The following example provides the appropriate
use of the $junos-interface-name variable:
[edit dynamic-profiles access-profile]
user@host# set protocols igmp interface $junos-interface-name
■ Table 25 in the Dynamic Variables Overview topic neglects to define the
$junos-igmp-version predefined dynamic variable. This variable is defined as
follows:
$junos-igmp-version—IGMP version configured in a client access profile. The
JUNOS Software obtains this information from the RADIUS server when a
subscriber accesses the router. The version is applied to the accessing subscriber
when the profile is instantiated. You specify this variable at the [dynamic-profiles
profile-name protocols igmp] hierarchy level for the interface statement.
In addition, the Subscriber Access Configuration Guide erroneously specifies the
use of a colon (:) when you configure the dynamic profile to define the IGMP
Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers ■ 95
Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers
To Next Page
Loading...
Need help?
General
