Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 69

Errata and Changes in Documentation for Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
Copyright © 2010, Juniper Networks, Inc.
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
access dynamic profile. The following example provides the appropriate use of the
variable:
$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 follows:
$junos-igmp-version
$junos-igmp-version —IGMP version configured in a client access profile. The Junos OS
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
level for the statement.
interface
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
The Subscriber Access Configuration Guide and the System Basics Configuration Guide
contain information about the
does not appear in the CLI and is not supported.
[Subscriber Access, System Basics]
When you modify dynamic CoS parameters with a RADIUS change of authorization
(CoA) message, the Junos OS accepts invalid configurations. For example, if you specify
that a transmit rate that exceeds the allowed 100 percent, the system does not reject
the configuration and returns unexpected shaping behavior.
[Subscriber Access]
We do not support multicast RIF mapping and ANCP when configured simultaneously
on the same logical interface. For example, we do not support when a multicast VLAN
and ANCP are configured on the same logical interface, and the subscriber VLANs are
the same for both ANCP and multicast.
[Subscriber Access]
The Guidelines for Configuring Dynamic CoS for Subscriber Access topic in the Subscriber
Access Configuration Guide erroneously states that dynamic CoS is supported for
dynamic VLANs on the Trio MPC/MIC family of products. In the current release, dynamic
CoS is supported only on static VLANs on Trio MPC/MIC interfaces.
variable when a IGMP interface is configured in the client
[dynamic-profiles profile-name protocols igmp]
override-nas-information
hierarchy
statement. This statement
69