■
The yellow marking for the three-color-policers is incorrect. Even after the excess
burst buffer is full, the yellow counters continue to increment at the same rate
as the green buffers. [PR/504192: This issue has been resolved.]
■
As a result of an incorrect configuration for the DDR memory controller, errors
might be reported when a Trio-based MPC or MX80 boots. There is no
workaround. [PR/505490: This issue has been resolved.]
■
Under certain circumstances, the E3 IQ PIC might report bogus CCV, CES, and
CSES alarms. [PR/505921: This issue has been resolved.]
■
The JUNOS Software may accept duplicate data-link connection identifiers (DLCIs)
configured on the same physical interface. [PR/506908: This issue has been
resolved.]
■
When
native-vlan-id
is configured for aggregated interface with the child links on
an IQ2 PIC, the LACP are dropped and the links go down. [PR/507040: This issue
has been resolved.]
■
The
show interfaces diagnostics optics interface
command does not display the
unit of measurement when the received power is in a very low range (power <
5e-10). It shows the value of 0.00 without any unit of measurement. [PR/507653:
This issue has been resolved.]
■
On MX Series routers, the chassisd crashes when the SCB is taken offline and
removed. [PR/510950: This issue has been resolved.]
■
On M7i and M10i routers, the syncer process writes to the file
/var/rundb/chassisd.dynamic.db
every 30 seconds. [PR/511901: This issue has
been resolved.]
■
Under certain circumstances, the chassisd process might crash on a backup
Routing Engine while a configuration is commited. [PR/512044: This issue has
been resolved.]
■
Due to a flaw in implementation, the execution of the
show interfaces
mac-database
command causes the IQ2 PIC to reboot with the core. [PR/513407:
This issue has been resolved.]
■
The local protocol MTU on an interface with PPP encapsulation might become
higher than the configured media MTU after the PPP negotiation when the remote
end has a higher media MTU configured. [PR/514079: This issue has been
resolved.]
■
The monitor traffic interface (tcpdump) does not produce an outbound output
with matching option when used with the encapsulation
flexibile-ethernet-services. [PR/514247: This issue has been resolved.]
Layer 2 Ethernet Services
■
The DHCPv6 clients do not bind when routing-options access-internal is
configured. [PR/495358: This issue has been resolved.]
■
On MX960 routers, i2c messages related to the fan such as the following are
displayed:
Jan 26 13:32:22 rocky-re0 /kernel: PCF8584(WR): target ack failure on byte 0
Jan 26 13:32:22 rocky-re0 /kernel: PCF8584(WR): (i2c_s1=0x08, group=0xe,
device=0x54)
68
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes