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

Changes to the JUNOS Documentation Set

The new JUNOS MX-series Layer 2 Configuration Guide provides an overview of the Layer 2 functions of the MX-series routers, including configuring bridging domains, MAC address and VLAN learning and forwarding, and spanning-tree protocols. It also details the routing instance types used by Layer 2 applications. All of this material was formerly covered in the JUNOS Routing Protocols Configuration Guide.

Starting in JUNOS Release 9.5, 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.

Errata

This section lists outstanding issues with the documentation.

Class of Service

In JUNOS software Release 8.0 and later, contrary to what is implied in the JUNOS Class of Service Configuration Guide, Memory Allocation Dynamic (MAD) support is dependent on the FPC and PFE, not the PIC. All M320, MX-series, and T-series routing platform FPCs and PFEs support MAD, except for the T-series ES-FPC and Enhanced IV FPC. No IQ, IQ2, IQ2E or IQE PICs support MAD. [Class-of-Service]

Interfaces and Chassis

The version of the JUNOS Network Interfaces Configuration Guide accessible at the JUNOS documentation home page (http://www.juniper.net/techpubs/software/junos/) corrects some errors in the version included on the JUNOS 9.3 Documentation DVD. We recommend always accessing the online version to obtain the most current information. [Network Interfaces]

In the JUNOS 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 level. This is incorrect, and has been revised in the 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 level. [Network Interfaces]
In Network Interfaces, section "Configuring Aggregated SONET/SDH Interfaces", the examples of aggregated SONET/SDH configurations use the address 10.2.11.1/32 destination 10.2.11.3 statement at the edit interfaces as0 unit 0 family inet hierarchy level. The subsection "Configuring Filters or Sampling on Aggregated SONET/SDH Links" contains similar examples that use the address 10.2.11.1/32 destination 10.2.11.3 statement at the edit interfaces asX unit 0 family inet hierarchy level. These examples are contrary to best practice.
The examples should show the address 10.2.11.1/30 statement at the edit interfaces as0 unit 0 family inet hierarchy level and also in the the edit interfaces asX unit 0 family inet hierarchy level.
Network Interfaces
The JUNOS Network Interfaces Configuration Guide, Chapter "Configuring Physical Interface Properties", Section "Disabling a Physical Interface", and Chapter "Summary of Interface Configuration Statements", Statement "disable (interface)" erroneously omit the following information: When you use the "disable" statement at the "edit interfaces" hierarchy level, depending on the PIC type, the interface might or might not turn off the laser. Older PIC transceivers do not support turning off the laser, but newer Gigabit Ethernet PICs with SFP and XFP transceivers do support it and the laser will be turned off when the interface is disabled. You can also use the set form of the statement, as follows: set interfaces <interface> disable
WARNING: Do not stare into the laser beam or view it directly with optical instruments even if the interface has been disabled. Network Interfaces

Mulitcast Applications

In the JUNOS Multicast Configuration Guide, under the section titled, “Configuring PIM Join Load Balancing” the following has been updated: “When PIM join load balancing is enabled in a multicast VPN scenario with point-to-multipoint (P2MP) tunnels, the load balancing is achieved based on the join counts for the far-end provider edge (PE) routers, not for any intermediate P routers” to correctly state “ When PIM join load balancing is enabled in a draft-rosen Layer 3 VPN scenario, the load balancing is achieved based on the join counts for the far-end provider edge (PE) routers, not for any intermediate P routers. In addition, the following note has been added to this section to make the support clear: NOTE: PIM join load balancing is supported on Draft Rosen multicast VPNs (also referred to as Dual PIM Multicast VPNs). PIM join load balancing is not supported on multiprotocol BGP-based multicast VPNs (also referred to as next-generation Layer 3 VPN multicast). [Multicast]

Routing Policy and Firewall Filters

The per-flow statement at the [edit forwarding-options load-balance] hierarchy level is supported only on the M120, M320, and MX-series routers. In addition, you cannot configure a numerical value with the hash-seed statement at the [edit forwarding-options load-balance per-flow] hierarchy level. The JUNOS software automatically chooses a value when you configure the hash-seed statement at this hierarchy level. For the correct documentation on this feature, see the JUNOS 9.5 version of the JUNOS Policy Framework Configuration Guide. [Policy]

Subscriber Access Management

Some links in the HTML output for the JUNOS Subscriber Access Configuration Guide do not work correctly. If you encounter any broken links, the workaround is to locate the information by browsing the HTML expanded table of contents or the HTML index.
The description of the revert-interval statement in the JUNOS System Basics Configuration Guide and the JUNOS Subscriber Access Configuration Guide incorrectly indicates the default value as 3 seconds. The correct default value for the revert-interval statement is 600 seconds.
The HTML output of the JUNOS Subscriber Access Configuration Guide is missing three sections. Refer to the following sections in the PDF output of the JUNOS Subscriber Access Configuration Guide for the missing information:
- Chapter 27—Class of Service for Subscriber Access Overview, "CoS and Static IP Demux Interface Set Overview" on page 378 and "Subscriber Interfaces that Provide Initial CoS Parameters Dynamically Obtained from RADIUS Overview" on page 378
- Chapter 28—Configuring Class of Service for Subscriber Access, "Configuring a Subscriber Interface to Provide Initial CoS Parameters Dynamically Obtained from RADIUS" on page 394

System Logging

The destination-address field is no longer valid in the system log message text for the following tags: RPD_IGMP_JOIN, RPD_IGMP_LEAVE, RPD_MLD_JOIN, and RPD_MLD_LEAVE. In JUNOS Release 9.3 and later, the character string “(null)” appears in the field instead of an actual address, as in this example: “RPD_IGMP_JOIN: Listener ip-address sent a join to (null) for group multicast-address source * on interface interface-name at timestamp.” [System Log]
When an interface configured for IGMP or MLD goes down, an RPD_IGMP_LEAVE or RPD_MLD_LEAVE message is no longer generated for each group and host pairing that is associated with the interface. Instead, a single message is generated, such as the following: “RPD_IGMP_ALL_SUBSCRIBERS_DELETED: All IGMP subscribers on interface interface-name deleted at timestamp because the interface is down.”
The RPD_IGMP_LEAVE and RPD_MLD_LEAVE messages are still generated when a subscriber session ends or times out. [System Log]

User Interface and Configuration

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

Network Interfaces

The "Configuring an Unnumbered Interface" section in the JUNOS 9.4 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.
The JUNOS Network Interfaces Configuration Guide, Chapter Configuring Physical Interface Properties, Section Disabling a Physical Interface, and Chapter Summary of Interface Configuration Statements, Statement disable interface erroneously omit the following information:
When you use the disable statement at the edit interfaces hierarchy level, depending on the PIC type, the interface might or might not turn off the laser. Older PIC transceivers do not support turning off the laser, but newer Gigabit Ethernet PICs with SFP and XFP transceivers do support it and the laser will be turned off when the interface is disabled. You can also use the set form of the statement, as follows:
set interfaces interface disable
WARNING: Do not stare into the laser beam or view it directly with optical instruments even if the interface has been disabled.
In Network Interfaces, section Configuring Aggregated SONET/SDH Interfaces, the examples of aggregated SONET/SDH configurations use the address 10.2.11.1/32 destination 10.2.11.3 statement at the edit interfaces as0 unit 0 family inet hierarchy level. The subsection Configuring Filters or Sampling on Aggregated SONET/SDH Links contains similar examples that use the address 10.2.11.1/32 destination 10.2.11.3 statement at the edit interfaces asX unit 0 family inet hierarchy level. These examples are contrary to best practice.
The examples should show the address 10.2.11.1/30 statement at the edit interfaces as0 unit 0 family inet hierarchy level and also in the edit interfaces asX unit 0 family inet hierarchy level.
Network Interfaces

VPNs

When you issue a ping vpls instance command, a chassis MAC address is drawn from the ingress provider edge (PE) router's pool of MAC addresses and used to create the VPLS ping packet. The ping packet is then forwarded to the egress provider edge (PE) router. When the egress provider edge (PE) router receives the ping packet, it learns the MAC address from the VPLS ping packet. The MAC address is added to the egress provider edge (PE) router's MAC table. [System Basics Command Reference]
The ping vpls instance command is now supported on T1600 routing platforms. [System Basics and Services Reference, VPNs]
The LDP BGP VPLS interworking feature is currently supported only on MX-series and M320 routers. [VPNs]