Platform and Infrastructure
■
The output of the
show route forwarding-table family vpls multicast
command may
display an unexpected output such as “rtinfo” with the multicast statement
because this statement is supported only with inet and inet6 families and is not
supported for the ISO, NTP, MPLS, UNIX, and VPLS families. The output of this
command will be fixed in JUNOS 10.1R1 to display the message: “Multicasting
is not supported by UNIX, ISO, NTP, MPLS, and VPLS protocols.” [PR/235712:
This issue has been resolved.]
■
When certain FPCs (T1600-FPC4-ES, T640-FPC4-1P-ES, T640-FPC1-ES,
T640-FPC2-ES, and T640-FPC3-ES) receive corrupted cells via high-speed links,
they might unnecessarily reboot and report the following system log error
message: "Unrecoverable Error: Flist gtop bit toggled !." No reset is needed to
recover from this condition. [PR/441844: This issue has been resolved.]
■
When the strict-high priority queue is overloaded, the high priority queue may
starve, resulting in the loss of high priority traffic. [PR/455152: This issue has
been resolved.]
■
When the flow monitoring version 9 feature is enabled on an MS PIC (or service
PIC which supports flow monitoring version 9), the MS PIC may crash upon
receiving certain corrupted IPv6 packets. [PR/458361: This issue has been
resolved.]
■
Reading the list of boot devices from the BIOS may fail once in hundreds or
thousands of times due to an improper locking mechanism. [PR/461320: This
issue has been resolved.]
■
After upgrading from JUNOS Release 9.3 to Release 9.5, the timestamps in the
log files show the UTC time instead of the local time corresponding to the
specified time zone. [PR/469175: This issue has been resolved.]
■
On T640 and TX Series routers which have outgoing interface on a GFPC , the
interface might report LSIF errors or cell mismatched errors after it receives an
IPv6 packet with an invalid payload. The interface still accepts traffic, but discards
all outgoing packets. To recover, reboot the FPC on T640 and TX Series routers.
But if the IPv6 packets of the invalid payload are still transmitted, the problem
will occur again. [PR/470219: This issue has been resolved.]
■
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.]
88
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
