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

[ Contents] [ Prev] [ Next] [ Report an Error]

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

Changes to the JUNOS Documentation Set

Starting in JUNOS Software Release 9.6, the JUNOS Documentation DVD (DOC-CD-S) will no longer be orderable. The software is still available on the Juniper Networks website and you can download the complete documentation set for later offline viewing or burn your own DVD-ROM by accessing the documentation set at the following URL www.juniper.net/techpubs/resources/cdrom.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 [JUNOS High Availability Configuration Guide].

Interfaces and Chassis

The show chassis fabric plane command is not listed in the Index of Statements and Commands. To access the documentation for this command, see the Table of Contents or use this URL: https://www.juniper.net/techpubs/en_US/junos9.6/information-products/topic-collections/swcmdref-basics-services/show-chassis-fabric-plane.html.
[System Basics Command Reference]

The following corrections and additions have been made to the descriptions of the command options and output fields for the show chassis fabric plane command:

[Description]:
(TX Matrix Plus, T1600, M120, and MX Series routers only) On the M120 router, display the state of all fabric plane connections to the Forwarding Engine Boards (FEBs). On MX Series routers, display the state of all fabric plane connections to the Dense Port Concentrators (DPCs) and Packet Forwarding Engines (PFEs) on the Flexible PIC Concentrators (FPCs). On the TX Matrix Plus router and T1600 routers in a routing matrix, display the state of the fabric management plane and the logical planes on the switch-fabric chassis (SFC) and line-card chassis (LCC). This command can be used on the master Routing Engine only.
[Command options]:

detail — (TX Matrix Plus and T1600 routers in a routing matrix only) (Optional) Display detailed output for the fabric management plane. Shows Switch Interface Board (SIB) states for the TXP-F13 SIB and TXP-F2S SIB.extensive — (TX Matrix Plus and T1600 routers in a routing matrix only) (Optional) Display extensive output for the fabric management plane, including the state of the optical links between the F13 SIB on the TX Matrix Plus router and the TXP-T1600 SIB (ST-SIB-L) on the T1600 router.lcc number — (TX Matrix Plus router only) (Optional) T1600 router (LCC) that is connected to a TX Matrix Plus router. Replace number with a value from 0 through 3.sfc number — (TX Matrix Plus router only) (Optional) Show information about the TX Matrix Plus router (SFC). Replace number with 0.terse — (TX Matrix Plus router only) (Optional) Display terse output for the fabric management plane.

[Output field descriptions]:

Table 2 lists the output fields for the show chassis fabric plane command. Output fields are listed in the approximate order in which they appear.

Table 2: show chassis fabric plane Output Fields

Field Name	Field Description	Level of output
Plane	(TX Matrix Plus, MX Series, and M120 routers only) Number of the plane.	none
Plane state	(MX Series and M120 routers only) State of each plane: ACTIVE—SIB is operational and running. OFFLINE—SIB is powered down. FAULTY— SIB is in alarmed state where the SIB’s plane is not operational for the following reasons: On-board fabric ASIC is not operational. Fiber optic connector faults. FPC connector faults. SIB mid-plane connector faults.	none
FEB	(M120 routers only) FEB number and state of links to each FEB: Link error—Link between SIB and FPC is not operational. Links ok—Link between SIB and FPC is active. Unused—No FPC is present.	none
FPC	(MX Series routers only) Slot number of each Dense Port Concentrator (DPC) or Flexible PIC Concentrator (FPC). An FPC occupies two DPC slots on an MX Series router. The interface corresponds to the lowest numbered DPC slot for which the FPC is installed.	none
PFE	(MX Series and M120 routers only) Slot number of each Packet Forwarding Engine and the state of the links to the DCP: Links ok, Link error, or Unused. Each DPC includes four Packet Forwarding Engines. Links ok: Link between SIB and FPC is active. Link error: Link between SIB and FPC is not operational. Unused: No FPC is present.	none
State	(TX Matrix Plus and T1600 routers in a routing matrix only)—State of the fabric plane: Online: Fabric plane is operational and running and links on the SIB are operational. Spare: Fabric plane is redundant and can be operational if the operational fabric plane encounters an error. Check: Fabric plane is in alarmed state due to the following reason and the cause of the error must be resolved: One or more SIBs (belonging to the fabric plane) in the Online or Spare states has transitioned to the Check state. Check state of the SIB can be caused because of link errors or destination errors. Fault: Fabric plane is in alarmed state if one or more SIBs belonging to the plane are in the Fault state. A SIB can be in the Fault state because of the following reasons: On-board fabric ASIC is not operational. Fiber optic connector faults. FPC connector faults. SIB mid-plane connector faults. Link errors have exceeded the threshold.	none
Uptime	(TX Matrix Plus and T1600 routers in a routing matrix only)—Time the fabric plane has been up and running.	none
Fabric Management Plane State Output Fields for the show chassis fabric plane extensive command on a TX Matrix Plus router
PLANE number	State of the fabric plane: Online: Fabric plane is operational and running and links on the SIB are operational. Spare: Fabric plane is redundant and can be operational if the operational fabric plane encounters an error. Check: Fabric plane is in alarmed state due to the following reasons and the cause of the error must be resolved: One or more SIBs (belonging to the fabric plane) in the Online or Spare states has transitioned to the Check state. Check state of the SIB can be caused because of link errors or destination errors. Fault: Fabric plane is in alarmed state if one or more SIBs belonging to the plane are in the Fault state. A SIB can be in the Fault state because of the following reasons: On-board fabric ASIC is not operational. Fiber optic connector faults. FPC connector faults. SIB mid-plane connector faults. Link errors have exceeded the threshold.	extensive
SIB F13/F2S slot-number	State of the TXP-F13 SIB or TXP-F2S SIB: Activating—Transitional state when the SIB is transitioning to the Online or Spare state. Deactivating—Transitional state when the SIB is going offline. Online—SIB is operational and running. Offline—SIB is powered down. Spare—SIB is redundant and will move to active state if one of the working SIBs fail to pass traffic. Empty—No SIB is present. Fault— SIB is in alarmed state due to the following reasons and the cause of the error must be resolved: On-board fabric ASIC is not operational. Fiber optic connector faults. FPC connector faults. SIB mid-plane connector faults. Link errors have exceeded the threshold Check—SIB is in alarmed state where the SIB is partially operational due to link or destination errors. Only a SIB that is Online or Spare can transition to the Check state. Note: If a SIB is not inserted properly, the SIB cannot transition to the Online or Spare state, and therefore, cannot transition to the Check state.	extensive
SIB F13 slot-number Odd/Even	State of the TXP-F13 SIB Even and Odd port connection optical links from the TX Matrix Plus router (SFC) to the T1600 router (LCC) in the routing matrix . The left four ports on the SFC are labeled Even and provide connections to one even-numbered LCC—LCC0 or LCC2. The right four ports on the SFC are labeled Odd and provide connections to one odd-numbered LCC—LCC1 or LCC3.	extensive
LCC number, SIB slot-number	State of the SIB on the LCC that is connected to the Even or Odd port on the TXP-F13 SIB faceplate: Links ok—Links between the TXP-F13 SIB on the SFC and the LCC is active. Link error—Link between the TXP-F13 SIB on the SFC and the LCC is not operational. Unused—No SIB is present.	extensive
SG number Port number	State of the SG chip ports on the LCC: Links ok—Link is active. Link error—Link is not operational. Unused—Port is not in use.	extensive
SIB F2S slot-number	State of the intra-chassis links between the TXP-F2S and TXP-F13 SIB.	extensive
Fabric Management SIB State Output Fields for the show chassis fabric plane extensive command on a TX Matrix Plus router
SIB slot-number	State of the SIBs on the T1600 router (LCC) in the routing matrix: Activating—Transitional state when the SIB is coming online. Deactivating—Transitional state when the SIB is going offline. Connected—SIBS on an LCC are connected and trained, but are either not online or are spare, because the plane on the the TX Matrix Plus router (SFC) is still offline. The LCC SIB transitions to the Connected state when the F13 SIB to which it connects is online but the SFC plane (to which the LCC SIB connects) is offline for some reason. For instance, when there are insufficient number of F2 SIBs in the plane. Disconnected—If an F13 SIB on the TX Matrix Plus router (SFC) goes offline, then the SIBs on the LCCs connected to the F13 SIB get disconnected. The Disconnected state is valid only for SIBs on an LCC. An LCC SIB transitions to the Disconnected state when the F13 SIB to which it connects goes Offline, irrespective of the state of the SFC plane. Note: The Connected and Disconnected states are only applicable to the SIBs on an LCC. Online—SIB is operational and running. Offline—SIB is powered down. Spare—SIB is redundant and will move to active state if one of the working SIBs fail to pass traffic. Empty—No SIB is present. Fault— SIB is in alarmed state where the SIB’s plane is not operational for the following reasons: On-board fabric ASIC is not operational. Fiber optic connector faults. FPC connector faults. SIB mid-plane connector faults. Link errors have exceeded the threshold Check—SIB is in alarmed state where the SIB is partially operational due to link or destination errors. Only a SIB that is Online or Spare can transition to the Check state. Note: If a SIB is not inserted properly, the SIB cannot transition to the Online or Spare state, and therefore, cannot transition to the Check state.	extensive
LCC SIB Link State	State of the LCC SIB link: Links ok—Link is active. Link error—Link is not operational. Unused—SIB is not in use.	extensive
SG number Port number	State of the SG chip ports on the LCC: Links ok—Link is active. Link error—Link is not operational. Unused—Port is not in use.	extensive

[System Basics Command Reference]

Network Interfaces

The 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 routers, 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 routers, these statements are supported.”
The Network Interfaces Configuration Guide in Chapter 5: Configuring Protocol Family and Interface Address Properties, the section "Configuring ICCP for MC-LAG" describes functionality not supported for JUNOS Release 9.6 and earlier.
The PDF version of the Baseline Network Operations Guide in Chapter 16: Use the ping and traceroute Commands, the section “Check the Accessibility of Two Routers on the Edge” contains an incorrect figure. Figure 17 should show a router network, but instead shows T320 hardware. The correct figure can be located in the HTML version of the section: http://www.juniper.net/techpubs/en_US/junos9.6/information-products/topic-collections/nog-baseline/ping-traceroute-accessibility-checking.html#id-11574067.

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

User Interface and Configuration

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

VPNs

In Chapter 10 of the VPNs Configuration Guide in the section titled “Configuring BGP Between the PE and CE Routers”, it incorrectly states that route reflectors and cluster IDs are not supported on a routing instance. They are indeed supported, so it is possible to configure the cluster-id statement at the [edit routing-instances routing-instance-name protocols bgp group group-name] hierarchy level.