
•
BMP is not sending a correctly formatted prefix for inet/inet6 labeled unicast BGP
family routes. This occurs if the route resides in the inet[6].0 table, and not if the route
resides in the inet[6].3 table. PR996374
•
There are two scenarios that the rpd might crash. The first scenario is when all BGP
peers flap with /jointfilesconvert/293395/bgp route target proxy configured. The second scenario is when BGP
session is configured in a way that one side is configured with family l2vpn
auto-discovery-only, while on the other side is configured with both family l2vpn
signaling and keep all knobs. PR1002190
•
When IS-IS is configured for traffic engineer (TE), after remove family mpls from the
interface and remove the specific interface from [edit protocols rsvp] and [edit
protocols mpls] hierarchy level, corresponding link is not removed from the TED as
expected. PR1003159
•
When there are more than 65535 "flow-spec" routes existing in the routing table, the
rpd process might crash because it exceeds the current maximum supportable scaling
numbers (Current scaling numbers are in the range of 10K~16K). PR1004575
•
During unified in-service software upgrade (ISSU), when a Bidirectional Forwarding
Detection (BFD) session negotiation is happening, if the session is configured with 10
seconds or higher interval, BFD session would flap. PR1010161
•
Misconfiguring BGP route validation session to the router itself might lead to rpd process
crash. PR1010216
•
In scaled BFD scenarios, BFD unified ISSU poll negotiation will fail causing the BFD
session to flap during unified ISSU. PR1012859
•
Multicast packets might get dropped with NSR configured and graceful switchover of
the Routing Engine is performed. PR1020459
Services Applications
•
On MX240/480/960 routers with MS-DPC with "deterministic-port-block-allocation
block-size" configuration. In rare condition, when the "block-size" is set to a larger value
(in this case, block-size=16128), the Services PIC might crash. PR994107
•
jflow-logging: seen "mspmand.core.ms41.0.gz*" with data traffic. PR994256
•
The redundant services PIC (rsp-) interfaces or redundant Multiservices (rms-)
interfaces configured with "hot-standby" mode might flap upon committing any
configuration change (will happen for even an unrelated interface description change).
PR1000591
•
The following messages are being logged at ERR not DEBUG severity: mspd[3618]:
mspd: No member config mspd[3618]: mspd: Building package info This PR sets the
correct severity. PR1003640
Copyright © 2015, Juniper Networks, Inc.110
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series
Comentários a estes Manuais