Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 64

JUNOS OS 10.4 Release Notes
64
Under certain timing conditions, an interior gateway protocol topology change can
result in the BGP routes referencing an incorrect egress interface. This problem can
occur when active and inactive BGP routes are learned from the same peer and the
inactive BGP routes are deleted at the time of the topology change. [PR/543911: This
issue has been resolved.]
In instances with scaled LACP configurations, the periodic packet management process
(ppmd) might experience memory leaks. [PR/547484: This issue has been resolved.]
When two identical local interface addresses are shared between two VRFs via
auto-export, the routing protocol process might cause a high CPU utilization.
[PR/547897: This issue has been resolved.]
When the primary loopback address changes, the routing protocol process might crash
when a new data mdt is created. [PR/549483: This issue has been resolved.]
If a PIM <S, G> join arrives when there is no route to the source, PIM RPF checking is
disabled, and a matching multicast route is present, the output interfaces associated
with the PIM <S, G> join are not added to the multicast route. [PR/550703: This issue
has been resolved.]
The IPv6 entries are removed from the output of the
when the corresponding interface is in the down state. This is a cosmetic issue.
[PR/550799: This issue has been resolved.]
On MX80 routers, even when static routes are configured, the management port does
not forward traffic to the user ports. [PR/552952: This issue has been resolved.]
When an interface-based IPv6 BGP session with a 2-byte AS format is used, the system
might crash. [PR/553772: This issue has been resolved.]
An IS-IS adjacency flap at a precise interval can cause the routing protocol process to
restart on a neighbor, as it is in the process of purging the LSAs of the previously down
node from the local database. [PR/554233: This issue has been resolved.]
Services Applications
In Junos OS Release 10.0 and later, the routing instance name is restricted to 63
characters. [PR/533882: This issue has been resolved.]
The BGP_IPV4_NEXT_HOP field on the jflow v9 record matches the originator ID instead
of the BGP next hop. [PR/534598: This issue has been resolved.]
When traffic is forwarded in an L2TP session and a teardown request is received, the
ASPIC crashes with a memory access violation in mlppp_output. [PR/537225: This
issue has been resolved.]
On M Series routers configured for L2TP tunneling with several thousands of PPP
connections, when all the PPP sessions expire at the same time, the MS-PIC might
hang and become unusable. To recover the service, restart the PIC. [PR/541793: This
issue has been resolved.]
command
show pim interfaces
Copyright © 2010, Juniper Networks, Inc.