Table of Contents
Advertisement
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
If there is enough join state associated with a neighbor and that neighbor goes down
and comes back up quickly, then that join state may be stranded in an unresolved state
until the
command is issued. [PR/539962: This issue has been resolved.]
clear pim join
On Type 2 Trio MPC, multiple changes to a single term in quick succession can cause
an incorrect filter state in the Packet Forwarding Engine. This causes the MPC to crash.
[PR/540674: This issue has been resolved.]
The routing protocol process might crash when a BGP connection attempt meets with
an RST from the peer. This is due to an unlikely race condition. [PR/540895: This issue
has been resolved.]
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
command
show pim interfaces
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.]
Copyright © 2011, Juniper Networks, Inc.
71
Advertisement
Table of Contents
