Specifications

•
On MX Series platforms with ADPC FPCs, M120, or M7i/M10i with Enhanced CFEB, each
VPLS LSI interface flapping triggers a memory leak in jtree segment 0. There is no
memory leak in FPC heap 0 memory. PR1009985
•
When destinations are pointing to protocol next-hops as unilist type or IP forwarding
next-hops as unilist, which in scenarios like using Loop-Free Alternate Routes for OSPF
(LFA-OSPF) with link protection or MPLS FRR is enabled. If flapping the active interface
very fast, especially an interface comes back up before Kernel gets a chance to delete
all the unilist next-hops, those unilist next-hops which have not been deleted yet would
be re-used. As a result, the corresponding destinations are pointing to discard
next-hop(s) or replaced next-hop(s) in Packet Forwarding Engine Jtree. The "discard"
next-hop(s) causes traffic blackhole while the "replaced" next-hop(s) diverts traffic
to other active next-hop(s) in the unlist. Those unilist next-hops which have been
already deleted are safe and get updated accordingly. This is a day one timing issue.
PR1016649
•
Under corner cases, if there are multiple back-to-back Virtual Chassis port (VCP)
related CLI commands, Network Processing Card (NPC) core may be observed and
FPC hosting the VC ports might reboot. PR1017901.
•
If you issue the show services nat mappings details command with a large number of
service sets configured (such as 1000 service sets) and one or two NAT mappings
specified, the command takes a certain amount of time to display the output. During
this period, if you deactivate or activate the services, a multiservices PIC management
daemon core file is generated. PR1019996
•
Enabling sampling on an ms- interface is not supported configuration, if
'forwarding-opions sampling sample-once' is subsequently deactivated, the FPC may
reboot. PR1021946
•
On MX Series router with IPv6 subscribers, after performing GRES or reloading one line
card which has underlying interfaces for demux, some demux interfaces might be stuck
in Tentative state, and some other demux interfaces which has the same link local
addresses might be unable to send any IPv6 RA message. PR1026724
•
On MPC5E line card, if a firewall filter with large-scale terms (more than 1300 etc.) is
attached to an interface, traffic drop might be seen. PR1027516
•
With an unrecognized or unsupported Control Board (CB), mismatch link speed might
be seen between fabric and FPCs, which results in FPCs CRC/destination errors and
fabric planes offline. Second issue is in a race condition, Fabric Manager (FM) might
process the stale destination disable event but the error is cleared indeed, it will result
in the unnecessary FPC offline and not allowing Fabric Hardening action to trigger and
recover. PR1031561
•
If a logical interface is used as the qualified-next-hop (which implies the logical interface
has unnumbered-address configured), and there are changes in the logical interface
filter configuration, then the static route might disappear from routing table. To make
it reappear, need to delete it from the configuration and add it back. PR1035598.
•
For MLPPP interface on MX Series based line card, in some very rare conditions, the
received fragmented packets might be dropped. PR1041412
Copyright © 2015, Juniper Networks, Inc.82
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series