Errata and Changes in Documentation for Junos OS Software Release 10.3 for M Series, MX Series, and T Series Routers

Changes to the Junos Documentation Set

The Junos Software Class of Service Configuration Guide, the Junos Software Services Interfaces Configuration Guide, and the Junos Software Network Interfaces Configuration Guide are now available as subject-based Web pages. Also updated are the subject pages for the MX Series Ethernet Services Routers Solutions Guide.

You can still access full-book PDFs of this documentation on the right hand side of the relevant Web pages.

You can locate the links to the new Web pages for the guides at:

Junos Software Class of Service Configuration Guide http://www.juniper.net/techpubs/en_US/junos10.3/information-products/pathway-pages/cos/index.html
Junos Software Services Interfaces Configuration Guide http://www.juniper.net/techpubs/en_US/junos10.3/information-products/pathway-pages/services-interfaces/index.html
Junos Software Network Interfaces Configuration Guide http://www.juniper.net/techpubs/en_US/junos10.3/information-products/pathway-pages/config-guide-network-interfaces/index.html

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

In the Network Interfaces Configuration Guide, Chapter 61, Configuring SONET/SDH Interfaces, included a subsection titled Configuring APS Using a Container Interface with ATM Encapsulation. This information was mistakenly included and should not have been published until Junos OS Release 10.4.
[Network Interfaces]
The Configuring Layer 2 Circuit Transport Mode chapter in the Network Interfaces Configuration Guide states the following:
- For Layer 2 circuit cell relay and Layer 2 trunk modes, include the atm-l2circuit-mode cell statement at the [edit chassis fpc slot pic slot] hierarchy level and the encapsulation atm-ccc-cell-relay statement at the [edit interfaces interface-name] hierarchy level.
The configuration above is correct and will interoperate with routers running all versions of Junos software.
However, the chapter does not mention that you can also include the encapsulation atm-ccc-cell-relay statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. When you use the above configuration, keep the following points in mind:
- This configuration will only interoperate between Juniper routers running Junos OS Release 8.2 or lower.
- This configuration will NOT interoperate with other network equipment, including a Juniper router running Junos OS Release 8.3 or higher.
- For a Juniper router running Junos OS Release 8.3 or higher to interoperate with another Juniper router running Junos OS Release 8.2 or lower, on the router running Junos OS Release 8.3 or higher, include the use-null-cw statement at the [edit interfaces interface-name atm-options] hierarchy level.
- The use-null-cw statement inserts (for sending traffic) or strips (for receiving traffic) an extra null control word from the ATM cell.
- The use-null-cw statement is not supported on a router running Junos OS Release 8.2 or lower.
[Network Interfaces]
For Ethernet shared interfaces on the JCS 1200 Platform, gratuitous-arp configuration statements are supported on the Root System Domain (RSD), but not the Protected System Domain (PSD). These statements are configured at the [edit interfaces ge-x/y/x] hierarchy level. These statements include: gratuitous-arp-reply, no-gratuitous-arp-replay, and no-gratuitous-arp-request. Values you configure for gratuitous-arp statements on the RSD are not passed to the PSD. This is not communicated in the Junos Software 10.3 JCS 1200 documentation.
[JCS 1200]

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 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 [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 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.
[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]

User Interface and Configuration

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

VPNs

In Chapter 19 Configuring VPLS of the VPNs Configuration Guide, an incorrect statement that caused contradictory information about which platforms support LDP BGP interworking has been removed. The M7i router was also omitted from the list of supported platforms. The M7i router does support LDP BGP interworking.
[VPNs]