Specifications

command "show route advertising-protocol bgp <peer-addr>" might crash the routing
protocol process (rpd). This is very corner issue and hardly to be experienced.
PR1028390
•
When BGP is doing path selection with default behavior, soft-asserts requests are
introduced. If BGP routes flap a lot, it needs to do path selection frequently, because
of which a great deal soft-asserts might be produced which will cause unnecessary
high CPU and some service issues, such as SNMP can not respond and even rpd core.
PR1030272
•
When "clear bfd session" is issued immediately (before the Poll - Final sequence is
completed) post config check-in for interval change from higher to lower
minimum-interval value, BFD sessions don't revert to lower interval. PR1033231
•
Issue in populating isisRouterTable values. Some entries are not filled correctly. This
does not block/affect the functionality of ISIS or other components. PR1040234
•
If labeled BGP routes are leaked from inet.3 table to inet.0, then activation of BGP
"add-path" feature might crash the routing protocol process (rpd). PR1044221
•
BFD session might reset on commit if version is configured. The adaptive RX interval
gets set to 0 which results in the reset. A sample configuration of BFD version is as
follows: protocols { bgp { bfd-liveness-detection { version 1; minimum-interval 1000;
transmit-interval { minimum-interval 1000; } } } PR1045037
•
When BGP and ICCP are the client of the same multi-hop BFD session, BFD runs in
centralized (non-distributed) mode. But if nonstop-routing configuration is added and
enabled, running mode of BFD is changed to distributed mode. This behavior is incorrect
but it would not affect to protocols which is client of the BFD session. However, if
Routing Engine switchover is performed after enabling NSR, the BFD session will get
unstable and all the client protocols also get unstable. PR1046755
•
Junos OS Multicast Source Discovery Protocol (MSDP) implementation is closing an
established MSDP session and underlying TCP session on reception of source-active
TLV from the peer when this source-active TLV have an "Entry Count" field of zero.
"Entry Count" is a field within SA message which defines how many source/group
tuples are present within SA message. PR1052381
•
The BGP session sending add-path prefixes can cause an rpd crash when the add-path
IDs that it allocates roll over from 65535 to 0. If the routes contributing add-path
prefixes are changing, the allocated path-id can eventually reach this value. This fix
changes the allocation scheme to always use the lowest available free path-id, so a
rollover will never occur. PR1053339
•
After multicast traffic source incoming interface and source ip RPF (reverse path
forwarding) route switching to a different interface, the multicast route cache upstream
interface might not be refreshed to be in sync with the pim join upstream interface.
This is incorrect and will cause packet blackhole for the affected multicast stream.
PR1057023
•
RPD cored at isisSysLevelTable_next function when we do snmpwalk/snmpget with
invalid value in snmp data variable part. With this fix,added sanity checks for those
OIDs that do not have checks in earlier versions. PR1060485
Copyright © 2015, Juniper Networks, Inc.88
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series