Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 96

Hide thumbs Also See for JUNOS 10.1 - RELEASE NOTES REV 4:
Table of Contents

Advertisement

JUNOS 10.1 Software Release Notes
96
Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers
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
statement 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 Software 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.
[Subscriber Access]
The Subscriber Access Configuration Guide incorrectly describes the
statement as it is used for subscriber access management.
authentication-order
When configuring the
authentication-order
management, you must always specify the
management does not support the
authentication fails when you do not specify an authentication method.
[Subscriber Access]
In the JUNOS Subscriber Access Configuration Guide, Table 26, "RADIUS-Based
Mirroring Attributes" incorrectly indicates that RADIUS VSA 26-10,
Juniper-User-Permissions, is required for subscriber secure policy mirroring. In
fact, this VSA is not used.
[Subscriber Access]
override-nas-information
statement for subscriber access
method. Subscriber access
radius
password
keyword (the default), and
statement. This

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOS 10.1 - RELEASE NOTES REV 4 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Networks junos 10.1

Table of Contents