Juniper JUNOS OS 10.4 - RELEASE NOTES REV 5 Release Note page 65

Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
The statistics get for LSQ interfaces fails in a scaled LSQ configuration when the
interfaces queue lsq-w/x/y:z
resolved.]
When MLPPP interfaces of an MS-PIC are taken offline, the following syslog message
displays: "RT: itable unset idx 372 to proto MLPPP iftable failed (Invalid arguments)
on FE -1." [PR/528649: This issue has been resolved.]
In Junos OS Release 10.0 and later, a significantly large number of the following
messages appear on the MX960 and SRX5800 routers:
MX960 /kernel: PCF8584(WR): transmit failure on byte 1
MX960 /kernel: PCF8584(WR): (i2c_s1=0x80, group=0xe, device=0x54)
MX960 /kernel: PCF8584(WR): busy at start, attempting to clear
MX960 /kernel: PCF8584(WR): (i2c_s1=0x00, group=0xe, device=0x54)
MX960 /kernel: PCF8584(RD): ack failure on 2nd last byte
These messages are not an indication of a fan failure. They are cosmetic and can be
ignored. [PR/531253: This issue has been resolved.]
On Trio MPCs, multiple changes to a single term in quick succession results in an
incorrect filter state in the Packet Forwarding Engine. This causes the MPC to crash.
[PR/532791: This issue has been resolved.]
An XE circuit on the MPC-3D-16XGE-SFPP might cause a high CPU utilization on the
MPC. [PR/535057: This issue has been resolved.]
On MX960 routers, the link status stays in the "Link ok" state when the SCB is removed
without taking it offline using the CLI or switch. [PR/536860: This issue has been
resolved.]
The SCB displays an incorrect state when it is removed without taking it offline using
the CLI or buttons. This is not a cosmetic error and might impact the traffic.
[PR/536866: This issue has been resolved.]
The "frame-relay-ether-type" encapsulation is not programmed to the hardware
properly. Because of this, the incoming packet parsing fails and the packets are
discarded. [PR/539484: This issue has been resolved.]
On MX Series routers with 10.x Power Budget, after a "Power Budget: Chassis
experiencing power shortage" alarm occurs, the alarm does not clear even after the
power budget problem is cleared. [PR/540522: This issue has been resolved.]
The MX-MPC1-3D-Q accepts VLAN tagged packets even when the interface is not
configured with VLAN tagging. [PR/540620: This issue has been resolved.]
The link-up time on a 16x 10-Gigabit Ethernet MPC is not less than the other platforms
(ADPC and other MPCs) due to the emission dispersion compensation (EDC)
functionality of the PHY device on the MPC. This causes a delay of 50 mS to 150 mS
and cannot be changed. [PR/540694: This issue has been resolved.]
The
sonet-options raise-rdi-on-rei
the option on and off again requires the
raise-rdi-on-rei
to assert or clear the RDI-L alarm. As a workaround, when both
and
raise-rdi-on-rei trigger
[PR/540745: This issue has been resolved.]
command is executed. [PR/523260: This issue has been
and options do not work well together. Turning
trigger
options are configured, flap the
show
option to flap in order
trigger
sonet-options
trigger as well.
sonet-options
65