Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 49

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
Forwarding and Sampling
A high CPU utilization by the DFWD process might occur if the interface lo0 is configured
as part of the interface group 0. [PR/497242]
On a sampled traffic on a multi services PIC, the multicast convergence slows down
with the message "RPD_KRT_Q_RETRIES: Indirect Next Hop Update: No buffer space
available." [PR/554363]
Making any circuit cross-connect (CCC) filter changes might render the Packet
Forwarding Engine busy which might cause a slow statistics response. [PR/554722]
When a loopback filter is configured, packets sent by the ASIC to the Packet Forwarding
Engine's CPU for generation of TTL expiry notification are dropped. [PR/555028]
In Junos OS Release 10.2 and above, the Packet Forwarding Engine process tracing is
enabled by default. This results in the MIB2D process not being able to communicate
with the Packet Forwarding Engine process. [PR/566681]
When a firewall filter with multiple terms references the same three color policer and
has the same count variable configured, any IP packets that match the second or later
terms might get corrupted. Use different count variables in each term to prevent this
issue. [PR/567546]
High Availability
The SSH keys are not in sync between the master and backup Routing Engine when
SSH is enabled after a graceful Routing Engine switchover (GRES). [PR/455062]
When a container interface (used in AE interfaces) is freed in the memory, the child
nexthop (member link) on the master Routing Engine is also freed. However, in some
cases, the child nexthop on the backup Routing Engine is not freed resulting in a crash.
[PR/562295]
Interfaces and Chassis
When the Rx power level is a negative value, the SFP diagnostics output displays an
invalid receiver power level reading. [PR/235771]
When an ATM II interface is configured as a Layer 2 circuit with cell transport mode on
a router running Junos OS Release 8.2 or lower, interoperability issues with other network
equipment and another Juniper Networks routers running Junos OS Release 8.3 or
higher might occur. [PR/255622]
Upon a link up event, old packets from the previous link down are still dequeued. This
leads to huge latency reports. [PR/515842]
Discrepancies exist in MAC and filter statistics between Trio MPC and I+EZ DPCs.
[PR/517926]
The queue counter of the aggregated Ethernet is counted up after the statistics are
cleared and the FPC is restarted. [PR/528027]
The
multipoint-destination
the configuration of this statement is accepted without problems initially, subsequent
reconfiguration of the interface might cause the FPC and Packet Forwarding Engine
to reboot. [PR/529423]
configuration statement is not supported on IQE PICs. While
49