Specifications
•
On MX Series platform with one of the following protocols configuration, flapping the
protocols will trigger the Composite Next-hop change operation. In rare condition,
since it is not proper programmed, the FPC might crash. This is a day-1 issue. - LDP -
MPLS - Point-to-multipoint LSP - RSVP - Static LSPs. PR1045794
•
Once default route 0.0.0.0/0 is added, deleted or changed, the PFEMAN thread running
on the MPC/FPC5 needs more than 600 mseconds to program such changes. This is
long enough to trigger LFM or BFD flap. Junos OS Release 13.3R2 or later is exposed to
this symptom. PR1045828
•
On T Series FPC 1-3 and M320 except E3-FPC with fib-local configuration. If there are
multiple FIB local FPCs or the FIB local is a multiple Packet Forwarding Engine FPC,
the TCP packets might be out of order, packets re-ordering would occur. It reduces the
application level throughput for any protocols running over TCP. PR1049613
•
In the PPP dual-stack subscribers environment, in rare condition, if bringing up 1000
dual-stack subscribers quickly, the PPP negotiation might fail. Then PPP retries
negotiation, all subscribers fully establish. PR1050415
•
Incorrect flow count is reported in the field 'count' of V9 header in all the packets sent
to the collector. PR1050543
•
This problem is because of a race condition, where other FPCs are not able to drain
"which is 1 second" Fabric Streams connecting to FPC which is getting offline. With
this situation - even when FPC comes online, other FPCs which have observed message
"xmchip_dstat_stream_wait_to_drain" will not be able to send traffic to that particular
FPC over fabric. There is no workaround. To recover, we have to reboot FPCs which
observed error message "xmchip_dstat_stream_wait_to_drain". PR1052472
•
As a precautionary measure, a periodic sanity check is added to Ichip based FPC. It
checks FPC error conditions and performs the appropriate actions in case of an error.
PR1056161
•
IFCM error messages may occur in logs when it is not used. We lowered the severity of
the message to avoid confusion. PR1057712
•
This problem scenario with stuck DEMUX VLANs was observed after upgrade to 12.3
from previous release of 11.4X27. PR1054914
•
When enabling pseudowire subscribers the "show subscribers extensive" command
does not display CoS policies applied to the subscriber interface. This issue was fixed
in 13.3R6, 14.1R5 and 14.2R3. PR1060036
•
bfd-protected ospf-session and bfd-protected bgp-session fail to come up via site-site
IPSec tunnel. As a workaround use no-ipsec-tunnel-in-traceroute cli configuration
statement. PR1061342
83Copyright © 2015, Juniper Networks, Inc.
Resolved Issues