Specifications

reassigned to a template filter. This could be considered as a timing issue given it comes
with a very specific sequence of events only. PR949975
•
When a port being used for port mirroring goes down due to an external factor, such
as a fiber cut or the remote side rebooting, the FPC CPU may rise to 100% for 4 minutes
and then followed by a reboot of the FPC with a reason of "pfeman watchdog expired".
The issue will only be observed occasionally and requires that the FPC CPU is already
very busy and very large firewall filters (thousands of terms long) to be used. If any of
these three factors are not present, the issue will not occur. As such disabling the port
being used for port mirroring on the Juniper prior to bringing down that link is sufficient
to avoid this issue. PR968393
•
On MX Series based line card, VPLS traffic might get blocked for about 5 minutes
(timer of MAC address aged-out) after re-negotiating control-word. PR973222
•
The problem is seen because CFMD is getting a configuration commit after the MX-VC
switch has happened. This commit is deleting the cfmd session and then creating a
new session which is causing the old information of action-profile to be deleted which
brings the interface back up. This problem is fixed by the code correction. PR974663
•
On MX Virtual Chassis platforms, if you configure the interface alias feature, the feature
might not work as expected and interfaces might go up and down after commit.
PR981249
•
Have BFD session between one router supporting inline-BFD (MX Series and Junos 13.3
or higher) and the other which does not support inline-BFD (any version and non-MX
Series, or MX Series and Junos OS prior to 13.3). When the "failure detection time" is
less than 50 ms, the BFD session might flap. PR982258
•
On MX2020/MX2010 we might see sporadic FO request time-out error reported under
heavy system traffic load. This would mean the request returning into a grant took
longer then +/-30usec. The packet will still get forwarded through the fabric hence no
operational impact. [May 6 18:56:59.174 LOG: Err] MQCHIP(2) FO Request time-out
error [May 6 19:33:47.555 LOG: Info] CMTFPC: Fabric request time out pfe 2 plane 6
pg 0, trying recovery PR991274
•
Packets dropped with IPv6 reject route are currently subjected to loopback ipv6 filter
processing on MX Series-based line cards. As a result the packet dropped by a reject
route may be seen from the "show firewall log". PR994363
•
On an MX Series router with MX Series linecard or T4000 router with type5. When the
firewall filter under the [forwarding-options] hierarchy within a bridge domain is
removed, it might result in lookup error and frame drop might be observed. PR999083
•
In the IRB interface environment with "destination-class-usage" configuration. If the
bridge domain ID is the same as Destination Class Usage (DCU) ID (bridge domain ID
and DCU ID are generated by system), the firewall filter might match wrong packets,
the packet forwarding would be affected. PR999649
•
On M7i, or M10i equipped with Enhanced Compact Forwarding Engine Board (CFEB-E).
When a MPLS LSP flaps, the CFEB-E is unable to recover 8 bytes of JTREE memory
per event. PR1000385
•
MS PIC may reset after GRES in case of excessive resolve traffic. PR1001620
Copyright © 2015, Juniper Networks, Inc.108
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series