[Contents][Prev][Next][Report an Error]

Errata

This section lists outstanding issues with the documentation.

User Interface and Configuration

The show system connections command includes 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 Private internal routing instances (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. [JUNOS System Basics and Services Command Reference]
FRF.12 is supported on link services (ls-) interfaces on the J-series routing platform. [JUNOS Services Interfaces Configuration Guide]
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.]
On J-series Services Routers, RS-232 serial interfaces cannot function error-free at speeds greater than 200 KHz. [J-series Basic LAN and WAN Access Configuration Guide]

Services Applications

The J-series documentation states that you can timestamp UDP ping and UDP ping timestamp RPM probes. However, the Services Router supports hardware timestamping of UDP ping and UDP ping timestamp RPM probes only if the destination port is UDP-ECHO. [J-series Services Router Administration Guide]
Two new voice services statements, the dynamic-call-admission-control and bearer-bandwidth-limit statements, are erroneously listed as the dynamic-cac and bbl statements. Otherwise, the descriptions for these statements are correct. [JUNOS Services Interfaces Configuration Guide]
The JUNOS Feature Guide incorrectly states that passive flow monitoring is supported on the M120 router. In fact, passive flow monitoring is not supported on the M120 router. [JUNOS Feature Guide]

General Routing

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

Routing Protocols

The delegate-processing statement at the [edit routing-options ppm] hierarchy level is not documented at this time. [JUNOS Routing Protocols Configuration Guide]

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 Configuration Guide]
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. [MPLS Applications Configuration Guide]

Multicast

The policy listing in the Multicast section "Creating the Flow Map Policy" for JUNOS Release 8.2 and 8.3 is incorrect. The correct policy for the desired result is:

[edit policy-options]
prefix-list permanentEntries1 {
    232.1.1.0/24;
}
policy-statement policyForFlow1 {
    from {
        source-address-filter 11.11.11.11/32 exact;
        prefix-list-filter permanentEntries1 orlonger;
    }
    then accept;
}

The 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 spare-mode operation, the "spt-pending" state for shortest-path tree status has been eliminated starting with JUNOS Release 8.1.

VPNs

The JUNOS 8.2 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.2 and later. 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.
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. [JUNOS VPNs Configuration Guide]

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. [JUNOS Class of Service Configuration Guide]
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, 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]
The IQ PIC default average packet size is now 40 bytes. In previous releases, the default was 256 bytes. The new large-scale statement at the [edit chassis fpc fpc-slot pic pic-slot q-pic-large-buffer] hierarchy level that modifies the packet size to 256 bytes is not documented. [JUNOS Class of Service Configuration Guide, JUNOS System Basics Configuration Guide, Network Interfaces 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. [JUNOS Class of Service Configuration Guide, J-series Services Router Advanced WAN Access 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 8 significant digits. [JUNOS Policy Framework Configuration Guide]

Network Management

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

JUNOS API and Scripting

The BGP_PROCESS_OPEN event is not defined in the JUNOS software. [JUNOS Configuration and Diagnostic Automation Guide]

[Contents][Prev][Next][Report an Error]