Specifications

General Routing
•
On MX Series platform with Enhanced DPCs equipped, after router rebooted, the IRB
broadcast channel is not enabled, all the broadcast packets that are received in the
IRB interface will get dropped. Also when ping is given the below L2Channel error
increases as ping packets are sent: user@router>show interfaces ge-*/*/* extensive
| match channel L3 incompletes: 0, L2 channel errors: 10, L2 mismatch timeouts: 0.
PR876456
•
DPD may not work with link-type IPSec tunnels when NAT is present between the
IPSec peers. Even when NAT is not present between the IPsec peers, the issue can
occur with lesser probability. PR895719
•
On T/TX/TXP platforms, once detecting rchip sram parity errors, both parity-error
correction process and automatic jtree simulation are invoked within interrupt context
which triggers an assertion and resulting a FPC restart with coredump. FPC Type 5-3D
are not affected. Junos OS Releases 13.3R1 and later are exposed. PR944967
•
When a router is booted with AE having per-unit-scheduler configuration and hosted
on an EQ DPC, AE as well as its children get default traffic control profile on its control
logical interface. However, if a non-AE GE interface is created on the DPC with
per-unit-scheduler configuration, it will get default scheduler map on its control logical
interface. PR946927
•
In large scale L3VPN environment(in this case, there are 80K L3VPN routes) with
non-stop active routing (NSR) enabled, when the L3VPN routes are added and deleted
frequently, in rare condition, the Composite Next Hop (cnh) deletion from kernel after
backup rpd process learns cnhs with duplicated key but with different nhids. This might
lead to rpd process crash on backup Routing Engine. This issue is not reproducible and
only happened once. PR959331
•
On MX Series, delete an interface A from routing-instance VRF1; then create
routing-instance VRF2 and interface A is added to VRF2 with qualified-next-hop
configured; finally, delete VRF1. Commit the entire above configuration once, in rare
condition, rpd might crash. PR985085
•
On MX104 router with SONET/SDH OC3/STM1 (Multi-Rate) MIC. In rare condition, if
the MIC is plugged out from MX104, the PFE might crash, the traffic forwarding will be
affected. These MICs as below belong to SONET/SDH OC3/STM1 (Multi-Rate) MIC:
* MIC-3D-8OC3OC12-4OC48 * MIC-3D-4OC3OC12-1OC48 *
MIC-3D-8CHOC3-4CHOC12 * MIC-3D-4CHOC3-2CHOC12 * MIC-3D-8DS3-E3 *
MIC-3D-8CHDS3-E3-B * MIC-3D-1OC192-XFP. PR997821
•
An unnecessary update from the routing protocol process (rpd) to the route record
database might be triggered by certain configuration change. This process causes jump
in CPU utilization of all Packet Forwarding Engines. PR1002107
•
On MX Series Virtual Chassis with the no-split-detection configured, in some rare
circumstances, the transit traffic might get dropped if all of the virtual chassis ports
(VCP) go down and come up quickly (within few seconds). PR1008508
81Copyright © 2015, Juniper Networks, Inc.
Resolved Issues