■ The MX DPC might reboot with the error message: "EZ:
ezchip_get_srh_msg_from_srhq". [PR/310223]
■ The bridge-domain MAC learn limit on the Packet Forwarding Engine can
sometimes become negative if the bridge domain is deleted and added
immediately as part of a configuration change. If that happens, the MAC learning
on that bridge domain can be affected. As a workaround, deactivate and activate
the bridge domain or VPLS routing instance configuration. [PR/467549]
■ Due to a larger number of components on the Neo board, it takes more time to
boot up than a comparable MX Series boards. [PR/468665]
■ When lockout is configured and the router is rebooted, the working router is
stuck in the wait-to-restore state while the protect router still shows channel state
working and no requests, but no longer shows the lockout flag. [PR/474482]
■ On restart with a large-scale configuration (16K IFLs per MPC), the
MPC-3D-16XGE-SFPP card may take up to 15 minutes to come up. [PR/478548]
■
If a firewall show command is followed by the clear command in a very quick
succession, there is a possibility that the show command will time out. If the
show command is issued after a few seconds (5 seconds ideally), this issue will
not be seen. [PR/479497]
■ When an IQ2 PIC is brought online with a class-of-service configuration that
includes a scheduler using the rate-limit options, the system incorrectly reports
that rate limiting is not supported on the PIC. [PR/482199]
■ With JUNOS Releases 10.0 and 10.1, Trio DPCs do not support more than 31
remote PEs in a VPLS instance. Also, they do not support more than 31 AE
bridging logical interfaces in a bridge domain. [PR/488139]
■ If a T640-FPC4-ES is installed in a T1600 router and an SIB statistics collection
is performed, the message log might report "JBUS: U32 read error, client .." only
if one of the SIBs is faulted or in the offline state. This system log message will
also appear if the T640-FPC4-ES FPC is removed from the chassis. There is no
operational impact. [PR/504363]
■ On an M20 router with AC PEMS, the alarm message “Power Supply x not
providing power” is generated when the power cord is removed. The alarm is
not cleared when the power cord is reconnected. [PR/506413]
■ When trigger hold timer UP/DOWN values for a defect condition is configured
or changed from the CLI, the up or down timer for the defect is started, based
on the current defect condition in the hardware. If the timer value is large enough
and the defect condition is changed in the hardware when the timer is still
running, a new defect will be reflected in the alarms only after the timer has
expired. [PR/509890]
■ When the 1x10GE PIC is brought online, related error messages are seen in the
logs but without any functional impact. [PR/512094]
■ Under certain conditions, some Packet Forwarding Engines may fail to install
VPN multicast routes when downstream interfaces are RLSQ bundles.
[PR/515878]
56 ■ 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...
Need help?
General
