Errata

This section lists outstanding issues with the documentation.

User Interface and Configuration

• The show system statistics bridge command displays system statistics on MX-series routers. [System Basics Command Reference]
• When specifying a URL in a JUNOS statement using an IPv6 host address, you must enclose the entire URL in quotation marks (" ") and enclose the IPv6 host address in brackets ([ ]). For example, "ftp://username<:password>@[host-address]<:port>/url-path" or "scp://username<:password>@[host-address]<:port>/url-path". This type of URL format appears in the system archival statement syntax. Not using the quotations and brackets in conjunction with using an IPv6 host address results in a failure when the transfer on commit is executed. [System Basics]
• The System Basics Configuration Guide included on the JUNOS 9.2 Release Documentation DVD includes incorrect information regarding remote tracing. See http://www.juniper.net/techpubs/software/junos/ to download the revised JUNOS 9.2 System Basics Configuration Guide. The revised information is in Chapter 3, “System Management Overview,” in the “Tracing and Logging Operations” section. [System Basics]

• The following two commands return the message “No valid completions”:

  • help reference vrrp ?
  • help topic schedulers ?
  This is the expected result, because the system does not include reference information about configuration statements at the [edit protocols vrrp] hierarchy level or usage guidelines for configuration statements at the [edit scheduler] hierarchy. Reference information for statements at the [edit protocols vrrp] hierarchy is available in JUNOS Release 9.3 and later.

Interfaces and Chassis

• To configure the Link Aggregation Control Protocol (LACP), include the lacp statement at the [edit protocols] hierarchy level. [Network Interfaces]
• For IQ2 interfaces, you can define the TPIDs expected to be sent or received on a particular VLAN. For each Gigabit Ethernet port, you can configure up to eight TPIDs using the tag-protocol-id statement; but only the first four TPIDs are supported on IQ2 interfaces. Any fifth through eighth TPIDs configured for IQ2 interfaces are not functional. [Network Interfaces]

Routing Protocols

• AS-dot notation format for 4-byte autonomous system numbers is not supported. Only the plain-text format for 4-byte AS numbers is currently supported. [Routing Protocols, Policy Framework, Routing Protocols and Policies Command Reference]

MPLS Applications

• To ensure compatibility with other vendors’ equipment, it was necessary to alter the behavior of point-to-multipoint (P2MP) LSPs. JUNOS 9.2 and later releases now accept Resv messages which include the S2L_SUB_LSP object. JUNOS 9.1 and earlier releases automatically reject any Resv messages with the S2L_SUB_LSP object. In networks in which equipment is running both the later and earlier releases of the JUNOS software and which also have P2MP LSPs configured, you need to include the no-p2mp-sublsp statement at the [edit protocols rsvp] hierarchy level on devices running JUNOS Release 9.2 and later software. [MPLS Applications]

VPNs

• The LDP BGP VPLS Interworking feature is currently supported only on MX-series and M320 routers. [VPNs, Feature Guide]
• The connectivity-type (ce | irb) configuration statement enables you to specify when a VPLS connection is taken down depending on whether or not the interface for the VPLS routing instance is customer facing or Integrated Routing and Bridging (IRB). To enable this feature, include the connectivity-type (ce | irb) statement at either of the following hierarchy levels:
  • [edit logical-routers logical-router-name routing-instances routing-instance-name protocols vpls]
  • [edit routing-instances routing-instance-name protocols vpls]

  The default value is ce. [VPNs]

Class of Service

• The JUNOS Class-of-Service Configuration Guide incorrectly states that high-priority queues on the IQ2 PICs and EQ DPCs can starve lower priority queues unless rate limited. In fact, any higher priority queue (even medium) can starve a lower priority queue (such as low) unless rate limited. [Class of Service]
• You cannot apply a percentage-based output policer to E3 interfaces that are being shaped to a lower rate for subrate services. The policer appears to continue to operate against the full bandwidth of the interface and not the shaped rate. [Policy Framework]

Protected System Domain

• In Chapter 7, “Summary of JCS Management Module Configuration Commands,” the correct syntax for the documented conf command is config. [JUNOS Release 9.2 JUNOS Protected System Domain Configuration Guide]
• In Chapter 6, “Configuring the JCS 1200 Platform,” the example in the “Configuring the System Name and Contact Information” section incorrectly uses the syntax conf. Additionally in this example, the location option should be documented as loc. [JUNOS 9.2 Release JUNOS Protected System Domain Configuration Guide]
• In Chapter 6, “Configuring the JCS 1200 Platform,” the example under the “Configuring the SNMP Community” section incorrectly specifies the letter l instead of the number 1. The example should read:

  system:mm[1]> snmp -c3i1 192.168.171.100 -ca3 trap 

  [JUNOS Release 9.2 JUNOS Protected System Domain Configuration Guide]

Subscriber Access

• Some links in the HTML output for the 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.

High Availability

• The section entitled “Nonstop Active Routing BFD Support” in the JUNOS High Availability Configuration Guide states that the minimum value for the minimum-interval statement (a BFD liveliness detection parameter) for distributed BFD sessions is 100 msec. However, the minimum allowed value for the minimum-interval statement in JUNOS Release 9.1 and later is 10 ms and not 100 ms as mentioned in the document.