Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 60

JUNOS OS 10.4 Release Notes
60
The DHCP relay bindings remain in a release state with a negative lease time.
[PR/549520: This issue has been resolved.]
The L2CPD might have a memory leak when LLDP is enabled. [PR/549531: This issue
has been resolved.]
MPLS Applications
With BFD enabled over IGP and an RSVP session built across it, when the RSVP peer
does not support RSVP Hello (or is disabled), the BFD session down event triggers
only the IGP neighbor to go down. The RSVP session remains up until a session timeout
occurs. [PR/302921: This issue has been resolved.]
The rlist entry corresponding to the previously existing rlist is not removed, which causes
the routing protocol process to crash. [PR/513160: This issue has been resolved.]
When a protected link flaps, certain RSVP routes do not lose association with the
p2mp_nh. [PR/530750: This issue has been resolved.]
Under NGEN-MVPN with vrf-table-label configured on the provider edge, the provider
router connecting to that provider edge might keep an old P2MP MPLS label entry
upon label-switched path optimization or reroute. There is no workaround. [PR/538144:
This issue has been resolved.]
An LSP with auto-bw might stay down for approximately 30 minutes after a Routing
Engine switchover or a Routing Engine restart when graceful restart fails. As a
workaround, disable and reenable the MPLS or OSPF stanza. [PR/539524: This issue
has been resolved.]
When RSVP path-mtu allow-fragmentation is configured, traffic redirection away from
its intended destination might occur. [PR/544365: This issue has been resolved.]
On a P2MP LSP setup, the routing protocol process of the transit router might core
when the topology changes with respect to the ingress sub-LSP router. There is no
workaround. [PR/549778: This issue has been resolved.]
In Junos OS Release 10.2, when the
at the ingress router, the updated Maximum AvgBW Utilization field displays a value
that is much higher than the actual bandwidth. [PR/550289: This issue has been
resolved.]
On MX80 routers, the MPLS LSP statistics do not record the transit traffic on a
single-hop LSP with an implicit NULL label. [PR/551124: This issue has been resolved.]
When a large number of P2MP LSPs exist during periods of high network instability
with many links flapping, and MBB re-routing of a P2MP LSP occurs, an MPLS route
can become stale. This can cause a routing protocol process assertion failure on a
transit router. [PR/555219: This issue has been resolved.]
clear mpls lsp autobandwidth
Copyright © 2010, Juniper Networks, Inc.
command is executed