Specifications

•
VRRP daemon (vrrpd) memory leak might be observed in "show system processes
extensive" when VRRP is set with routing-instance and then change any configuration.
PR1022400
•
On M120, when two type 1 FPCs are sharing the same FEB and they are both carrying
core facing interface, with vrf-table-label/no-tunnel-service configuration, the LSI
interfaces might be removed incorrect on a working FPC when the other is set to offline.
PR1027034
•
"set forwarding-options enhanced-hash-key symmetric" knob will not get applied on
MX104 Packet Forwarding Engine. PR1028931
•
If DPCE 20x 1GE + 2x 10GE X card is present in the chassis, BFD sessions over AE
interfaces may not be distributed PR1032604
•
Some duplicate entries are reported in jnx-chas-defines.mib. This patch removes the
duplicate entries to fix the issue. PR1036026
Layer 2 Features
•
After configuration change or convergence events, kernel may report ifl_index_alloc
failures for LSI interfaces and causing KRT queue ENOMEM issue, eventually preventing
new logical interfaces being added to the system. This condition always recovers on
its own once convergence is completed. PR997015
•
If "maintain-subscriber" knob is enabled on the router, DHCPv6 server/relay might be
unable to process any packet if deactivate and then activate the routing instance,
which means the subscribers can not get the IPv6 addresses. Please note, even with
the fix, the results of this scenario is also expected if with "maintain-subscriber" knob
enabled, please consider using the workaround to avoid this issue. PR1018131
•
After FPC restart, bridge domain (BD) implicit filters for Ethernet ring protection
switching (ERPS) might get reprogrammed with wrong logical interface index, which
causes ERPS to not work correctly. PR1021795
•
In a mixed VPLS instance where both LDP and BGP flavors are present with "best-site"
knob configured under "site" block, any cli change in that instance will result in rpd
crash. PR1025885
MPLS
•
When the size of a Routing Engine generated packet going over an MPLS LSP is larger
than MTU (i.e. MTU minus its header size) of an underlying interface, and the extra
bytes leading to IP-fragmentation is as small as <8 bytes, then that small-fragment
will be dropped by kernel and lead to packet drop with kernel message
"tag_attach_labels(): m_pullup() failed". For example - If SNMP Response with specific
size fall into above mentioned condition then small fragment will be dropped by kernel
and eventually the SNMP response will fail. PR1011548
•
In MPLS scenario with TX/TXP router acting as the transit node, performing MPLS LSP
ping or traceroute from ingress node might cause kernel crash on the transit node due
to improper timer initialization between SCC and LCC chassis. PR1020021
•
Ted link information of protocol from highest credibility level is used irrespective of the
level at which CSPF is computing. i.e., cspf-metric in "show mpls lsp extensive" would
95Copyright © 2015, Juniper Networks, Inc.
Resolved Issues