Errata

This section lists outstanding issues with the documentation.

Platform and Infrastructure

• The following note has been added to the section titled “Requirements for Routers with a Backup Router Configuration” in Chapter 6 of the JUNOS 8.5 High Availability Configuration Guide:

  Note: If you have a backup router configuration in which multiple static routes point to a gateway from fxp0, you must configure prefixes that are more specific than the static routes or include the retain flag at the [edit routing-options static route] hierarchy level. For example, if you configure the static route 172.16.0.0/12 from fxp0 for management purposes, you must specify the backup router configuration as follows: backup-router 172.29.201.62 destination [172.16.0.0/13 172.16.128.0/13]

  [High Availability]

• The following errata replaces the entire section titled “Graceful Routing Engine Switchover System Requirements” in Chapter 5 of the JUNOS 8.5 High Availability Configuration Guide.

  Graceful Routing Engine switchover supports most Physical Interface Cards (PICs) on the M10i, M20, M40e, M120, M320, T320, T640TX Matrix, and T1600 routers with the appropriate version of JUNOS software. Use Table 1 to determine which JUNOS software release provides initial graceful Routing Engine switchover support for PICs installed in your router. A dash (–) indicates that support is not available. Except where noted, the JUNOS software release is R1.

  Note: When an unsupported PIC is online, you cannot enable graceful Routing Engine switchover. If graceful Routing Engine switchover is already enabled, an unsupported PIC cannot come online.

  The following constraints apply to graceful Routing Engine switchover PIC support:

  • You can include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level on a router with Adaptive Services and MultiServices PICs configured on it and issue the commit command. The commit succeeds. However, all services on these PICs are reset during a switchover.
  • Graceful Routing Engine switchover is not supported on any Monitoring Services PICs or Multilink Services PICs. If you include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level on a router with either of these PIC types configured on it and issue the commit command, the commit fails.
  • Graceful Routing Engine switchover is not supported on MultiServices 400 PICs configured for monitoring services applications. If you include the graceful-switchover statement, the commit fails.

  Table 1: Graceful Routing Engine Switchover PIC Support

  PIC Type	M10i	M20	M40e	M120	M320	T320	T640	TX Matrix	T1600
  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	8.5
  Adaptive Services II PICs with Link Services IQ (LSQ) interfaces	7.6	7.6	7.6	8.2	7.6	7.6	7.6	–	8.5
  Adaptive Services II FIPS PICs	7.3	–	7.3	8.2	7.3	–	–	–	–
  ATM2 DS3 IQ PICs	6.1	6.1	6.1	8.2	6.4	–	8.0	8.0	8.5
  ATM2 E3 IQ PICs	6.1	6.1	6.1	8.2	6.3	7.4	7.4	7.4	8.5
  ATM2 OC3/STM1 IQ PICs	6.1	6.0	6.0	8.2	6.2	6.0	7.6	7.6	8.5
  ATM2 OC12/STM4 IQ PICs, 1-port	6.1	6.0	6.0	8.2	6.2	6.0	8.0	8.0	8.5
  ATM2 OC12/STM4 IQ PICs, 2-port	–	–	6.0	8.2	6.2	6.0	6.0	7.0	8.5
  ATM2 OC48/STM16 IQ PICs with SFP	–	–	7.3	8.2	7.3	7.3	7.3	7.3	8.5
  Channelized DS3 PICs	6.1	6.0	6.0	–	–	–	–	–	–
  Channelized OC12 PICs	6.1	6.0	6.0	–	–	–	–	–	–
  Channelized DS3 IQ PICs	6.1	6.1	6.1	8.2	6.2	6.3	8.0	8.0	8.5
  Channelized E1 IQ PICs	6.1	6.1	6.1	8.2	6.2	–	–	–	–
  Channelized OC3 IQ PICs	7.1	7.1	7.1	8.2	7.1	7.1	7.6	7.6	8.5
  Channelized OC12 IQ PICs	6.1	6.1	6.1	8.2	6.2	6.1	6.3	7.0	8.5
  Channelized STM1 IQ PICs	6.1	6.1	6.1	8.2	6.2	6.1	7.5	7.5	8.5
  Channelized T1 IQ PICs	7.4	7.4	7.4	8.2	7.4	–	–	–	–
  DS3 PICs	6.1	6.0	6.0	8.2	6.2	6.0	6.3	7.0	8.5
  E1 PICs	6.1	6.0	6.0	8.2	6.4	–	–	–	–
  E3 PICs	6.1	–	–	–	6.3	–	–	–	–
  E3 IQ PICs	6.1	6.1	6.1	8.2	6.2	6.2	6.3	7.3	8.5
  EIA-530 PICs	6.1	6.0	6.0	–	–	–	–	–	–
  ES PICs	6.1	6.1	6.1	–	6.2	6.1	–	–	–
  Fast Ethernet PICs, 4-port	6.1	6.0	6.0	8.2	6.2	6.0	6.3	7.0	8.5
  Fast Ethernet PICs, 8-port	6.1	6.0	6.0	8.2	6.3	–	–	–	–
  Fast Ethernet PICs, 12-port	6.1	6.0	6.0	8.2	6.2	6.1	–	–	–
  Fast Ethernet PICs, 48-port	–	–	6.0	8.2	6.4	–	–	–	–
  Fast Ethernet PICs (aggregated)	6.2	6.2	6.2	8.2	6.2	6.2	6.2	7.0	8.5
  Gigabit Ethernet PICs with SFP, 1-port	6.4	6.4	6.4	8.2	6.4	6.4	8.0	8.0	8.5
  Gigabit Ethernet PICs with SFP, 1-port	6.4	6.4	6.4	8.2	6.4	6.4	8.0	8.0	8.5
  Gigabit Ethernet PICs with SFP, 2-port	–	–	6.4	8.2	6.4	6.4	6.4	7.0	8.5
  Gigabit Ethernet PICs with SFP, 4-port	–	–	7.0	8.2	7.0	7.0	7.0	7.0	8.5
  Gigabit Ethernet PICs with SFP, 10-port	–	–	–	8.2	6.2	6.0	6.0	7.0	8.5
  Gigabit Ethernet IQ PICs, 1-port	7.0	7.0	7.0	8.2	7.0	7.0	8.0	8.0	8.5
  Gigabit Ethernet IQ PICs, 2-port	–	–	7.0	8.2	7.0	7.0	7.0	7.3	8.5
  Gigabit Ethernet IQ2 PICs, 4-port	7.6	–	7.6	8.2	7.6	7.6	7.6	7.6	8.5
  Gigabit Ethernet IQ2 PICs, 8-port	–	–	7.6	8.2	7.6	7.6	7.6	7.6	8.5
  10-Gigabit Ethernet DWDM PICs	–	–	–	8.2	7.5	7.5	7.5	7.5	8.5
  10-Gigabit Ethernet XENPACK PICs	–	–	–	8.2	6.2	6.2	6.2	7.0	8.5
  Link Services PICs	7.0	7.0	7.0	–	7.0	–	–	–	–
  MultiServices 100	8.1R2	–	8.1R2	8.2	8.1R2	8.1R2	8.1R2	8.1R2	8.5
  MultiServices 400	–	–	8.1R2	8.2	8.1R2	8.1R2	8.1R2	8.1R2	8.5
  MultiServices 500	–	–	–	8.3	8.3	8.3	8.3	8.3	8.5
  SONET/SDH OC3c/STM1 PICs, 2-port Type 1	6.1	–	–	–	–	–	–	–	–
  SONET/SDH OC3c/STM1 PICs, 4-port Type 1	6.1	6.0	6.0	8.2	6.2	7.1	7.1	7.1	8.5
  SONET/SDH OC3c/STM1 PICs, 4-port Type 2	–	–	–	–	–	6.0	6.0	7.0	8.5
  SONET/SDH OC3/STM1 PICs with SFP, 2-port Type 1	8.4	8.4	–	–	–	–	–	–	–
  SONET/SDH OC3/STM1 (Multi-Rate) with SFP, 4-port Type 1	8.4	8.4	8.4	8.4	8.4	8.4	8.4	8.4	8.5
  SONET/SDH OC3/STM1 (Multi-Rate) with SFP, 4-port Type 2	–	–	8.3	8.3	8.3	8.3	8.3	8.3	8.5
  SONET/SDH OC12c/STM4 SMIR PICs, 1-port Type 1	6.1	6.0	6.0	8.2	6.2	7.5	6.0	7.0	8.5
  SONET/SDH OC12c/STM4 MM PICs, 1-port Type 1	–	–	–	–	–	–	7.1	7.1	8.5
  SONET/SDH OC12c/STM4 PICs, 4-port Type 2	–	–	6.0	8.2	6.2	6.0	6.0	7.0	8.5
  SONET/SDH OC12/STM4 (Multi-Rate) with SFP, 1-port Type 1	8.4	8.4	8.4	8.4	8.4	8.4	8.4	8.4	8.5
  SONET/SDH OC12/STM4 (Multi-Rate) with SFP, 4-port Type 2	–	–	8.3	8.3	8.3	8.3	8.3	8.3	8.5
  SONET/SDH OC48c/STM16 PICs with SFP, 1-port quad-wide Type␣1	6.4	6.1	–	–	–	–	–	–	–
  SONET/SDH OC48c/STM16 PICs with SFP, 1-port Type 2	–	–	6.1	8.2	6.2	6.1	6.1	7.0	8.5
  SONET/SDH OC48c/STM16 PICs with SFP, 4-port Type 3	–	–	–	8.2	6.2	6.2	6.2	7.0	8.5
  SONET/SDH OC48/STM16 (Multi-Rate) with SFP, 1-port, Type 2	–	–	8.3	8.3	8.3	8.3	8.3	8.3	8.5
  SONET/SDH OC192c/STM64 PICs, 1-port Type 3	–	–	–	8.2	6.2	6.0	6.0	7.0	8.5
  SONET/SDH OC768c/STM256 PICs, 1-port Type 4	–	–	–	–	–	–	7.5	7.5	8.5
  SONET/SDH PICs (aggregated)	6.2	6.2	6.2	8.2	6.2	6.2	6.2	7.0	8.5
  T1 PICs	6.1	6.0	6.0	8.2	6.4	–	–	–	–
  Tunnel Services PICs, Type 1	6.1	6.0	7.0	8.2	6.2	6.1	8.0	8.0	8.5
  Tunnel Services PICs, Type 2	–	–	7.0	8.2	6.2	6.1	6.1	7.0	8.5
  Tunnel Services PICs, Type 3	–	–	–	8.2	6.3	6.0	6.0	7.0	8.5
  Tunnel Services PICs, 40-gigabit	–	–	–	–	–	–	8.0	8.0	8.5

  [High Availability]

User Interface and Configuration

• When you configure a logical-router system administrator, you cannot also configure graceful Routing Engine switchover (GRES) on the router. [PR/237070]
• J-Web Quick Configuration pages do not support IPv6 addressing and routing. [J-series Basic Configuration]
• The new bridge option to the show system statistics command displays system statistics on MX-series routers. The option is not documented in the JUNOS System Basics and Services Command Reference.
• The new static-mac statement at the [edit routing-instances instance-name protocols l2vpn site site-name interface interface-name] and [edit routing-instances instance-name protocols vpls site site-name interface interface-name] is not documented in the JUNOS VPNs Configuration Guide.

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 in to 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.
• To configure the Link Aggregation Control Protocol (LACP), include the lacp statement at the [edit protocols] hierarchy level. [Network Interfaces Configuration Guide]
• IP address for the master Routing Engine—Enables you ton configure a management IP address that is always used by the master Routing Engine, even when a failover occurs. To configure, include the master-only statement at the [edit interfaces fxp0 unit logical-unit-number inet address ip-address] hierarchy level on the master Routing Engine. [Network Interfaces Configuration Guide]

Services Applications

• The documentation does not include information about the clear-ike-sas-on-pic-restart statement, which you can include at the [edit services ipsec-vpn] hierarchy level to have the IKE SAs associated with tunnels cleared automatically when an AS PIC goes offline or is restarted. [Services Interfaces]

General Routing

• The manuals currently state that only the following routing platforms support GRES for VPLS: M10i, M20, M40e, M320, T320, and T640. The TX Matrix routing platform also supports GRES for VPLS. [System Basics, Feature Guide, VPNs]

Routing Protocols

• For the Spanning Tree Protocol (STP) bridge domain configuration and show spanning-tree bridge command shown in the Routing Protocols Configuration Guide, the words bridge domain should be bridge. In addition, the extended system ID is now configurable. [Routing Protocols Configuration Guide]
• To configure Layer 2 control protocol features, include the layer2-control statement at the [edit protocols] hierarchy level. Routing Protocols Configuration Guide

MPLS Applications

• Inter-AS traffic engineering (Phase 2) enables traffic-engineered MPLS LSPs to dynamically discover OSPF autonomous system boundary routers (ASBRs) and enables 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]
• 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. Configurations that have static labels outside the new range cannot be committed. To configure static MPLS labels, include the label-map statement at the [edit protocols mpls interface interface-name] hierarchy level. The JUNOS software now uses the range of 10,000 through 99,999 for processing label-switched interface (LSI) labels. [MPLS Applications]

VPNs

• The statement hierarchy for the vpls statement shown in the “Configuring the VPLS Routing Instance” section includes an extraneous bracket character (}). The corrected statement hierarchy is as follows:

  vpls {

  active-inteface {

  any;

  primary interface-name;

  }

  interface-mac-limit limit;

  mac-table-size size;

  neighbor neighbor-id;

  no-tunnel-services;

  site site-name {

  active-interface {

  any;

  primary interface-name;

  }

  interface interface-name {

  interface-mac-limit limit;

  }

  multi-homing;

  site-identifier identifier;

  site-preference preference-value;

  }

  site-range number;

  traceoptions {

  file filename <replace> <size size> <files number> <no-stamp>;

  flag flag <flag-modifier> <disable>;

  }

  tunnel-services {

  devices device-names;

  primary primary-device-name;

  }

  vpls-id vpls-id;

  }

  [VPNs]
• You cannot configure the mac-table-aging-time statement on MX-series routers. [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. [CoS]
• On J-series Services Routers, if you create a policy to match IPv4 traffic with a route filter, 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 Advanced Configuration, CoS]
• For 4-port Fast Ethernet ePIMs on J-series 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. [J-series Getting Started]

Routing Policy and Firewall Filters

• Floating point metric multiplier values in routing policies are now limited to eight significant digits. [Policy]
• In the documentation for the extended DHCP relay agent feature in the JUNOS 8.3 Policy Framework Configuration Guide, 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;

  }

  }

JUNOS XML API and Scripting

• In the JUNOS 8.4 Configuration and Diagnostic Automation Guide, which also applies to JUNOS Release 8.5, the section titled “Using Regular Expressions to Refine the Set of Events That Cause a Policy to Be Executed” includes a cross reference to a configuration example, but the target link is missing. The correct target is the section titled “Controlling Event Policy Using a Regular Expression” (http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-automation
  /controlling-event-policy-using-a-regular-expression.html). [Automation]