Specifications

General Routing
•
"show services accounting usage" does not populate cpu utilization for XLP based
cards . Please use "show services service-sets cpu-usage". PR864104
•
Leak in /mfs/var/sdb/iflstatsDB.db. PR924761
•
In this scenario the CPCD (captive-portal-content-delivery) is configured for
HTTP-REDIRECT for Subscriber Management clients using MS-DPC. When services
sessions start to redirect the HTTP traffic, the memory-usage consistently increments
for MSPMAND on the multi-service PIC. The memory limit then might cause packets
loss. PR954079
•
MPLS traceroute causes "rttable-mismatch" syslog messages. PR960493
•
On MX Series DPC line cards with redundancy System Control Boards (SCBs), when
active SCB goes down ungracefully by unexpected event (such as turn off Power Entry
Modules (PEMs)), traffic loss is observed and cannot be recovered on standby SCB
as expected. PR961241
•
In the dual Routing Engines scenario with large scale nexthops (in this case, more than
1-million nexthops and around 8K VRFs). In rare condition, kernel might crash on backup
and/or master Routing Engine due to exhaustion of nexthop index space. PR976117
•
1) Due to a previous fix chassisd on the protocol master Routing Engine and the protocol
backup Routing Engine connect to the main snmpd on the protocol master using the
following methods. a) Chassisd on the protocol master Routing Engine connects using
a local socket since snmpd is running locally. b) Chassisd on the protocol backup
Routing Engine connects using a TNP socket since snmpd is not local. 2) However this
fix changed the way the other daemons connect to snmpd. All important daemons
run on the protocol master and should connect to snmpd using a local socket. However
the fix changed it so that all daemons that ran on the protocol master (other than
chassisd) tried to connect using the TNP socket. SNMPD does not accept these
connections. As a fix, in an MX-VC, we made sure that chassisd connects to all processes
which run on the protocol master using internal socket while the chassisd process on
the protocol backup and protocol lincecard connect connect using TNP socket.
PR986009
•
In the dual Routing Engines scenario, in rare condition, while executing GRES and
deleting interfaces at the same time, it is possible that a nexthop delete message is
not sent to rpd process, causing rpd to keep a nexthop index (NHID) that kernel has
already deleted. Later when kernel allocates this NHID for next new nexthop and sends
it to rpd process, rpd process might crash due to duplicate NHID. PR987102
•
MX 960/480/240 fantray red alarm temp changed from 75C to 80C. PR995225
•
In the dual Routing Engines scenario with NSR configuration, backup peer proxy thread
is hogging CPU for more than 1 second if there are multiple updates (>5000) going
from master Routing Engine to backup Routing Engine. This is leading to FPC socket
disconnections. The traffic forwarding might be affected. PR996720
•
By default, the syslog utility exports 800,000 logs per second to a remote syslog server.
You can modify the number of syslogs to be sent by including the message-rate-limit
statement at the [edit interfaces interface-name services-options syslog] hierarchy
91Copyright © 2015, Juniper Networks, Inc.
Resolved Issues