Specifications

•
The rpd process might crash when executing the command "show route
advertising-protocol bgp <nbr>" without a table option, or with a table that is not
advertised by BGP. PR959535
•
In the scenario of multicast receiver could receive traffic from mLDP or PIM, if at first
the multicast traffic is flowing over PIM, then the flapping of PIM protocol will cause
the traffic to flow over mLDP and later switch back to PIM, but the mLDP
forwarding-cache might not get pruned, which resulting duplicated traffic. PR963031
•
In certain rare circumstances, BGP NSR replication to the backup Routing Engine may
not make forward progress. This was due to an issue where an internal buffer was not
correctly cleared in rare circumstances when the backup Routing Engine was
experiencing high CPU. PR975012
•
In scaled BGP environment, if an NSR enabled router does not have any routing-instance
configured, after flapping BGP groups with multiple peers, some BGP neighbors might
get stuck in 'not advertising' state. PR978183
•
In the dual Routing Engine scenario, after an Routing Engine switchover, the periodic
packet management daemon (ppmd) might exit. PR979541
•
On MX Series platforms with IGMP snooping enabled on an IRB interface, some transit
TCP packets may be wrongly considered as IGMP packets, causing packets to be
dropped. PR979671
•
Due to some corner cases, certain commits could cause the input and/or output BGP
policies to be reexamined causing an increase in rpd CPU utilization PR979971
•
PPMD filter is not programmed properly which is resulting Routing Engine to absorb
BFD packets instead of Packet Forwarding Engine. PR985035
•
In Junos OS, by default the RIP protocol "send" option is set to Multicast RIPv2. When
this "send" option is changed from "multicast"(active) to "none"(passive) or vice-versa,
rpd core might be seen on the router. PR986444
•
In V4 RG, member site receives traffic from both serving sites for few sources upon
withdraw/inject routes for 30 seconds. PR988561
•
OSPF adjacency is not coming up with error "OSPF packet ignored: authentication
failure (sequence error)" in p2mp when remote peer goes down. PR991540
Services Applications
•
Any SIP MESSAGE request will be dropped by the SIP ALG, this type of request is
unsupported from day one. This is rare type of request which will not prevent more
usual SIP operations such as voice calls, but it may affect some instant messaging
applications based on SIP. PR881813
•
Clearing the stateful firewall subscriber analysis causes the active subscriber count to
display a very huge number. The large number is seen because when a subscriber times
out the number of active subscribers is decremented. If it is set to zero using the clear
command, then a decrement would give an incorrect result. There is no impact to the
overall functionality and the fix is expected to be present in 14.1R2. PR939832
•
Ping failure from LNS to MLPPP client. PR952708
123Copyright © 2015, Juniper Networks, Inc.
Resolved Issues