Errata

This section lists outstanding issues with the documentation.

Software Installation

• New request system firmware upgrade and request system firmware downgrade operational mode commands have been added for installing firmware on PIMs on J-series Services Routers. To display firmware information, issue the show system firmware operational mode command. [Command Reference: System Basics and Services]
• On J-series Services Routers, when you install a software upgrade from a remote location using the request system software add validate ftp://hostname/pathname/package-name or request system software add validate http://hostname/pathname/package-name command, the package is removed at the earliest opportunity in order to make room for the installation to be completed. If you copy the software to a local directory on the router and then install the new package, use the unlink option with the request system software add validate pathname/package-name command to achieve the same effect and allow the installation to complete. [Command Reference: System Basics and Services]

Platform and Infrastructure

• The JUNOS software now uses the name dfc for the local1 facility. The facility is for messages related to dynamic flow capture. [System Basics]
• For a description of system log messages that are generated by the dfc facility, please contact Juniper Networks customer support. [System Log Messages Reference]

User Interface

• You cannot use the J-Web interface to configure a discard action for IPv6 firewall filters. You can only configure the discard action for IPv4 firewall filters. [J-Web Interface User Guide]

Interfaces and Chassis

• For Frame Relay encapsulation, the default protocol MTU is 1504 bytes, instead of the documented value of 4470 bytes. [Network Interfaces]
• The startup-silent-period seconds statement has been added at the [edit protocols vrrp] hierarchy level to instruct the system to ignore the Master Down Event when an interface transitions from the disabled state to the enabled state. This option is used to avoid an incorrect error alarm caused by delay or interruption of incoming VRRP advertisement packets during the interface startup phase. The range of values, in seconds, is from 1 to 2000. The default value is 4. [Network Interfaces]
• The idle-cycle-flag configuration statement is now included at the additional hierarchy level of [edit interfaces interface-name serial-options] for serial interfaces on J-series Services Routers only. [Network Interfaces]
• The dynamic flow capture (dfc-) interface supports up to 10,000 filter criteria. When more than 10,000 filters are added to the interface, the filters are accepted, but system log messages are generated indicating that the filter is full.
• On a G.SHDSL PIM on a J4300 or J6300 Services Router:
  • Only 2-port, 2-wire mode is supported and is enabled by default. 1-port, 4-wire mode is not supported.
  • Payload loopback functionality is not supported on ATM-over-SHDSL interfaces.
  • The show interfaces (ATM-over-SHDSL) command description of the Line mode output field includes a 4-wire option. This option is not supported on ATM-over-SHDSL interfaces.

  [Network Interfaces, J-series Configuration Guide, Command Reference: Interfaces]

• Byte counts in the output from the show interfaces queue command vary by PIC type. Table 3 show byte counts for each PIC type when outbound interfaces send IP traffic with 478 bytes per packet.

  Table 3: Byte Count by PIC Type

  PIC Type	Output Level	Byte Count Includes	Comments
  Gigabit Ethernet IQ PIC	Interface	Queued: 490 bytes per packet, representing 478 bytes of Layer 3 packet + 12 bytes Transmitted: 490 bytes per packet, representing 478 bytes of Layer 3 packet + 12 bytes RED dropped: 496 bytes per packet representing 478 bytes of Layer 3 packet + 18 bytes	The 12 additional bytes include 6 bytes for the destination media access control (MAC) address + 4 bytes for the virtual LAN (VLAN) + 2 bytes for the Ethernet type. For RED dropped, 6 bytes are added for the source MAC address.
  	Packet forwarding component	Queued: 478 bytes per packet, representing 478 bytes of Layer 3 packet Transmitted: 478 bytes per packet, representing 478 bytes of Layer 3 packet
  Non-IQ PIC	Interface	Queued: 478 bytes of Layer 3 packet + the full Layer 2 overhead Transmitted: 478 bytes of Layer 3 packet + the full Layer 2 overhead	The Layer 2 overhead is 14 bytes for non-VLAN traffic and 18 bytes for VLAN traffic.
  IQ PIC with a SONET/SDH interface	Interface	Queued: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes Transmitted: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes RED dropped: 482 bytes per packet, representing 478 bytes of Layer 3 packet + 4 bytes	The additional 4 bytes are for the Layer 2 PPP header.
  	Packet forwarding component	Queued: 478 bytes per packet, representing 478 bytes of Layer 3 packet Transmitted: 486 bytes per packet, representing 478 bytes of Layer 3 packet + 8 bytes	For transmitted packets, the additional 8 bytes includes 4 bytes for the PPP header and 4 bytes for a cookie.
  Non-IQ PIC with a SONET/SDH interface	Interface	Queued: 478 bytes per packet, representing 478 bytes of Layer 3 packet Transmitted: 483 bytes per packet, representing 478 bytes of Layer 3 packet + 5 bytes RED dropped: 478 bytes per packet, representing 478 bytes of Layer 3 packet	For transmitted packets, the additional 5 bytes includes 4 bytes for the PPP header and 1 byte for the PLP.

  [Command Reference: Interfaces]

• For Gigabit Ethernet IQ PICs, the output from the show interfaces ge-fpc/pic/port extensive command for traffic and MAC statistics varies by interface type. Table 4 shows the traffic and MAC statistics for two sample interfaces, each of which are sending traffic in packets of 500 bytes each (including 478 bytes for the Layer 3 packet, 18 bytes for the Layer 2 VLAN traffic header, and 4 bytes for cyclic redundancy check [CRC] information).

  In Table 4, the ge-0/3/0 interface is the inbound physical interface, and the ge-0/0/0 interface is the outbound physical interface. On both interfaces, traffic is carried on logical unit .50 (VLAN 50). [Command Reference: Interfaces]

  Table 4: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type

  Interface Type	Sample Command	Byte and Octet Counts Include	Comments
  Inbound physical interface	show interfaces ge-0/3/0 extensive	Traffic statistics: Input bytes: 496 bytes per packet, representing the Layer 2 packet MAC statistics: Received octets: 500 bytes per packet, representing the Layer 2 packet + 4 bytes	The additional 4 bytes are for the CRC.
  Inbound logical interface	show interfaces ge-0/3/0.50 extensive	Traffic statistics: Input bytes: 478 bytes per packet, representing the Layer 3 packet
  Outbound physical interface	show interfaces ge-0/0/0 extensive	Traffic statistics: Input bytes: 490 bytes per packet, representing the Layer 3 packet + 12 bytes MAC statistics: Received octets: 478 bytes per packet, representing the Layer 3 packet	For input bytes, the additional 12 bytes includes 6 bytes for the destination MAC address + 4 bytes for the VLAN + 2 bytes for the Ethernet type.
  Outbound logical interface	show interfaces ge-0/0/0.50 extensive	Traffic statistics: Input bytes: 478 bytes per packet, representing the Layer 3 packet

• For a T1 (t1-) interface configured on a channelized T1 (ct1-)interface on a Channelized T1 IQ PIC, you can configure the following T1 options, but in fact, these options do not take effect for the T1 interface:
  • bert-algorithm
  • bert-error-rate
  • bert-period
  • buildout
  • framing
  • line-encoding
  • loopback
  • remote-loopback-respond

  The T1 interface inherits these option settings from the parent channelized T1 (ct1-) interface. [Network Interfaces]

Services Applications

• You can clear dynamic flow capture information using the clear services dynamic-flow-capture (criteria | sequence-number) command. [System Basics and Services Command Reference]
• To configure CoS for DLSw on J-series Services Routers, include the destination-interface destination-interface and type-of-service tos-value statements at the [edit protocols dlsw dlsw-cos] hierarchy level and the dscp default statement at the [edit class-of-service interfaces interface-name unit unit-number classifiers] hierarchy level. The documentation incorrectly describes the destination-interface destination-interface statement as sna-destination-interface sna-destination-interface, and incorrectly describes the [edit protocols dlsw dlsw-cos] hierarchy level as the [edit protocols dlsw sna-cos] hierarchy level. [J-series Configuration Guide, Services Interfaces]
• On J-series Services Routers, if the values for the following configuration statements at the [edit protocols dlsw] hierarchy level are modified, any existing DLSw peer connection is torn down: connection-idle-timeout, dlsw-cos, local-peer, multicast-address, promiscuous, and receive-initial-pacing. If the remote-peer remote-peer-name statement is added or removed, only that remote peer and its associated circuits are affected. Any changes made to the values for the traceoptions statement do not affect existing peer connections or circuits.
• NAT now enables you to use dynamic source configuration to translate a large range of addresses to a smaller size pool. To configure this feature, include the translation-type source dynamic statement at the [edit services nat rule rule-name term term-name then] hierarchy level. The referenced pool must include a port or address configuration. [Services Interfaces]

General Routing

• Next-hop groups support—You can configure the next-hop-group statement at the [edit forwarding-options] hierarchy level only on M5, M7i, M10, M10i, M20, M40, M40e, and M160 routers. [Feature Guide]

Routing Protocols

• The ignore-lsp-metrics configuration statement has been added at the [edit protocols isis traffic-engineering shortcuts] hierarchy level. This statement instructs the system to ignore the metric of the MPLS LSP and removes the mutual dependency between IS-IS and MPLS for the shortcut computation. If this option is not configured, there may be a short interval during which IS-IS prefers the IP hop-by-hop path, even though an MPLS LSP is available. [Routing Protocols, MPLS Applications]
• When you include the vrf-table-label statement at the [edit routing-instances instance-name] hierarchy level, MPLS packets with label-switched interface (LSI) labels that arrive on core-facing ATM or Frame Relay interfaces, or on aggregated Ethernet interfaces configured with VLANs or Ethernet interfaces configured with VLANs, are not counted at the logical interface level. [Routing Protocols, MPLS Applications]
• Explicit null option for IPv6-based BGP—Enables you to advertise an explicit null for BGP when using labeled unicast in an IPv6 network. To configure the explicit null option, include the explicit-null statement at the [edit protocols bgp group group-name family inet6 labeled-unicast] hierarchy level. [Routing Protocols]
• The JUNOS implementation of BFD now supports version 1 and automatic version detection. By default, the system is set to automatic detection. To modify the BFD version, include the bfd-liveness-detection version (0 | 1 | automatic) statement at any of the following hierarchy levels:
  • [edit protocols isis interface interface-name]
  • [edit protocols (ospf | ospf3) area area-id interface interface-name]
  • [edit routing-instances routing-instance-name protocols isis interface interface-name]
  • [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name]
  • [edit routing-instances instance-name routing-options rib rib-name static route destination]
  • [edit routing-instances instance-name routing-options rib rib-name static route destination qualified-next-hop next-hop]
  • [edit routing-instances instance-name routing-options static route destination]
  • [edit routing-instances instance-name routing-options static route destinationqualified-next-hop next-hop]
  • [edit routing-options rib rib-name static route destination]
  • [edit routing-options rib rib-name static route destination qualified-next-hop next-hop]
  • [edit routing-options static route destination]
  • [edit routing-options static route destination qualified next-hop next-hop]

  [Routing Protocols]

• To enable unicast RPF check on an interface, you must include the unicast-reverse-path statement at the [edit routing-options forwarding-table] hierarchy level and include the rpf-check statement at the [edit interfaces interface-name unit logical-unit-number (inet | inet6)] hierarchy level. [Routing Protocols]

Multicast

• MDTs and Tunnel PICs—When configuring multicast over VPNs according to Internet draft draft-rosen-vpn-mcast-07.txt, each tunnel PIC supports 512 multicast tunnel (mt-) interfaces. Configurations that allow more than 512 multicast tunnels require another tunnel PIC. Both default and data multicast distribution trees (MDTs) contribute to this total. There are typically two default multicast tunnels (one for encapsulation and the other for de-encapsulation). If a router with a single tunnel PIC tries to create more than 512 default or data MDTs, no traffic flows for tunnels created in excess of 512. For example, a configuration that allows 500 data MDTs requires only a single tunnel PIC (500 + 2 = 502). However, a configuration that allows 1000 data MDTs requires two tunnel PICs (1000 + 2 = 1002). Up to 1024 multicast tunnels are supported with two tunnel PICs. [Multicast]

Routing Policy

• The JUNOS documentation incorrectly states that firewall filters based on TCP cannot be used on Enhanced II FPCs with TCM configured. [Class of Service, Policy Framework]

VPNs

• Optimization of VPLS traffic flows—To improve the performance VPLS traffic processing in your routing platform, you can implement the following features:
  • To optimize VPLS traffic flows across multiple paths, you can enable per-packet load balancing. To configure, include the load-balance per-packet statement at the [edit policy-options policy-statement policy-name term term-name then] hierarchy level and apply the policy to the forwarding table with the export policy-name statement at the [edit routing-options forwarding-table] hierarchy level.
  • To optimize hashing of source and destination MAC addresses within VPLS traffic flows, include the source-mac and destination-mac statements at the [edit forwarding-options hash-key family multiservice] hierarchy level.

  [Policy Framework, Feature, Guide, VPNs]

Class of Service

• When you configure tricolor marking on a 10-port 1-Gigabit Ethernet PIC, for queues 6 and 7 only, the output of the show interfaces queue interface-name command does not display the number of queued bytes and packets, or the number of bytes and packets dropped because of RED. If you do not configure tricolor marking on the interface, these statistics are available for all queues. [Class of Service]
• For T-series platforms that have Enhanced II FPCs and are configured to use tricolor marking, you can set the loss priority with a BA classifier. Previously, on T-series platforms, you needed to set the loss priority using an MF classifier. [Class of Service]
• Table 5 lists the maximum scheduler buffer sizes. When large buffer sizes are not enabled, maximum sizes vary by PIC and platform type. When large buffer sizes are enabled, maximum sizes differ by interface type. The q-pic-large-buffer statement is not supported on Gigabit Ethernet IQ PICs and has no effect on Gigabit Ethernet IQ VLANs. [Class of Service]

  Table 5: JUNOS 7.4 Maximum Scheduler Buffer Sizes

  Platform, PIC, or Interface Type	Maximum Buffer Size
  With Large Buffer Sizes Not Enabled
  T-series and M320	50,000 microseconds
  Other M-series	200,000 microseconds
  IQ PICs on all platforms	100,000 microseconds
  With Large Buffer Sizes Enabled
  Channelized T3 and channelized OC3 DLCIs—Maximum sizes vary by shaping rate:
  With shaping rate from 64,000 through 255,999 bps	4,000,000 microseconds
  With shaping rate from 256,000 through 511,999 bps	2,000,000 microseconds
  With shaping rate from 512,000 through 1,023,999 bps	1,000,000 microseconds
  With shaping rate from 1,024,000 through 2,048,000 bps	500,000 microseconds
  With shaping rate from 2,048,001 through 10 mbps	400,000 microseconds
  With shaping rate from 10,000,001 through 20 mbps	300,000 microseconds
  With shaping rate from 20,000,001 through 30 mbps	200,000 microseconds
  With shaping rate from 30,000,001 through 40 mbps	150,000 microseconds
  With shaping rate up to 40,000,001 bps and above	100,000 microseconds
  NxDS0 IQ Interfaces—Maximum sizes vary by channel size:
  1xDS0 through 3xDS0	4,000,000 microseconds
  4xDS0 through 7xDS0	2,000,000 microseconds
  8xDS0 through 15xDS0	1,000,000 microseconds
  16xDS0 through 32xDS0	500,000 microseconds
  Other IQ interfaces	500,000 microseconds

• The JUNOS Class of Service Configuration Guide contains the erroneous caveat: “TCM does not work when the memory allocation dynamic (MAD) mechanism is disabled.” [Class of Service]

Forwarding and Sampling

• Next-hop groups support (M-series routers, except the M320 router)—You can configure the next-hop-group statement at the [edit forwarding-options] hierarchy level on M5, M7i, M10i, M20, M40, M40e, and M160 routers. [Feature Guide]

JUNOS API and Other Scripting

• Indicator for configuration identifiers—Client applications can request that the JUNOScript server's response to a <get-configuration> request indicate that a child tag element is an identifier for its parent tag element. As the indicator, the junos:key="key" attribute is included in the opening tag for each identifier tag element. To request the indicator, a JUNOScript client that uses the Perl module provided by Juniper Networks provides the junos_key => 1 parameter to the JUNOS::Device object along with the four parameters required by the object (access, hostname, login, and password). A JUNOScript client that does not use the Perl module includes the junos:key="key" attribute in the opening <junoscript> tag that it emits at the beginning of the JUNOScript session. [JUNOScript Guide]
• In the chapter of the JUNOScript API Guide titled “Controlling the JUNOScript Session,” the section titled “Locking the Configuration” shows a sample tag exchange. The tag elements returned by the JUNOScript server are not correct in the example. The correct tag elements are as follows and are described in the text that precedes the example:

  <rpc-reply xmlns:junos=”URL”>

  </rpc-reply>