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
When the chassisd process receives a temporary error code (such as Device Busy, Try
Again, No Buffer Space, or No Memory), while trying to add both the PIC and physical
interfaces present in the PIC to the kernel, the chassisd process may not retry adding
the physical interface back to the kernel until it succeeds. The device or physical
interface will not recover. It is recommended to restart the router or the FPC when this
issue is encountered. [PR/570206: This issue has been resolved.]
On TX Matrix Plus routers, the
flooding. [PR/571270: This issue has been resolved.]
On any Junos OS device that supports Ethernet OAM, the cfmd process might crash
when a malformed delay measurement message (DMM) is received. [PR/571673: This
issue has been resolved.]
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 at the
hierarchy level. [PR/550699: This issue has been resolved.]
When the
no-decrement-ttl
[edit protocols mpls label-switched-path path-name]
field in the output of the
TTL action
vrf-propagate-ttl
as the action. This is a display issue only and has no operational
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, a DPC, an FPC, or an MPC is restarted, or after
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
As a workaround, use the
resolved.]
set craft-lockout
command might cause an FPM interrupt
statement is included at the
show route extensive
no-propagate-ttl
hierarchy level. [PR/563505: This issue has
option is enabled, a ping between two CE interfaces fails.
option. [PR/551207: This issue has been
no-control-word
[edit protocol mpls]
[edit protocols mpls]
or the
hierarchy level, the
VPN Label
command displays
statement is not
63
Advertisement
Table of Contents
