Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010 Release Note page 87

Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers
NOTE: This caveat is
the Junos Trio chipset.
Subscriber Access Management
The Subscriber Access Configuration Guide contains the following dynamic variable
errors:
Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers
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
applicable to MX Series routers with line cards based on
not
M120 routers with Type 1, Type 2, and Type 3 FPCs
M10i routers with Enhanced CFEB
[System Basics]
The Configuring a Dynamic Profile for Client Access topic erroneously uses the
$junos-underlying-interface
client access dynamic profile. The following example provides the appropriate
use of the $junos-interface-name
[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
predefined dynamic variable. This variable is defined as
$junos-igmp-version
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
profile-name protocols igmp]
In addition, the Subscriber Access Configuration Guide erroneously specifies the
use of a colon (:) when you configure the dynamic profile to define the IGMP
version for client interfaces. The following example provides the appropriate
syntax for setting the IGMP interface to obtain the IGMP version from RADIUS:
[edit dynamic-profiles access-profile protocols igmp interface $junos-interface-name]
user@host# set version $junos-igmp-version
variable when a IGMP interface is configured in the
variable:
hierarchy level for the interface
[dynamic-profiles
statement.
87