■ With GRES configured, a container interface (CI) configuration can trigger a
kernel core on the backup Routing Engine. [PR/488679: This issue has been
resolved.]
■ Container interfaces with ATM children with OAM may not initiate sending of
OAM cells after Automatic Protection Switching (APS) switchovers. [PR/489250:
This issue has been resolved.]
■ Commit fails with IEEE 802.1p config when applied to container interfaces.
[PR/489400: This issue has been resolved.]
■ Kernel panic may occur if the child ATM interfaces are removed or disabled
under container. [PR/490196: This issue has been resolved.]
■ The system may not learn all MACs in the hardware within a second across the
fabric when trying to learn all new MACs at a 10–Gigabit line rate. A small fraction
will be learned via the software path, in the order of hundreds of seconds.
However, all MACs are learned eventually. [PR/489705: This issue has been
resolved.]
■ When filter-based forwarding is applied to the output interface and the egress
Packet Forwarding Engine (PFE) is different from the ingress PFE, the traffic gets
regular discards. [PR/490214: This issue has been resolved.]
■ During graceful Routing Engine switchover (GRES), if the peer's discovery state
is passive, the LFM state machine should be kickstarted even if the kernel state
is SEND_ANY, otherwise the peer will be stuck in PASSIVE_WAIT state. As a
workaround, configure both sides in the link-discovery mode as “active.”
[PR/490886: This issue has been resolved.]
■ On the IEEE 802.1ag CFM, when the loss threshold is configured to 256, it
displays a '0.' [PR/491422: This issue has been resolved.]
■ Whenever the system gets busy, the master Routing Engine might relinquish
mastership and take the line cards offline soon after. [PR/491583: This issue has
been resolved.]
■ The CI logical interface state may go out of sync when OAM is configured and
the logical interface flaps due to OAM. [PR/491866: This issue has been resolved.]
■
The chassis cell relay mode might not be set properly for CI interfaces.
[PR/492197: This issue has been resolved.]
■ The DPC remains in the ready state and the demux0 interface remains in a down
state after a chassisd restart without graceful Routing Engine switchover enabled.
[PR/492961: This issue has been resolved.]
■ When an SCB with an active plane is powered down, an HSL link error occurs
on unrelated SCBs. [PR/493151: This issue has been resolved.]
■ The CLI does not respond when Control+c is entered at the "more” separator.
[PR/493881: This issue has been resolved.]
■ The system may generate a core file when the DPC is removed before it is taken
offline. [PR/494625: This issue has been resolved.]
■ An outer virtual LAN tag is not added in a provider edge-customer edge link when
VPLS traffic arrives with an MPLS value of 2, 3, 4, or 5. However, VPLS traffic
with a value of 0, 1, 6, or 7 does not have this issue. [PR/495555: This issue has
been resolved.]
84 ■ Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
To Next Page
Loading...