Specifications

Routing Protocols
•
Prefixes that are marked with two or more route target communities (matching multiple
configured targets configured in policies) will be using more CPU resources. The time
it takes to process this kind of prefixes depends on the number of VRFs and the number
of routes that are sharing this particularity. This can lead to prolonged CPU utilization
in rpd. PR895194
•
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
•
When all the below conditions are met, if the knob "path-selection
always-compare-med" is configured, the rpd process might crash. - routing-instance
(VR, VRF) with no BGP configuration - rib-group in default instance with
routing-instance.inet.0 as secondary-rib - rib-group applied to BGP in default instance
- BGP routes from master tables (inet.0) leaked to the routing-instance table
(routing-instance.inet.0). PR995586
•
In the multicast environment, in rare condition, after graceful Routing Engine switchover
(GRES) is executed, the rpd process might crash due to receiving NULL incoming logical
interface. PR999085
•
Abnormal ip6 route-calculation behavior can be seen when ospf3-te-shortcut is
configured. PR1006951
•
When the same PIM RP address is learnt in multiple VRFs, with NSR configured, rpd
on the backup Routing Engine may crash due memory corruption by the PIM module.
PR1008578
•
When inet.3/inet6.3 is not enabled, BGP group uses inet6.0 table to advertise the
routes for both inet6 unicast and inet6 labeled-unicast families. When BGP family is
changed, BGP sessions re-establish. When BGP starts to advertise routes to the peer,
BGP expects to see route label however if the old inet6 unicast routes are still present
(not completely cleaned), then rpd process crashes. The fix is to separate BGP group
for inet6 unicast with inet6 labeled-unicast with same rib. The old peers are cleaned
up in the old group and new peers are established in new group. Thus, new peer
establishment is not delayed by the cleanup of the old peer. PR1011034
•
IS-IS router table MIB issues, when we do "show snmp mib walk
isisRouterHostName/isisRouterTable" we were not getting exact hostname as it is in
"show isis hostname" so the actual implementation was not as per RFC-4444, because
it was showing only the hostnames of the devices which are immediate neighbors of
Dut. Added level info to get sysis_entry per each level correctly and filled
data(isisRouterTable) correctly. PR1011208
•
Under certain sequence of events RPD can assert after a RPD_RV_SESSIONDOWN
event. PR1013583
•
With multicast discard route present, if a RP router has no pd- interface, it might not
generate (S,G) join to upstream when receiving MSDP source active (SA) message.
PR1014145
•
When receiving open message with any capability after the "add-path" capability from
BGP peer, the session will be bounced. PR1016736
99Copyright © 2015, Juniper Networks, Inc.
Resolved Issues