Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
58
"D4P-10/1: FROML tx48 stream 1 data path stuck". To resolve this issue, purge the D4P
buffer. [PR/424326: This issue has been resolved.]
The queue counter of the aggregated Ethernet is counted up after the statistics are
cleared and the FPC is restarted. [PR/528027: This issue has been resolved.]
On an MX Series router with a mixed MPC and DPC environment, first and non first cell
drops occur at the DPC. [PR/540283: This issue has been resolved.]
When a large OID registration traffic exists from the sub agent to the master agent,
the registration packets encounter random errors during transmission. This affects the
registration process. [PR/555345: This issue has been resolved.]
When a member link is added to an existing aggregated interface, a multicast
distribution tree (MDT) mismatch might occur among the FPCs. This issue occurs only
when graceful Routing Engine switchover (GRES) is enabled. [PR/558745: This issue
has been resolved.]
A Layer 2 instability and rapid VRRP mastership change might cause
MPC-3D-16XGE-SFPP to restart. [PR/560716: This issue has been resolved.]
When a MAC is moved, the resulting flush process might be interrupted when the list
is processed. [PR/560730: This issue has been resolved.]
If the cable of a TX router is removed from the interface on an MIC-3D-20GE-SFP, the
state of the interface remains in the "up up" state. [PR/561254: This issue has been
resolved.]
When multiple physical interfaces exist in a 4xChDS3 PIC, errors might occur when
each controller physical interface is deleted while the PIC is taken offline. [PR/561841:
This issue has been resolved.]
When a change in the bridge domain membership occurs, and the bridge domain has
an IRB interface and a vt-x/y/z interface, the Packet Forwarding Engine that does not
have any local interfaces on that bridge domain might restart. [PR/566878: This issue
has been resolved.]
When the chassisd process receives a temporary error code (such as Device Busy, Try
Again, No Buffer Space, or No Memory), while trying to add both the PIC and physical
interfaces present in the PIC to the kernel, the chassisd process may not retry adding
the physical interface back to the kernel until it succeeds. The device or physical
interface will not come back up. It is recommended to reboot the router or restart the
FPC when this issue is encountered. [PR/570206: This issue has been resolved.]
On TX Matrix Plus routers, the
flooding. [PR/571270: This issue has been resolved.]
On any Junos OS device that supports Ethernet OAM, the cfmd process might crash
when a malformed delay measurement message (DMM) is received. [PR/571673: This
issue has been resolved.]
command might cause an FPM interrupt
set craft-lockout
Copyright © 2011, Juniper Networks, Inc.
Advertisement
Table of Contents
