Specifications

command is configured prior to the upgrade. This PR reverses the above change and
allows hash-key command to be ignored on unsupported platforms: show configuration
forwarding-options ## ## Warning: configuration block ignored: unsupported platform
(mx80) ## hash-key { family inet { layer-3; } } PR1016339
•
In dynamic subscribers management environment with "maintain-subscriber" feature
enabled, when scaling up the logged in subscribers, the demux interface might not be
associated with the subscriber and "show auto-configuration extensive" CLI command
only print partial output. PR1017544
•
MAC accounting support was added for 40G and 100G interfaces on MPC3 and MPC4
cards. PR1017595
•
Traffic destined to the Broadcast or Network address of a Network Address Translation
(NAT) pool using the address prefix setting for the MS-MIC/MS-MPC card causes a
traffic loop that spikes the CPU. PR1019354
•
On a MX Series-based FPCs, when there are next-hop changes, the "heap 0" memory
of the FPC may experience memory leakage which will eventually causes memory
exhaustion. PR1019794
•
No performance or functional impact. Can be safely ignored. "Ignore the PTP message
(2) as this MPC doesn't support EEC" should be moved from notice to debug level.
PR1020161
•
When source address is configured under ms interface, and the service-set has syslog
host as local the FPC slot is printed as -ve. PR1020854
•
Trace file size is already limited to 1 Mega bytes, but the actual issue is different. When
file reaches its maximum allowed size, an attempt is made to rotate trace file. But
trace files count is presently set to 0 (default), so rotate is not functional. As a result
all logs are appended to the same trace file even after crossing max limit. PR1021076
•
MQCHIP(0) mqchip_get_q_forwarded_stats() invalid q_sys 0 q_num messages are
continously shows in logs.It will cause two GE or XGE interfaces to not forward traffic.
PR1021951
•
The host MPC might continuously crash when trying to online a faulty MS-MIC after
discovering the hardware failure. PR1026310
•
On MPC5E line card, if a firewall filter with large-scale terms (more than 1300 etc.) is
attached to an interface, traffic drop might be seen. PR1027516
•
For M320 or T Series FPCs (M320 non-E3 FPC and T Series non-FPC5) with queuing
PIC, if the configured total buffer size temporal values exceeds the supported maximum
scheduler buffer size for the PIC (e.g. For PD-5-10XGE-SFPP PIC, the maximum
temporal buffer size that can be configured for a scheduler is 40,000 microseconds),
the default scheduler [95,0,0,5] is applied instead of the default chassis scheduler
[25,25,25,25], which might result in the packet drops on Q1 and Q2. PR1027547
•
In a rare case, rdd core is reported under /usr/sbin/rdd as soon as applying the group
and commit is performed. PR1029810
•
On MX Series platform with MS-MPC card, after performing switchover from master
RE0 to backup RE1, 2 internal ARP entries for Routing Engine address (128.0.0.1) on
93Copyright © 2015, Juniper Networks, Inc.
Resolved Issues