■
Under some circumstances where LDP is enabled, a memory leak might occur
where the routing protocol process does not free up memory. [PR/493885: This
issue has been resolved.]
■
An incorrectly changed LDP session authentication key causes the LDP session
to fail, and the LDP/IGP syncronization feature stops working. The IGP continues
to advertise the link at normal metric values. [PR/499226: This issue has been
resolved.]
■
LDP might not handle certain error conditions gracefully when NSR is enabled.
This might cause the LDP replication state to be stuck in the "In Progress" state
forever. [PR/505043: This issue has been resolved.]
■
The
show route table mpls.0 label-switched-path
lspname
command may cause
the routing protocol process to core if no route is found. [PR/507239: This issue
has been resolved.]
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 knob because
this knob 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.]
80
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes