■
Both the working and protect circuit are stuck in the “disabled” state when the
TX cable is unplugged and the RX cable is plugged for protect circuit after an
Automatic Protection Switching (APS) switchover. [PR/466649: This issue has
been resolved.]
■
On an M320 router, the 4x STM-1 1x STM-4 SFP PIC (PB-4OC3-1OC12-SON-SFP)
currently supports only two ports (0 and 2) when configured for eight queues
per port on an E3 FPC. [PR/475008: This issue has been resolved.]
■
SFPs are absent in the output of the
show chassis hardware
command following
TOXIC SFP messages. [PR/480828: This issue has been resolved.]
■
When a DPC restarts, a large amount of route (about 700,000 simple IPv4 routes)
remains in the forwarding table learned through another DPC. The sync process
between the Routing Engine and the Packet Forwarding Engine will take too
long, and the Routing Engine will restart the FPC. This repeats endlessly.
To restore the service and get the DPC out of the boot loop, restart the chassis
process or the routing process. [PR/481164: This issue has been resolved.]
■
In some cases during the periodic error status monitoring, error messages such
as “Wi seg ucode discards in fabric stream” might be displayed on adjacent
streams. These messages are cosmetic and can be ignored. [PR/481344: This
issue has been resolved.]
■
Under certain conditions, when aggregate interfaces are used and the member
links are located on more that one FPC, multicast traffic will not use one or more
of the aggregate child links. This can happen after an FPC reboot.
If the aggregate member links are located on the same FPC, this problem is not
triggered. To recover from this condition, deactivate and activate the aggregate
interface. [PR/484007: This issue has been resolved.]
■
The logical unit of a Gigabit Ethernet interface may show less than 1000 Mbps
of bandwidth even if there is no speed configuration under the physical interface.
As a workaround, manually set the bandwidth on the logical interface.
[PR/485840: This issue has been resolved.]
■
When loopback is configured on t3 under ct3, t1 under ct1, or e1 under ce1, no
error syslog message is logged. Additionally, the
show interface extensive
command on the t3/t1/e1 displays "loopback" even though it is not actually
applied. [PR/486424: This issue has been resolved.]
■
On an M20 router with an LS PIC, the backup Routing Engine kernel may core
at rnh_index_alloc. [PR/486646: This issue has been resolved.]
■
Traffic may be sent out on a child link of an aggregated Ethernet (AE) bundle
even when it is not in the Collecting-Distributing Link Aggregation Control Protocol
(LACP) state if and only if the following conditions are met:
■
The remote end configured one link to be primary and another to be backup.
■
On the System Under Test (SUT), a unit of the AE bundle is disabled, then
enabled.
As a workaround, deactivate and activate the child link that is not in the
Collecting-Distributing LACP state. [PR/487786: This issue has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
83
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
