Specifications

•
When sending traffic coming on MPC and going out on DPC, the MAC entry on a Packet
Forwarding Engine will not be up-to-date and the frames targeted to a known MAC
address will be flooded across the bridge domain. PR1003525
•
The non-first IP fragments containing UDP payload may be mistakenly interpreted as
PTP packets if the following conditions are met: - the byte at the offset 9 in the IP
packet contains 0x11 (decimal 17) - UDP payload - the two bytes at the offset 22 in the
IP packet contain the value 0x01 0x3f (decimal 319; byte 22=0x01 and byte 23=0x3f)
- PTP protocol The mis-identification of the packet as PTP will trigger the corruption
of the fragment payload. PR1006718
•
When Micro-BFD configurations is added after the ae bundle configuration, then
micro-bfd session for all the member links remains in "Down" state. Below is the snippet
as reference, when ae100 LACP state is "Disturbing", while micro-BFD session remain
in "Down" state while on the other end the session would be in "Init" state.
user@ndoeA> show lacp interfaces ae100 Aggregated interface: ae100 LACP state:
Role Exp Def Dist Col Syn Aggr Timeout Activity xe-0/3/0 Actor No No Yes Yes Yes
Yes Fast Active xe-0/3/0 Partner No No Yes Yes Yes Yes Fast Active xe-0/3/1 Actor
No No Yes Yes Yes Yes Fast Active xe-0/3/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State xe-0/3/0 Current Fast periodic
Collecting distributing xe-0/3/1 Current Fast periodic Collecting distributing
user@ndoeA> show bfd session address 10.10.100.145 Detect Transmit Address State
Interface Time Interval Multiplier 10.10.100.145 Down xe-0/3/0 0.000 1.000 3
10.10.100.145 Down xe-0/3/1 0.000 1.000 3 PR1006809
•
Memory allocated in reference to the BFD session was not getting freed up. This resulted
in memory leak and the memory exhaustion triggered crash. PR1007432
Routing Protocols
•
When the IPv6 address on fxp0 is active during bootup, the joining of the all-router
group causes the kernel to create a ff02::2 route with a private next-hop, which is not
pushed to the Packet Forwarding Engine. When a non-fxp0 interface is active later,
the private next-hop will be shared by the non-fxp0 interface as well, resulting in packet
drops destined to ff02::2 on the non-management interface. - After this PR, the
advertising interface should be configured via the following CLI. [edit protocols] +
router-advertisement { + interface <interface_name>; + } PR824998
•
Performing CLI command "clear multicast bandwidth-admission interface <int>" on
64-bit Junos OS results the rpd process crash. The command should be used without
the interface qualifier on the impacted releases. PR949680
•
There are two receivers joined to same (S,G) and IGMP immediate-leave is configured.
When one of the receivers sends the leave message for (S,G), another receiver is not
receiving the traffic for 1-2 minutes. PR979936
•
In the P2MP environment with OSPF adjacency are established. One router's time is
set to earlier date than another router. OSPF adjacency might not come up when one
router goes down and comes up. PR991540
•
Bringing up DFWD based BFD sessions at scale causes a churn in DFW as a result of
which the FPC CPU usage remains at 100% for a prolonged timespan. PR992990
109Copyright © 2015, Juniper Networks, Inc.
Resolved Issues