Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 58

JUNOS OS 10.4 Release Notes
58
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.]
With Junos OS Release 10.2 and later, when a logical interface on an ATM-II IQ PIC is
disabled, the FPC is taken offline and brought back online, and the PIC is reenabled,
the logical interface stays down with atm_maker_check_indq error messages.
[PR/541688: This issue has been resolved.]
When a Gigabit Ethernet or an XE interface on IQ2 PICs is disabled, and the link status
is up, the traffic received from the interface might still be forwarded. [PR/543388: This
issue has been resolved.]
When neither the per-unit scheduler nor the hierarchical-scheduler is configured on a
physical interface and the physical interface has the overhead-accounting bytes
configured, it does not take effect. [PR/544608: This issue has been resolved.]
and options do not work well together. Turning
trigger
options are configured, flap the
option to flap in order
trigger
sonet-options
trigger as well.
sonet-options
Copyright © 2010, Juniper Networks, Inc.