Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

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

    Changes to the JUNOS Documentation Set

    The JUNOS Layer 2 Configuration Guide provides an overview of the Layer 2 functions supported on Juniper Networks routers, including configuring bridge domains, MAC addresses and VLAN learning and forwarding, and spanning-tree protocols. It also details the routing instance types used by Layer 2 applications. This material was formerly covered in the JUNOS MX Series Ethernet Services Routers Layer 2 Configuration Guide.

    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 (https://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.

    Class of Service

    • In JUNOS Release 10.1 and 10.2, the topic Example: Configuring Large Delay Buffers for Slower Interfaces states “Assuming that the sched-best scheduler is assigned to a T1 interface…” This is an error. The topic should state “Assuming that the sched-exped scheduler is assigned to a T1 interface…”

      [Class of Service]

    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)

    • The topics Assigning a NAT Pool and Assigning a NAT Pool for the BGF contain a reference to the media-service configuration statement, which was deprecated in JUNOS Release 10.2R1.
      • Assigning a NAT Pool was replaced in Integrated Multi-Service Gateway (IMSG) by a new topic, Configuring NAT Pools. However, Assigning a NAT Pool was not deleted and should be ignored.

        [Integrated Multi-Service Gateway IMSG]

      • Assigning a NAT Pool for the BGF was replaced in Border Gateway Function (BGF) by a new topic, Configuring NAT Pools. However, Assigning a NAT Pool was not deleted and should be ignored.

      [Integrated Multi-Service Gateway (IMSG), Border Gateway Function (BGF)]

    • The new-transaction-output-policies configuration statement was introduced in JUNOS Release 10.1R1. The document did not mention the following restriction. New transaction policies that include route or message-manipulation options cannot be configured as new-transaction-output-policies.

      [Integrated Multi-Service Gateway (IMSG), Services Interfaces Configuration]

    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]

    • The description for the default-address-selection configuration statement in the System Basics Configuration guide must be: Use the loopback interface (interface to the router’s or switch’s Routing Engine), lo0, for all locally generated IP packets sourced from the interface and sent out on a regular routable interface, but not for packets routed through the loopback interface. [System Basics]
    • The description for the seconds option for the idle-timeout configuration statement must be: The number of seconds a user can remain idle before the session is terminated. Some of the reasons a session can remain idle are:
      • Absence of ingress traffic on the PPP session
      • Absence of egress traffic on the PPP session
      • Absence of either ingress or egress traffic on the PPP session
      • Absence of either ingress or egress traffic on the PPP session
      • Absence of ingress or egress ppp control traffic

      Range—0 through 4,294,967,295 seconds

      Default—0

      [System Basics]

    • Output fields displayed for the show chassis fabric topology command on a TX Matrix Plus router—The description of the output fields on a TX Matrix Plus router for the show chassis fabric topology command is as follows:

      Table 1: Output fields for the show chassis fabric topology command

      Field Name

      Field Description

      Out-Links: and In-Links:

      State of the links from the F13 SIB to the LCC or vice-versa. Out-Links indicate Tx links. In-Links indicate an Rx link. The following additional fields are displayed for each SIB:

      • VCSEL Status—Optical (VCSEL channel) link status for the corresponding electrical (HSL2) link. The states include:
        • OK—Optical signal power is good.
        • Error—Internal error.
        • LOS—Loss of Signal detected.
        • High Cur—The Tx Bias-current is higher than threshold on this channel. This is applicable only to Tx Channels.
        • Low Cur —The Tx Bias-current is lower than threshold on this channel. This is applicable only to Tx Channels.
      • HSL2 Channel—HSL2 is the electrical link used to connect ASICs to the in-link and out-link. The channel number corresponds to the link and varies based on the ASIC or configuration.
      • HSL2 Status —The status of the HSL2 Channel. Includes the following states:
      • Up—Channel is up.
      • Down—Channel is down.
      • Reset—Channel has been reset.
      • Fault—Channel has faults.

      The following is a sample output with description of the fields displayed in the output for Out-Links:

      Out-Links:
      =========
      SF_3_13_FB_A(21,09) -> FPC7_B_SG(3,3,6)_FB_A(18,09)      OK       203     Up 
      
      • SF_3_13—Name of the ASIC, with Fabric F1 or F3 mode. In this case, 3 is the F3 direction and is used in the Tx path. You can also have F1 mode and Rx path instead.
      • FB_A (21, 09)—Fiber bundle A, with VCSEL unit number 21 within the SIB, and channel number 9 within the unit number.
      • FPC7_B_SG(3,3,6—FPC 7.with bottom Packet Forwarding Engine (T for top PFE and B for bottom PFE), SG ASIC, with number 3 and port number 3, with HSL2 link number with the SIB as 6.
      • FB_A(18, 09)—Fiber Bundle, with VCSEL unit number 18 within the SIB, and VCSEL channel number 9 within the unit number.

      The following is a sample output with description of the fields displayed in the output for In-Links:

      In-Links:
      =========
      FPC0_T_SG(0,0,0)_FB_D(04,11)  -> SF_1_00_FB_D(01,11)     OK       0       Up 
      • FPC0—FPC 0.
      • T—Top Packet Forwarding Engine.
      • SG (0, 0, 0)—SG ASIC with port number 0 and link 0.
      • FB_D (04,11)—Fiber Bundle D with VCSEL 4, channel 11.
      • SF_1—Indicates F1 mode and Rx path.
      • SF_1_00_FB_D(01,11) —Indicates F1 mode and Rx path with port 0, fiber bundle D, with VCSEL 1, channel 11.

      [System Basics and Services Command Reference]

    • In Chapter 19, Router Chassis Configuration Guidelines and Chapter 20, Summary of Router Chassis Configuration Statements of the System Basics Configuration Guide, the TX Matrix Plus router is omitted from the list of devices that support the fpc-resync statement. The TX Matrix Plus router does support this statement. [System Basics]
    • The Network Interfaces Configuration Guide, section Creating the IMA Groups (ATM Interfaces) should include the following statement: The PIC is automatically rebooted when a configuration that changes the IMA group count is committed.

      [Network Interfaces]

    • 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 Release 10.4.

      [Network Interfaces]

    • The Configuring Layer 2 Circuit Transport Mode chapter in the Network Interfaces Configuration Guide states that one way to configure an ATM II interface to enable a Layer 2 circuit connection across all versions of JUNOS Software is the following:
      • For Layer 2 circuit cell relay and Layer 2 trunk modes, 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 interface 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 interface interface-name unit logical-unit-number] hierarchy level. When you use the above configuration, keep the following points in mind:

      • • This configuration will interoperate between Juniper Networks routers running JUNOS Release 8.2 or lower.
      • This configuration will NOT interoperate with other network equipment, including a Juniper Networks router running JUNOS Release 8.3 or higher.
      • • For a Juniper Networks router running JUNOS Release 8.3 or higher to interoperate with another Juniper Networks router running JUNOS Release 8.2 or lower, on the router running JUNOS 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 in the MPLS packet.
      • • The use-null-cw statement is not supported on a router running JUNOS Release 8.2 or lower.

      [Network Interfaces]

    Services Applications

    • Border Gateway Function (BGF) apply implicit latching on TCP gates when the gate is created—By default, latching of gates is done by explicit latch requests. You can configure implicit latching of gates by entering the set implicit-tcp-latch and set implicit-tcp-source-filter configuration statements at the [edit services pgcp gateway gateway-name h248-options] hierarchy level.

      The new configuration statements result in the following actions:

      • implicit-tcp-latch—If explicit latching has been applied (using using ipnapt/latch) on either gate of a gate pair, implicit latching is not applied. If explicit latching has not been applied on either gate:
        • Latching is applied to both gates of the gate pair.
        • When either of the gates latches, latching is automatically disabled on the other gate.
      • implicit-tcp-source-filter—Applies source address (but not source port) filtering on incoming packets, using the current remote destination address under the following conditions:
        • Explicit source filtering has not been applied by use of gm/saf.
        • Explicit latching has not been applied by use of ipnapt/latch.

      [Border Gateway Function (BGF), Services Interfaces]

    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

    • In the example Carrier-of-Carriers VPN Example—Customer Provides VPN Service in Chapter 23 Configuration Examples for Interprovider and Carrier-of-Carriers VPNs of the VPNs Configuration Guide, the configurations of Router E and Router H (both PE routers) did not include the as-override statement in the [edit routing-instances vpn-isp1] hierarchy level, causing the examples to not work. This statement has now been added to both configurations. [VPNs]
    • In Chapter 10, Configuring Layer 3 VPNs of the VPNs Configuration Guide, the M10i router is omitted from the list of devices that support the vrf-table-label statement. The M10i router does support this statement. [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]


    Published: 2010-09-28