Errata

This section lists outstanding issues with the documentation.

User Interface and Configuration

• The show system connections command has been enhanced to include a show-routing-instances option. Use the show system connections show-routing-instances command to display routing instances associated with active IP sockets on the Routing Engine. Command output includes IP sockets for all external routing instances and for Juniper Networks Private internal routing instances (which are not externally accessible). [System Basics and Services Command Reference]

Interfaces and Chassis

• To display the FRU model number, part number, and serial number, issue the show chassis hardware models command. To display the FRU model number, part number, and CLEI code, issue the show chassis hardware clei-models command. [System Basics and Services Command Reference]
• FRF.12 is supported on link services (ls-) interfaces on the J-series routing platform. [Services Interfaces]
• The drop-and-insert multiplexer is now integrated into channelized T1/E1 PIMs on J-series Services Routers. The data-input [system | interface interface-name] statement at the [edit interfaces ds-pim/0/port:channel] hierarchy level is not documented in the JUNOS Network Interfaces Configuration Guide.
• The following errata applies to the Graceful Routing Engine Switchover PIC Support table in the “Graceful Routing Engine Switchover System Requirements” section of the JUNOS High Availability Configuration Guide:

  The release information for the following PIC types should be changed to:

  Table 3: Graceful Routing Engine Switchover PIC Support

  PIC Type	M10i	M20	M40e	M120	M320	T320	T640	TX Matrix
  Adaptive Services PICs	7.3	7.3	7.3	–	–	–	–	–
  Adaptive Services II PICs	7.2	7.2	7.2	8.2	7.2	7.2	7.2	7.3
  Adaptive Services II PICs with Link Services IQ (LSQ) interfaces	7.6	7.6	7.6	8.2	7.6	7.6	7.6	n/a

  Information for the following PIC types should be added to the table:

  Table 4: Graceful Routing Engine Switchover PIC Support

  PIC Type	M10i	M20	M40e	M120	M320	T320	T640	TX Matrix
  MultiServices 100	8.1R2	–	8.1R2	8.2	8.1R2	8.1R2	8.1R2	8.1R2
  MultiServices 400	–	–	8.1R2	8.2	8.1R2	8.1R2	8.1R2	8.1R2
  MultiServices 500	–	–	–	8.3	8.3	8.3	8.3	8.3

• IP address definition for the master Routing Engine—Enables you to configure a management IP address so that it is always used by the master Routing Engine, even in the case of a failover event. To configure this feature, include the master-only statement at the [edit interfaces fxp0 unit logical-unit-number family inet address ip-address] hierarchy level on the master Routing Engine. [Network Interfaces]
• To configure the Link Aggregation Control Protocol (LACP), include the lacp statement at the [edit protocols] hierarchy level. [Network Interfaces]

Services Applications

• Support for simultaneous port-mirroring of IPv4 and IPv6 packets has been expanded to include the M120 routing platforms. [Feature Guide]
• The documentation currently states that the JUNOS software supports RFC 2766, Network Address Translation – Protocol Translation (NAT-PT). The JUNOS software does not currently comply with this RFC. [Hierarchy and RFC Reference]

General Routing

• The manuals currently list only the M10i, M20, M40e, M320, T320 and T640 routing platforms as supported routing platforms for the GRES for VPLS feature. The TX Matrix routing platform also supports GRES for VPLS. [System Basics, Feature Guide, VPNs]

Routing Protocols

• The Routing Protocols and Policies Command Reference for JUNOS Releases 8.1, 8.2, and 8.3 erroneously states that spt-pending is a valid PIM sparse-mode multicast operational condition. In order to comply with RFC 2362 for PIM sparse-mode operation, the spt-pending state for the shortest-path tree status has been eliminated starting with JUNOS Release 8.1.

MPLS Applications

• Inter-AS traffic engineering (Phase 2)—Provides traffic-engineered MPLS LSPs with the ability to dynamically discover OSPF autonomous system boundary routers (ASBRs) and allows routers to establish a traffic-engineered LSP across multiple autonomous systems (ASs). Each AS is assumed to be under the control of a single service provider and to use OSPF. To configure traffic engineering across multiple ASs using OSPF, include the traffic-engineering statement at the [edit protocols (ospf | ospf3) area area-id interface interface-name passive] hierarchy level. [MPLS Applications]
• Range for static MPLS LSP labels—The recommended range for static MPLS label-switched path (LSP) labels is now 1,000,000 through 1,048,575. The previous recommended range for static labels was 10,000 through 99,999. Old configurations that have static labels outside the new range cause a commit failure. You configure static MPLS labels using the label-map statement at the [edit protocols mpls interface interface-name] hierarchy level. The range of 10,000 through 99,999 is now used by the JUNOS software for processing LSI labels. [MPLS Applications]

VPNs

• Limitations for LSI-based VPLS—When you configure VPLS without a Tunnel Services PIC by including the no-tunnel-services statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level, the following limitations apply:
  • An Enhanced FPC is required.
  • Aggregated SONET/SDH interfaces used as core-facing interfaces are not supported.
  • Channelized interfaces used as core-facing interfaces are not supported.
  • ATM1 interfaces are not supported. [VPNs]
• The JUNOS 8.3 VPNs Configuration Guide erroneously states that graceful Routing Engine switchover is not supported for VPLS. Graceful Routing Engine switchover support for VPLS was added in JUNOS Release 8.3 and later. [VPNs]

Class of Service

• As stated in the documentation, you can selectively set the DSCP field of IPv4 and IPv6 packets to 0 without affecting output queue assignment, and continue to set the MPLS EXP field according to the configured rewrite table, based on forwarding classes. This feature is not supported with GRE and IP-IP tunnels. The documentation incorrectly implies that you can use the dscp 0 action modifier to set the DSCP field of IPv4 and IPv6 packets to 0. For IPv4 traffic, the dscp 0Service action modifier at the [edit firewall family inet filter filter-name term term-name then] hierarchy level is valid. However, for IPv6 traffic, you configure this feature by including the traffic-class 0 action modifier at the [edit firewall family inet6 filter filter-name term term-name then] hierarchy level. [Class of Service]
• On J-series Services Routers, if you create a policy to match IPv4 traffic with a route filter and assign the traffic to a forwarding class, and then apply the policy at the [edit class-of-service forwarding-policy class policy-name] hierarchy level, use of the classification-override statement at the [edit class-of-service forwarding-policy class policy-name] hierarchy level is not supported. [J-series Services Router Advanced WAN Access Configuration Guide]
• For J-series Services Routers deploying strict-high priority scheduling, the JUNOS and J-series manuals incorrectly state that the out-of-profile limit does not work when you configure shaping on the interface. The out-of-profile limit does work with shaping. [Class of Service, J-series Services Router Advanced Configuration Guide]
• For 4-port Fast Ethernet ePIMs on J4350 and J6350 Services Routers, if you apply a CoS scheduler map on outgoing (egress) traffic, the router does not divide the bandwidth appropriately among the CoS queues. As a workaround, configure enforced CoS shaping on the ports. [J4350 and J6350 Getting Started Guide]

Routing Policy and Firewall Filters

• Floating point metric multiplier values in routing policies are now limited to eight significant digits. [Policy Framework]
• In the documentation for the extended DHCP relay agent feature, the syntax for the server-group statement is incorrectly documented as server-groups. You can include the server-group statement at the [edit forwarding-options dhcp-relay] hierarchy level to configure a named group of DHCP server addresses for use by the extended DHCP relay agent on the router. The correct syntax for the server-group statement is as follows:

  [edit forwarding-options dhcp-relay]

  server-group {

  server-group-name {

  server-ip-address;

  }

  }

  [Policy Framework]

Network Management

• The documentation states incorrectly that the JUNOS software supports RFC 2737, Entity MIB (Version 2). [Network Management, Hierarchy and RFC Reference]