Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers

Changes to the JUNOS Documentation Set

The title of the JUNOS Hierarchy and RFC Reference is now JUNOS Hierarchy and Standards Reference.

Documentation for the extended DHCP relay agent feature is no longer included in the Policy Framework Configuration Guide. For DHCP relay agent documentation, see the Subscriber Access Configuration Guide or the documentation for subscriber access management.

The new JUNOS Technical Documentation index page (http://www.juniper.net/techpubs/software/junos/index.html ) consolidates documentation for JUNOS Software features that are common to all platforms that run JUNOS Software. The new index page provides direct access to core JUNOS information and links to information for JUNOS features that run on particular platforms.

Errata

This section lists outstanding issues with the documentation.

High Availability

TX Matrix Plus routers and T1600 routers that are configured as part of a routing matrix do not currently support nonstop active routing. [High Availability]

Integrated Multi-Services Gateway (IMSG)

Chapter 15, Maintenance and Failover in the IMSG, describes the IMSG high availability feature. This feature is not supported in this release of the software.
[Multiplay Solutions]

Interfaces and Chassis

The Configuring ECMP Next Hops for RSVP and LDP LSPs for Load Balancing topic in the System Basics Configuration Guide does not mention the following caveat for configuring ECMP next hops for RSVP LSPs:
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]

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 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 override-nas-information statement. This 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 authentication-order statement as it is used for subscriber access management. When configuring the authentication-order statement for subscriber access management, you must always specify the radius method. Subscriber access management does not support the password keyword (the default), and 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]

User Interface and Configuration

The show system statistics bridge command displays system statistics on MX Series routers. [System Basics Command Reference]

VPNs

The mac-tlv-receive and mac-tlv-send statements were removed from Release 10.0 of the JUNOS Software and are no longer visible in the [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] and [edit routing-instances routing-instance-name protocols vpls] hierarchy levels. Although the mac-tlv-receive and mac-tlv-send statements are recognized in the current release, they will be removed in a future release. We recommend that you update your configurations and use the mac-flush statement described in the Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers section of the release notes.
[VPNs]