■
When an aggregated SONET with a Cisco High-Level Data Link Control (HDLC)
encapsulation is configured, a member link may not be marked as linkdown in
the Packet Forwarding Engine if the remote end of the link is disabled.
[PR/472677: This issue has been resolved.]
■
The output of the
show arp
command does not show the entire demux interface
identifier, making it difficult to determine with which specific demux subinterface
a given ARP entry is associated. [PR/482008: This issue has been resolved.]
■
If a duplicate IPv6 address is configured, every ICMP6 packet received (icmp
request, icmp neighbor solicitation, or icmp neighbor advertisement) will trigger
an mbuf leak. Such a duplicate address configuration might not get noticed at
the VRRP backup router which is not used for data forwarding. Correcting the
configuration and deactivating or activating the interface will stop the mbuf leak.
[PR/482202: This issue has been resolved.]
■
The fxp0 packet counter statistics are inconsistent between the physical interface
and the logical interface as the statistics are updated twice. [PR/486200: This
issue has been resolved.]
■
Jtree corruption may be observed when the DCU is configured on ES-FPCs.
[PR/486782: This issue has been resolved.]
■
A problem occurs on an M120 router with an FEB redundancy configuration
when the backup FEB is protecting a non-primary FEB. In this case, the Routing
Engine will prompt the incorrect Packet Forwarding Engine for status, causing
delays in the SNMP responses. [PR/490172: This issue has been resolved.]
■
An issue occurs when one or more multicast routes (i.e., one or more <S,G>
s) have received joins over an AE interface represented by two (or more) AE legs
on separate Packet Forwarding Engines. In a Packet Forwarding Engine ASIC
forwarding, the next hop shared by these multicast routes contains a list
representing the two (or more) Packet Forwarding Engines. When this next hop
list is no longer referenced by any active multicast route, it is not correctly freed
and remains stranded in the Packet Forwarding Engine ASIC memory. This issue
does not occur when the AE legs are all on the same Packet Forwarding Engine.
[PR/494246: This issue has been resolved.]
■
Due to excessive logging at the FPC, the E3 FPC Type 3 core dumps multiple
times. [PR/494534: This issue has been resolved.]
■
In certain cases, a configuration change can cause the backup Routing Engine
to reboot. [PR/497290: This issue has been resolved.]
■
On T Series routers with ES-FPCs, removing or adding flow-tap filters may trigger
an FPC reboot. However, the other FPC types in the same system are not affected.
[PR/499233: This issue has been resolved.]
■
When a next-hop chain has multiple types of next-hop dependencies, including
indirect next-hop, aggregate next-hop, and multiple unicast next-hops, during
an aggregate link flap (down/up), a certain sequence of events from the kernel
is expected by the Packet Forwarding Engine for the next-hop change and delete
updates. However, during a quick link flap (down/up), in an extreme corner case,
the Packet Forwarding Engine does not receive the expected sequence, and the
FPC will crash. [PR/499315: This issue has been resolved.]
■
On IQ2 PICs, when copy-plp is enabled under class of service, the DCU provides
the wrong statistics. [PR/499378: This issue has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
81
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
