Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
64
A DPC or an MPC may reset when Aggregate Ethernet (AE) interfaces are provisioned
with IRB. In some case, a DPC may also reset when a member link of an AE interface
flaps. [PR/559887: This issue has been resolved.]
With the IRB and AE interfaces in a bridge-domain, the old nexthop data is not cleared
from the Packet Forwarding Engines when they are updated. This causes the Packet
Forwarding Engine to crash when that nexthop is later referenced. [PR/560813: This
issue has been resolved.]
On an MX960 router, when an MPC is installed and OSPF and IS-IS is activated
simultaneously, the "jtree memory free using incorrect value 8 correct 0" message is
displayed for all DPCs. [PR/562719: This issue has been resolved.]
On standalone routers with GRES enabled (using the
graceful-switchover
command), or on multichassis platforms (TX and TXP routers),
FPCs can crash creating a core file when interfaces are moved from one aggregate
bundle to another aggregate bundle in a single configuration commit operation. As a
workaround, split the operation into two commits. Remove the interface from one
bundle and perform a commit, and later add it to another bundle and perform another
commit. [PR/563473: This issue has been resolved.]
The MPC might crash when multicast traffic is forwarded and interfaces are deactivated.
[PR/565454: This issue has been resolved.]
In Junos OS Release 10.2 and later, 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: This issue has been resolved.]
On MX Series routers running Junos OS Release 10.2 and later, when a new link from
a newly inserted FPC is configured to an existing aggregate configuration, the newly
added link information might not appear in the
Marker Statistics:
fields in the output of the
Deactivate and then activate the aggregate interface to resolve this issue. [PR/571245:
This issue has been resolved.]
Routing Protocols
In rare situations, the routing protocol process might restart due to a software validation
failure. [PR/476143: This issue has been resolved.]
With a large number of peers in a single BGP group, continuous large route churn may
trigger scheduler slips in the routing protocol process. [PR/544573: 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 a policy matching an extended community using a 4-byte AS and a wildcard is
configured, the match condition might fail to match the relevant communities. As a
workaround, configure exact matches. [PR/550539: This issue has been resolved.]
A rare race condition might cause the routing protocol process to crash when an
entry is removed. [PR/551949: This issue has been resolved.]
(s,g)/(*,g)
set chassis redundancy
,
Link:, LACP info:
LACP Statistics:
show interface aex extensive
Copyright © 2011, Juniper Networks, Inc.
, and
command.
Advertisement
Table of Contents
