Specifications

•
When node-protection is enabled for a specified LSP and optimize-timer for a
node-protecting bypass LSP is configured on router, the bypass route might
get-optimized in such a way that it traverses through the very node that the bypass is
trying to protect during re-optimization. As a consequence, the node-protecting bypass
LSP only provide link protection instead of node protection. PR1045055
•
On M/MX/T Series routers, dynamic-rsvp-lsp is configured under interface
link-protection hierarchy level. After interface flap, the bypass LSP does not come up.
PR1054155
Multicast
•
In multicast environment, if GRES is performed immediately after a routing-instance
being deleted, the krt (kernel routing table) queue might get stuck after adding back
the routing-instances which were deleted. PR1001122
Network Management and Monitoring
•
Mib2d cores while trying to re-add a lag child into the internal DB. Since the entry is
already present in the internal DB. Before adding the child link, mib2d does a lookup
on the tree, to know if the entry is not already there. However, this lookup returns no
results, since the child link is part of snmp filter-interface configuration. PR1039508
•
SNMP mib walk jnxMac does not return value with et- interfaces on
MPC3/MPC4/MPC5/MPC6. PR1051960
•
There is no specific counter name in the MIB2D_COUNTER_DECREASING syslog
message. PR1061225
Platform and Infrastructure
•
With inline jflow enabled, if the low 12 bits of the packet counter are zero (0x000)
while copying packets count from hash record into flow export packet, the
packetDeltaCount counter might be incorrect in inline jflow records. There is no traffic
impact but may impact billing. PR886222
•
For inline BFD over aggregated Ethernet (AE) interface which member links are hosted
on different FPCs, BFD packets coming on ingress line card will be steered to anchor
Packet Forwarding Engine through fabric. If FPC reconnects to master Routing Engine
(such as Routing Engine switchover operation), the inline BFD session punts the BFD
packet to host, the BFD packet should go through loopback interface filter of VRF on
which it is received. But in this case, the BFD packet might hit the wrong loopback
interface filter from wrong routing-instance since the VRF information is not carried
across fabric. PR993882
•
BFD session within default routing-instance are not coming up once inline-services pic
is configured and fixed class-of-service forwarding-class is assigned. BFD session
operating in no-delegate-processing are not affected. PR999647
•
On MX Series platform with scaled set-up, after deactivate/activate or renaming a
bridge domain (BD) which has irb interface associated, the IGMP snooping configured
under the BD might not work any more. Note it happens only when the router is in
"network-services enhanced-ip" mode. PR1024613
Copyright © 2015, Juniper Networks, Inc.86
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series