Errata and Changes in Documentation for JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms

Changes to the JUNOS Documentation Set

The following changes have been introduced to the JUNOS documentation set:

Technical documentation will no longer be available in iSilo/Palm OS and Windows eBook formats. Documentation will still be available in HTML, TAR/ZIP, and PDF formats.
There is a new book, the SDK Applications Configuration Guide and Command Reference.
For JUNOS Release 9.5 only, documentation on the DVD-ROM will be available in PDF form only.
JUNOS Release 9.5 supports a new index page that consolidates subscriber management information (http://www.juniper.net/techpubs/en_US/junos9.5/
information-products/pathway-pages/subscriber-access/index.html). This index page provides top-level access to the Broadband Subscriber Management Solutions Guide and topic categories that describe how to configure clients and services in a subscriber access network. The index page contains pathway page links categorized as follows:
- Access Technologies
  - DHCP (Local and Relay)
  - Mobile IP Home Agent
  - Point-to-Point Protocol (PPP)
- AAA Technologies
  - Authentication, authorization, and accounting (AAA)
  - Address Assignment Pools
- Protocols
  - Access Node Control Protocol (ANCP)
  - Internet Group Management Protocol (IGMP)
- Subscriber Management and Services
  - Dynamic Profiles
  - Class of Service (CoS)
  - Subscriber Secure Policy

Errata

This section lists outstanding issues with the documentation.

Class of Service

In JUNOS Release 8.0 and later, contrary to what is implied in the text, memory allocation dynamic (MAD) support is dependent on the FPC and PFE, not the PIC. All M320 router, MX-series router , and T-series router FPCs and PFEs support MAD, except for the T-series router ES-FPC and Enhanced IV FPC. No IQ, IQ2, IQ2E, or IQE PICs support MAD. [Class of Service]

The Class of Service Configuration Guidefor JUNOS Release 9.3 and 9.4 states that “If you configure more forwarding classes than the supported platform maximum, an error message is displayed.” This is not correct. You cannot configure more forwarding classes than supported in these releases. [Class of Service]

Configuration and Diagnostic Automation

In the Introduction to Writing Event Scripts chapter of the JUNOS 9.5 Configuration and Diagnostic Automation Guide the section "Using RPCs and Operational Mode Commands" erroneously states that RPCs can be invoked from event scripts. This feature is not supported in JUNOS Release 9.5.
In the Introduction to Writing Operation Scripts chapter and Introduction to Writing Event Scripts chapter of the JUNOS 9.5 Configuration and Diagnostic Automation Guide the section "Importing the junos.xsl File" includes the jcs:getsecret() extension function. This function is accessible only after JUNOS Release 9.5R1; it is not accessible in JUNOS Release 9.5R1 or earlier JUNOS releases.
[Configuration and Diagnostic Automation]

Network Interfaces

In the Network Interfaces Configuration Guide, Chapter 44 Configuring IEEE 802.1ag OAM Connectivity-Fault Management section Configuring a CFM Interface Down Action Profile Action states the following:

“Note: The action profile is supported only on the physical interface level, and not on the logical interface.”
This is incorrect, and was revised in the JUNOS Software 9.6R1 release of the same document. The note was replaced with the following text:
“The action profile is supported on the physical interface level and the logical interface.”
[Network Interfaces]
Configuring Protocol Family and Interface Address Properties chapter of the Network Interfaces Configuration Guide sections “Configuring an Unnumbered Interface” and “Restrictions for Configuring Unnumbered Ethernet Interfaces” erroneously states that you cannot configure unnumbered Ethernet interfaces on the TX Matrix platform. This restriction was removed starting in JUNOS 9.5 and unnumbered Ethernet interfaces are now supported on the TX Matrix platform. [Network Interfaces]
The "Configuring an Unnumbered Interface" section in the JUNOS 9.5 Network Interfaces Configuration Guide in Chapter 5: Configuring Protocol Family and Interface Address Properties, erroneously included the following restriction on configuring unnumbered Ethernet interfaces:
- The configuration of unnumbered Ethernet interfaces is not supported when graceful Routing Engine switchover (GRES) is enabled on the router.
Beginning with JUNOS Release 9.4, the configuration of unnumbered Ethernet interfaces is supported when GRES is enabled on the router.
Network Interfaces Configuration Guide in Chapter 5: Configuring Protocol Family and Interface Address Properties, the section "Enabling Source Class and Destination Class Usage" contains the following incorrect statement that can be ignored: "On T-series, M120, and M320 platforms, the destination-class and source-class statements are not supported at the [edit firewall family family-name filter filter-name term term-name from] hierarchy level. On other M-series platforms, these statements are supported.”

Routing Policy and Firewall Filters

The output of the show pim statistics command has been enhanced to show the number of join and prune messages that have been dropped. The information is displayed in the following format: “Rx Join/Prune messages dropped 0” [Routing Protocols and Policies Command Reference]
In a routing policy, only standard and extended match conditions are evaluated according to a logical AND operation. Matching in prefix lists and route filters are handled differently. They are evaluated according to a logical OR operation. If you configure a policy that includes some combination of route filters, prefix lists, and source address filters, they are evaluated according to a logical OR operation or a longest-route match lookup. [Policy]
Active flow monitoring using version 9 supports sampling of both IPv4 and MPLS traffic simultaneously. You configure traffic sampling for IPv4 and MPLS traffic using the family (inet | mpls) statement at the [edit forwarding-options sampling input]hierarchy level. For additional information about configuring active flow monitoring , see the JUNOS Services Interfaces Configuration Guide and the JUNOS Feature Guide. [Policy]
The Routing Protocols Configuration Guide and the VPNs Configuration Guide both erroneously state that it is not possible to configure route reflectors and cluster IDs for the same routing instance. This type of configuration is now possible. [Protocols, VPNs]

Subscriber Access

The "DHCP State Persistence" and "Graceful Routing Engine Switchover" sections in the JUNOS 9.5 Subscriber Access Configuration Guide and the JUNOS 9.5 Policy Framework Configuration Guide contain erroneous information. The correct description, which applies to both the extended DHCP relay agent and the extended DHCP local server, is as follows:
The extended DHCP local server and the DHCP relay agent applications both maintain the state of active DHCP client leases in the session database. The extended DHCP application can recover this state if the DHCP process fails or is manually restarted, thus preventing the loss of active DHCP clients in either of these circumstances. However, the state of active DHCP client leases is lost if a power failure occurs or if the kernel stops operating (for example, when the router is reloaded) on a single Routing Engine.
The extended DHCP local server and the DHCP relay agent support graceful Routing Engine switchover on all routing platforms that contain dual Routing Engines. To support graceful Routing Engine switchover, the extended DHCP application automatically mirrors (replicates) information about the state of bound DHCP clients from the master Routing Engine to the backup Routing Engine.
To enable graceful Routing Engine switchover support for the extended DHCP local server or DHCP relay agent, include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level. You cannot disable graceful Routing Engine switchover support for the extended DHCP application when the router is configured to support graceful Routing Engine switchover.
For more information about using graceful Routing Engine switchover, see the JUNOS High Availability Configuration Guide.

Subscriber 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 configuring an IGMP interface 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 configuring 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
You can configure dynamic 802.1Q VLANs on Gigabit Ethernet (GE) and 10-Gigabit Ethernet (XE) interfaces only. Configuration on Aggregated Ethernet (AE) interfaces is currently not supported. For additional information about configuring dynamic VLANs, see the JUNOS Subscriber Access Configuration Guide.

VPNS

You can specify both Layer 3 and Layer 4 fields to be included while load-balancing Layer 2 traffic. This can be accomplished by including the layer-3 or the layer-4 statement at the [edit forwarding-options hash-key family multiservice payload ip] hierarchy level. The 9.5 JUNOS VPNs Configuration Guide does not include this information. For more information, see the JUNOS MX Series Ethernet Services Routers Layer 2 Configuration Guide.

User Interface and Configuration

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