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

Errata

This section lists outstanding issues with the documentation.

Platform and Infrastructure

The output of the show chassis fpc and show chassis hardware commands has been modified to indicate when an interface type is not supported for a particular software release or in a particular PIM slot on J-series Services Routers. [System Basics and Services Command Reference]
For a description of system log messages that are generated by the dfc facility, please contact Juniper Networks customer support. [System Log Messages Reference]
To restart the Layer 2 address flooding and learning process, issue the restart l2learning command. There is no restart l2ald command. [System Basics and Services Command Reference]
For J-series Services Routers, the multiservice statement at the [edit forwarding-options hash-key family] hierarchy level is not supported. This statement will be removed from the CLI for J-series routers in a future JUNOS release. [Routing]

Interfaces and Chassis

For Gigabit Ethernet IQ2 PICs, the show interfaces queue command output does not display the number of queued packets, because the counter is unsupported. [Interfaces Command Reference]
The JUNOS 8.0 Internet Software supports the 10-Gigabit Ethernet IQ2 PIC on M320 and T-series routers. In some copies of the printed manual, the new interface type used with the 10-Gigabit Ethernet IQ2 PIC is referred to as xge-fpc/pic/port. The interface type prefix xge- has been changed to xe-. The correct interface type to use with the 10-Gigabit Ethernet IQ2 PIC is xe-fpc/pic/port. [Network Interfaces, Interfaces Command Reference]
For 10-Gigabit Ethernet PICs with XENPAK optics installed in M320 and T-series routing platforms, the following fields have been added to the output of the show interfaces diagnostics optics interface-name-fpc/pic/port command:
- Optical diagnostics
- Laser bias current
- Laser output power
- Module temperature
- Laser rx power
[Interfaces Command Reference]
On M320 and T-series routing platforms, address and control field compression (ACFC) is not supported for any ISO family protocols. As a result, do not include the acfc statement at the [edit interfaces interface-name ppp-options compression] hierarchy level when you include the family iso statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. [Network Interfaces]
For 4–port OC192 PICs installed in M320 and T-series routing platforms, the following limitations exist when you include the aggregate-ports statement at the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level:
- The maximum difference in delay between all links in the bundle is 8 µs (approximately 1.5 km in distance).
- If a single link in the bundle fails, then the whole bundle fails. If link redundancy is required, implement an aggregated SONET/SDH bundle instead.
[Network Interfaces]
RS-232 serial interfaces cannot function error-free with a clock rate greater than 200 KHz. [J-series Basic Configuration]
On J-series Services Routers, payload loopback functionality is not supported on ATM-over-SHDSL interfaces. [J-series Basic Configuration]
On J-series Services Routers, Gigabit Ethernet interfaces have autonegotiation enabled (not disabled) by default. When autonegotiation is disabled and the link mode and speed are not configured, the link is negotiated in full-duplex mode at 1000 Mbps. [J-series Basic Configuration]
The JUNOS Network Interfaces Configuration Guide incorrectly states that the J-series management interface is fe-0/0/0. On the J2300, J4300, and J6300 Services Routers, the fe-0/0/0 interface is often used as the management interface. However, you can also configure the fe-0/0/1 interface for use as a management interface. On the J4350 and J6350 routers, any of the four built-in ports (ge-0/0/0 through ge-0/0/3) can be used as a management interface. [Network Interfaces]
For Gigabit Ethernet PIMs installed in J-series Services Routers, you can now explicitly configure the speed of the interface. You can set the speed on these interfaces to 10, 100, or 1000 Mbps. You must explicitly disable autonegotiation for the speed setting to take effect. [Network Interfaces]
When you configure flexible-vlan-tagging encapsulation on an Ethernet-based interface that does not support this encapsulation type, the system logs an error message but maintains the interface state as up. However, the interface state is shown as down in the output of the show vrrp summary command. [Network Interfaces]
On T-series routing platforms and TX Matrix platforms, link aggregation for Ethernet and SONET/SDH interfaces now supports a maximum number of 16 links per bundle (increased from eight). The maximum number of links supported on M-series platforms remains at eight. To configure the number of links, include the minimum-link statement at the following hierarchy levels: [edit interfaces aex aggregated-ether-options] or [edit interfaces asx aggregated-sonet-options]. [Network Interfaces]
Path MTU discovery for GRE and IPIP tunnels—Provides support for controlling path MTU settings on a per-tunnel basis and on a global basis for GRE and IPIP tunnels. To enable path MTU discovery for all GRE tunnels, include the gre-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To enable path MTU discovery for all IPIP tunnels, include the ipip-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To enable path MTU discovery for a specific tunnel, include the 'path-mtu-discovery' statement at the [edit interfaces interface-name unit logical-unit-number tunnel] hierarchy level.
Path MTU discovery is enabled by default. To disable path MTU discovery for all GRE tunnels, include the no-gre-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To disable path MTU discovery for all IPIP tunnels, include the no-ipip-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To disable path MTU discovery for a specific tunnel, include the no-path-mtu-discovery statement at the [edit interfaces interface-name unit logical-unit-number tunnel] hierarchy level. [System Basics]

Note: Enabling path MTU discovery requires you to configure the tunnel-level statement and the system-level statement simultaneously.

Services Applications

If you configure real-time performance monitoring (RPM) probes for a services interface (sp-), you need to announce local routes in a specific way for the following routing protocols:
- For OSPF, you can announce the local route by including the services interface in the OSPF area. To configure a services interface in an OSPF area, include the interface sp-fpc/pic/port statement at the [edit protocols ospf area area-number] hierarchy level.
- For BGP and IS-IS, you must export interface routes and create a policy that accepts the services interface local route. To export interface routes, include the point-to-point and lan statements at the [edit routing-options interface-routes family inet export] hierarchy level. To configure an export policy that accepts the services interface local route, include the protocol local, rib inet.0, and route-filter sp-interface-ip-address/32 exact statements at the [edit policy-options policy-statement policy-name term term-name from] hierarchy level and the accept action at the [edit policy-options policy-statement policy-name term term-name then] hierarchy level. For the export policy to take effect, apply the policy to BGP or IS-IS with the export policy-name statement at the [edit protocols protocol-name] hierarchy level.
[Services Interfaces]
If you configure real-time performance monitoring (RPM) timestamping on an AS PIC, you cannot configure the source-address statement at the [edit services rpm probe probe-name test test-name] hierarchy level. [Services Interfaces]
Dynamic or tunnel mode IPSec security associations (SAs) are not supported for OSPFv3. If you add SAs into OSPFv3 by including the ipsec-sa statement at the [edit protocols ospf3 area area-number interface interface-name] hierarchy level, your configuration fails to commit. [Services Interfaces]

Routing Protocols

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 value has been removed from the “Flag” field in the output of the show pim join extensive command. [Multicast]
The minimum BGP hold time value is 20 seconds. To configure the BGP hold time, include the hold-time statement at the [edit protocols bgp], [edit protocols bgp group group-name], or [edit protocols bgp group group-name neighbor ip-address] hierarchy level. You can also configure the BGP hold time for routing instances and logical routers at the global, group, and neighbor hierarchy levels. [Routing]
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 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. [Routing]

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]

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 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, Feature Guide]

Class of Service

The JUNOS documentation incorrectly states that firewall filters based on the Transmission Control Protocol (TCP) cannot be used on Enhanced II FPCs with tricolor marking (TCM) configured. [Class of Service, Policy Framework]
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 0 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, you cannot include the classification-override statement at the [edit class-of-service forwarding-policy class policy-name] hierarchy level. The classification-override statement is not supported under these conditions. [Class of Service]
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 in fact does work with shaping. [Class of Service, J-series Advanced Configuration]
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. [J–series Advanced Configuration]
For link services intelligent queuing (LSQ) interfaces configured on Adaptive Services or MultiServices PICs, you can configure a value of 80 for the fragment-threshold statement at the [edit class-of-service fragmentation-maps forwarding-class class-name] hierarchy level. [Class of Service]

Routing Policy and Firewall Filters

Floating point metric multiplier values in routing policies are now limited in range to eight significant digits. [Policy Framework]

Network Management

Gigabit Ethernet interfaces (both built-in and PIM interfaces) installed in J-series Services Routers do not support SNMP. [Network Management]

The traps listed in Table 2 are defined, but are not generated. [Network Management]

Table 2: Unsupported Traps

MIB	Trap Name	Description
isismib.mib	isisDatabaseOverload	Generated when the system enters or leaves the overload state.
	isisManualAddressDrops	Generated when one of the manual areaAddresses assigned to the system is ignored when the routing platform computes routes.
	isisCorruptedLSPDetected	Generated when an LSP stored in memory becomes corrupted.
	isisAttemptToExceedMaxSequence	Generated when the sequence number on a generated LSP wraps the 32-bit sequence counter and the number is purged.
	isisIDLenMismatch	Generated when a PDU is received with a different value for the system ID length. This trap includes an index to identify the circuit where the PDU was received and the PDU header.
	isisMaxAreaAddressesMismatch	Generated when a PDU with a different value for the maximum area addresses is received.
	isisOwnLSPPurge	Generated when a PDU is received with a system ID and zero age. This notification includes the circuit index, if available.
	isisSequenceNumberSkip	Generated when an LSP is received with a system ID and different contents, indicating the LSP may require a higher sequence number.
	isisAuthenticationTypeFailure	Generated when a PDU with the wrong authentication type field is received.
	isisAuthenticationFailure	Generated when a PDU with an incorrect authentication information field is received.
	isisVersionSkew	Generated when a hello PDU from an IS running a different version of the protocol is received.
	isisAreaMismatch	Generated when a hello PDU from an IS that does not share any area address is received.
	isisRejectedAdjacency	Generated when a hello PDU from an IS is received, but no adjacency is established because of a lack of resources.
	isisLSPTooLargeToPropagate	Generated when an LSP that is larger than the dataLinkBlockSize for a circuit is attempted, but not propagated.
	isisOriginatingLSPBufferSizeMismatch	Generated when a Level 1 LSP or Level 2 LSP is received that is larger than the local value for originating L1LSPBufferSize or originating L2LSPBufferSize respectively, or when a Level 1 LSP or Level 2 LSP is received containing the originating LSPBufferSize option and the value in the PDU option field does not match the local value for originating L1LSPBufferSize or originating L2LSPBufferSize, respectively.
	isisProtocolsSupportedMismatch	Generated when a non-pseudonode, segment 0 LSP is received that has no matching protocols.
jnx-bgpmib2.mib	jnxBgpM2Established	Generated when the BGP FSM enters the Established state.
jnx-bgpmib2.mib	jnxBgpM2BackwardTransition	Generated when the BGP FSM moves from a higher-numbered state to a lower-numbered state.
jnx-sonetaps.mib	apsEventFEPLF	Generated when the value of an instance of apsStatusFEPLFs increments.
l3vpnmib.mib	mplsVrfIfUp	Generated when the ifOperStatus of an interface associated with a VRF changes to the up(1) state, or when an interface with ifOperStatus = up(1) is associated with a VRF.
	mplsVrfIfDown	Generated when the ifOperStatus of an interface associated with a VRF changes to the down(1) state, or when an interface with ifOperStatus = up(1) state is disassociated from a VRF.
	mplsNumVrfRouteMidThreshExceeded	Generated when the number of routes contained by the specified VRF exceeds the value indicated by mplsVrfMidRouteThreshold.
	mplsNumVrfRouteMaxThreshExceeded	Generated when the number of routes contained by the specified VRF reaches or attempts to exceed the maximum allowed value indicated by mplsVrfMaxRouteThreshold.
	mplsNumVrfSecIllglLblThrshExcd	Generated when the number of illegal label violations on a VRF as indicated by mplsVpnVrfSecIllegalLblVltns has exceeded mplsVpnVrfSecIllegalLblRcvThrsh.
ldpmib.mib	mplsLdpInitSesThresholdExceeded	Generated when the value of mplsLdpEntityInitSesThreshold is not zero and the number of session initialization messages exceeds the value of mplsLdpEntityInitSesThreshold.
	mplsLdpPathVectorLimitMismatch	Generated when the mplsLdpEntityPathVectorLimit does not match the value of the mplsLdpPeerPathVectorLimit for a specific entity.
	mplsLdpSessionUp	Generated when the value of mplsLdpSesState enters the operational(5) state.
	mplsLdpSessionDown	Generated when the value of mplsLdpSesState leaves the operational(5) state.
msdpmib.mib	msdpEstablished	Generated when the MSDP FSM enters the Established state.
msdpmib.mib	msdpBackwardTransition	Generated when the MSDP FSM moves from a higher-numbered state to a lower-numbered state.
rfc1747.mib	sdlcPortStatusChange	Generated when the state of an SDLC port transitions to active or inactive.
rfc1747.mib	sdlcLSStatusChange	Generated when the state of an SDLC link station transitions to contacted or not contacted
rfc2115a.mib	frDLCIStatusChange	Generated when a virtual circuit changes state (has been created or invalidated, or has toggled between the active and inactive states).
rfc2662.mib	adslAtucRateChangeTrap	Generated when the ATUCs transmit rate has changed (RADSL mode only).
	adslAtucPerfLofsThreshTrap	Generated when the loss of framing 15-minute interval threshold is reached.
	adslAtucInitFailureTrap	Generated when ATUC initialization fails.
	adslAturPerfLprsThreshTrap	Generated when the loss of power 15-minute interval threshold is reached.
	adslAturRateChangeTrap	Generated when the ATURs transmit rate changes (RADSL mode only).
rfc3020.mib	mfrMibTrapBundleLinkMismatch	Generated when a bundle link mismatch is detected.
rfc3813.mib	mplsXCUp	Generated when mplsXCOperStatus for one or more contiguous entries in mplsXCTable enters the up(1) state from some other state.
rfc3813.mib	mplsXCDown	Generated when mplsXCOperStatus for one or more contiguous entries in mplsXCTable enters the down(2) state from some other state.

JUNOS API and Scripting

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

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