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 a remote PE's address is configured on a local loopback interface, the MVPN
PIM neighborship to that PE in a different VRF might be affected. [PR/558584]
On MX960 routers with PWR-MX960-4100-AC PEMs (high capacity AC PEMs), the
MPCs and DPCs do not power up when the system boots with only HC-AC PEM2,PEM3
being switched on, and PEM0,PEM1 being present but switched off. [PR/562125]
Layer 2 Ethernet Services
On MX Series routers, when both the top and bottom fan trays are enhanced and a
mastership switch is performed, the alarm "craftd[1337]: Minor alarm set, Mix of
FAN-TRAYS" displays. This only occurs after a switchover or an upgrade. This alarm
is temporary, is cleared within a few seconds, and does not cause any routing or
forwarding issues on the chassis. [PR/541617: This issue has been resolved.]
The AE interface does not show the system identifier for the attached interfaces in
actor role. Because of this, the AE interface gets stuck in the detached state after it is
rebooted from both ends. Additionally, the AE interface flaps when the backup Routing
Engine is rebooted and a graceful Routing Engine switchover (GRES) is performed.
[PR/547739: This issue has been resolved.]
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.]
71
Advertisement
Table of Contents
