Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
Layer 2 Ethernet Services
The PIM neighborship does not appear over the IRB interface after the dense port
concentrator (DPC) is restarted. [PR/559101: This issue has been resolved.]
MPLS Applications
Under certain circumstances, the routing protocol process might crash when
configuration changes are made to label-switched paths under the
hierarchy level. [PR/550699: This issue has been resolved.]
When the
no-decrement-ttl
[edit protocols mpls label-switched-path path-name]
TTL action
field in the output of the
as the action. This is a display issue only and has no operational
vrf-propagate-ttl
impact on the forwarding behavior. This is relevant to Layer 3 VPN scenarios where
BGP routes resolve over RSVP LSPs and the
configured at the
[edit protocols mpls]
been resolved.]
A point-to-multipoint LSP with bandwidth requirement might fail to retrace the original
path after a graceful restart, and might not come up until the end of the recovery period.
[PR/574308: This issue has been resolved.]
Network Management
SNMP might stop working after a router reboot, a DPC, FPC, or MPC restart, or a graceful
Routing Engine switchover. [PR/525002: This issue has been resolved.]
Platform and Infrastructure
Under certain circumstances, the message "NH: Failed to find nh (xxxx) for deletion"
appears for the child links of an aggregate interface. However, this message should
appear only when the child next hop is not found. This message is only cosmetic.
[PR/494528: This issue has been resolved.]
In a Layer 2 circuit setup with a link services intelligent queuing interface (LSQ) in the
core, and the control-word option enabled, a ping between two CE interfaces fails. As
a workaround, use the no-control-word option. [PR/551207]
• 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
command), or on multichassis platforms (TX and TXP routers),
graceful-switchover
statement is included at the
hierarchy level, the
show route extensive
no-propagate-ttl
hierarchy level. [PR/563505: This issue has
set chassis redundancy
[edit protocol mpls]
or the
[edit protocols mpls]
VPN Label
command displays
statement is not
59
Advertisement
Table of Contents
