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

Previous Releases

Release9.1R2

The following issues have been resolved since JUNOS Release 9.1R1.8. The identifier following the description is the tracking number in our bug database.

Software Installation and Upgrade

On an M320 router, when you perform an in-service software upgrade (ISSU), destination class accounting statistics might not be restored properly. [PR/284647: This issue has been resolved.]
On an M320 router, when you perform an ISSU, firewall filter statistics might not be restored properly. [PR/286413: This issue has been resolved.]
On an M320 router, when you perform an ISSU, destination class accounting statistics might not be restored properly. [PR/284647: This issue has been resolved.]

Platform and Infrastructure

When graceful Routing Engine switchover (GRES) and multicast are both configured on a router, the master Routing Engine kernel might dump core because of inconsistencies between the multicast forwarding database on the master Routing Engine and the multicast forwarding database on the backup Routing Engine. [PR/100795: This issue has been resolved.]
When using aggregate bundles with FRR, it takes about 10 to 16 seconds of packet loss when one of the member links fail. [PR/101295: This issue has been resolved.]
If Layer 2 encapsulation is larger than 34 bytes, the Packet Forwarding Engine might restart unexpectedly. [PR/240080: This issue has been resolved.]
An MX platform DPC with a 10x1GE interface might report the same interface statistics on all ports of the same PIC if the first interface has the MPLS family configured on it. As a workaround, do not configure a family interface on the first port of the PIC slot. [PR/262607: This issue has been resolved.]
On MX-series routers, when unicast RPF is configured on an interface (the rpf-check statement is included at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level), the DPC that houses the interface might generate a core file. [PR/275466: This issue has been resolved.]
With JUNOS Release 8.5R2 or later, when protocol tracing is enabled, I/O writes to the hard drive might get blocked causing daemons to delay sending packets. .[PR/278580: This issue has been resolved.]
On M10i routers that have Channelized DS3 IQ PICs installed, the CFEB might generate a core file, which also interrupts FPC operations. [PR/283943: This issue has been resolved.]
The router reboots when using request system software add command with a filename extension other that the one available for download from the Juniper Networks support site, even though the file is otherwise the same. [PR/283948: This issue has been resolved.]

On a J-series router configured to capture packets, certain conditions might trigger messages similar to the following:

Apr  7 15:00:07  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1552
Apr  7 15:00:07  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1556
Apr  7 15:00:09  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1552

These messages indicate that some packets have not been captured as expected. There is no impact on traffic passing though the router. [PR/285242: This issue has been resolved.]

Under certain circumstances, DHCP discover packets might be leaked to all the configured VRFs. [PR/286139: This issue has been resolved.]

Interfaces and Chassis

When graceful Routing Engine switchover is enabled and the backup Routing Engine is taken offline, a CHASSISD_SNMP_TRAP message might not be generated. [PR/238797: This issue has been resolved.]
Very rarely when there is a PIC error and the PIC is coming online again, the system might reset unexpectedly. With the fix, the PIC fails to attach if it has a hardware error. It does not cause the FPC to reset as in the previous case. [PR/241092: This issue has been resolved.]
When you configure MLPPP or MLFR UNI NNI (FRF.16) bundles on link services IQ interfaces, a certain mix of traffic might cause a lower-priority queue to be starved when packets expire after not being scheduled for some time. [PR/262901: This issue has been resolved.]
When a Fast Ethernet interface is connected to a Gigabit Ethernet interface that is configured for full duplex without autonegotiation, the information for the Fast Ethernet interface is incorrect in the Autonegotiation information section of the output from the show interfaces extensive command. [PR/263957: This issue has been resolved.]
For a routing node in a routing matrix, when you remove a hardware component from the chassis, alarms are cleared for that component (which is correct), but also for all components of the same type. [PR/278672: This issue has been resolved.]
If you power off and power on a Routing Engine model RE-A-2000 on a T640 routing node (by issuing the request system power-off other-routing-engine and request system power-on other-routing-engine commands), the output of the show chassis hardware command no longer includes an entry for SPMB 1. [PR/281463: This issue has been resolved.]
Prior to JUNOS Releases 9.0R3 and 9.1R2, you could not unplug a 4-port 10-Gigabit Ethernet PIC without taking the PIC offline first. [PR/288077: This issue has been resolved.]
When you insert an OC-192 SONET/SDH PIC that uses XFP optics into an Enhanced Type 3 FPC on a T640 routing node, the FPC might generate a core file. [PR/288884: This issue has been resolved.]
Under the following conditions, a logical interface configured for VRRP (the vrrp-group statement is included at the [edit interfaces interface-name unit logical-unit-number family family address address] hierarchy level) does not initialize properly and the output for it from the show vrrp summary command displays the value bringup in the VR State field:
1. The logical interface is configured with dual VLAN tags (the vlan-tags statement is included at the [edit interfaces interface-name unit logical-unit-number] hierarchy level)
2. The configuration for another logical interface of the same physical interface includes the vlan-id statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. The problem can occur even though the interfaces do not belong to the same VRRP group.
[PR/288975: This issue has been resolved.]
On an MX-series Ethernet Services router, if you bring fabric planes offline and spare planes are used, you might see high traffic drops or continuous high fabric red drops. To recover from continuous high fabric drops, perform the fabric plane switch again. [PR/291541: This issue has been resolved.]

Services Applications

When you commit a configuration that does not include either the pre-shared-key statement or the local-certificate statement at the [edit security ike policy policy-name] hierarchy level, the key management process (kmd) generates a core file. [PR/267957: This issue has been resolved.]
Services PICs (such as the Adaptive Services and MultiServices PICs) do not record correct information in the SAMPLE-RATE field in the header of the cflowd packets that they export. [PR/276142: This issue has been resolved.]
In a scaling setup with 4000 MLPPP sessions and traffic consisting of 256-byte packets, after traffic flows for more than an hour, the L2TP process does not start when the restart l2tp-service command is issued. [PR/276255: This issue has been resolved.]

Routing Protocols

If more than 1000 communities are attached to a route, the routing process (rpd) might become unresponsive. Removing the communities and restarting the routing process might be necessary to recover. [PR/77001: This issue has been resolved.]
When you activate or deactivate an aggregate route filter (represented by the aggregate statement at the [edit routing-options rib routing-table] hierarchy level, its contributing members are not reevaluated and the filter continues to function as before the change. [PR/270115: This issue has been resolved.]
The show ospf route detail command output displays the optional-capability value for intra-area router routes only. [PR/273809: This issue has been resolved.]
PPMD was not prprogrammed ahead of switchover time. This causes an 8 to 12 second blackout window where no IS-IS Hellos are generated during switchover. [PR/276823: This issue has been resolved.]
With a minimum of two PIM ASM routers and receiver on a LAN segment, if interface mismatch errors occur, an s,g entry will not be created. This is applicable for both native PIM configurations as well as multicast VPN configurations. [PR/281662: This issue has been resolved.]
Using PIM, certain multicast routing topologies might cause delays in multicast route convergence. [PR/282109: This issue has been resolved.]
A BFD v0 session might not be established between a router running a post-JUNOS 8.3 release and a router running a pre-JUNOS 8.3 releases. [PR/286331: This issue has been resolved.]
When BGP multipath is enabled (the multipath statement is included at the [edit protocols bgp group group-name]hierarchy level) and route updates arrive from multipath and nonmultipath peers in a certain order, load balancing across paths might stop working correctly. [PR/288694: This issue has been resolved.]

MPLS Applications

After upgrading to JUNOS Release 8.4 or later, LDP neighborship cannot be established with another vendor's equipment because of a subnet mismatch. The fix adds a new configuration statement, allow-subnet-mismatch, that ignores subnet mismatch for the source address in LDP link hello packets. [PR/285933: This issue has been resolved.]
When the target of the ping mpls rsvp command is another vendor's router, the value in the Local transmit time field is a UNIX timestamp instead of an NTP timestamp as specified by RFC 4379. [PR/289535: This issue has been resolved.]
Packet loss can occur following an RSVP auto-bandwidth adjustment. [PR/289553: This issue has been resolved.]
Other vendors' implementations might send status TLV notification messages with the U-bit set to 0 and F-bit set to 1. While such a combination is not recommended according to RFC 5036, the JUNOS software will tear down the LDP session upon receiving such a status TLV message. [PR/290845: This issue has been resolved.]

Multicast

In JUNOS Release 9.0 and later, the multicast snooping process (snoopd) leaks memory even if it is not configured. As a workaround, disable the process if it is not required. [PR/279378]
When nonstop active routing (NSR) is enabled and you issue the restart routing command on the master Routing Engine, VPLS connections on the backup Routing Engine might not be reestablished quickly. To speed up the synchronization process, issue the restart routing command on the backup Routing Engine. [PR/282095: This issue has been resolved.]

VPNs

The VT tunnel interface is not recreated upon reboot of Tunnel PIC or FPC reboot holding the Tunnel PIC. As a workaround deactivate and activate the vt tunnel interface stanza in the interface configuration. [PR/266170: This issue has been resolved.]
When nonstop active routing (NSR) is enabled and you issue the restart routing command on the master Routing Engine, VPLS connections on the backup Routing Engine might not be reestablished quickly. To speed up the synchronization process, issue the restart routing command on the backup Routing Engine. [PR/282095: This issue has been resolved.]
The delete routing-instances vpls protocols vpls mtu command does not reset the MTU to its default value. As a workaround, deactivate and then reactivate the VPLS instance to set the MTU to the default value of 1500. [PR/288026: This issue has been resolved.]

Class of Service

On the MX960, bandwidth sharing across high priority and strict-high priority schedulers might not be as expected. This issue occurs when the schedulers are configured on logical interfaces. [PR/265603: This issue has been resolved.]
On M120, M320, and MX960 routers, when you configure override input packet classification, the feature might not work. [PR/271660:This issue has been resolved.]
On M120 routers, MX-series routers, and M320 routers with E3-FPCs, MPLS transit traffic with a label stack that performs a pop operation at the penultimate node is not shaped according to the configured transmit rate exact value, which results in more traffic being sent than should be allowed. [PR/282002: This issue has been resolved.]

Forwarding and Sampling

When you commit a configuration that includes a large number of interfaces, routing instances, and policers, the firewall process (dfwd) might generate a core file. [PR/253440: This issue has been resolved.]

Network Management

A syntax error in the mib-rfc3811.txt MIB file prevents SNMP from using the MIB. The file is included in the package accessible at https://download.juniper.net/ software/junos-export/release/juniper-mibs-release-signed.tgz, where release is a JUNOS Release number such as 8.2R4.5. [PR/80648: This issue has been resolved.]

JUNOS SDK

Process health monitor (pmond) will not be able to monitor SDK processes that are spawned after it. Heartbeat updates from those applications will be ignored without any error. [PR/287738: This issue has been resolved.]

Release 9.1R1

The following issues have been resolved since JUNOS Release 9.0R2. The identifier following the description is the tracking number in our bug database.