Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
60
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 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: 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 (DPC-x or MPC-3D-x) is configured to an existing aggregate
configuration, the newly added link information might not appear in the under the
LACP info:
,
LACP Statistics:
command. Deactivate and then activate the aggregate interface
interface aex extensive
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
(s,g)/(* ,g) entry is removed. [PR/551949: This issue has been resolved.]
On an NSR LDP, an LDP database entry mismatch exists between the master and the
backup Routing Engines. The backup Routing Engine does not replicate the LDP socket
with the error "jsr_sdrl_set_data: No space dlen." [PR/552945: This issue has been
resolved.]
When a default route target is sent by a BGP peer, th eBGP does not track the VPN
routes covered by this route target. When the default route target goes away, the BGP
does not withdraw the VPN routes that were previously covered by that default route
target. [PR/556432: This issue has been resolved.]
On a 3D MPC, the load balance might be broken when a BGP multipath is configured.
[PR/557099: This issue has been resolved.]
On M Series, MX Series, and T Series routers, the Virtual Router Redundancy Protocol
(VRRP) process might become unresponsive when processing is delegated to the
, and
Marker Statistics:
fields in the output of the
Copyright © 2011, Juniper Networks, Inc.
Link:,
show
Advertisement
Table of Contents
