Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 57

Layer 2 Ethernet Services
NOTE: The duplicate LACP port number described above does not affect the
aggregation, but affects the SNMP extracting port information and shows an identical
pair of SNMP dot3adAggPortPartnerOperPort and dot3adAggPortActorPort for the
above mentioned links of the aggregate bundle.
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
The output of the
show chassis environment pem
used in FPC slots 0 through 3, even after the FPC is taken offline. [PR/528821]
If no dot1p classifier is explicitly configured for the logical interface of vid=0,
to accept priority tagged packets, packets without an IP header such as STP will
determine the forwarding class based on the priority tag value. [PR/529207]
DHCP packets may not be processed on an auto-sensed VLAN interface if the
DHCP configuration for the interface is performed after the auto-sensed VLAN
interface is instantiated. As a workaround, clear the auto-sensed VLAN interface(s)
after the DHCP configuration is made for the interface(s). [PR/417958]
On a TX Matrix router, an aggregate bundle composed of member links from
different LCCs has the same slot/PIC/port, and results in duplication of Link
Aggregation Control Protocol (LACP) port numbers. For example, a bundle with
actor and partner shown below will result in a duplicate LACP port number since
ge-0/3/0 and ge-8/3/0 (and similarly ge-1/3/0 and ge-9/3/0) are the same
slot/PIC/port but from different LCCs.
Actor
ge-0/3/0 ge-1/3/0
ge-8/3/0 ge-9/3/0
On MX960 routers, duplicate LACP port numbers will result in aggregate bundles
composed of member links for the same PIC and port on slots (0, 8), (1,9), (2,10),
and (3,11). Also, the following sets of ports on any slot will have duplicate LACP
port numbers:
PIC 0 port 8 and PIC 1 port (0,8)
PIC 0 port 9 and PIC 1 port (1,9)
PIC 2 port 8 and PIC 3 port (0,8)
PIC 2 port 9 and PIC 3 port (1,9)
[PR/526749]
A Spanning Tree Protocol triggered MAC flush might fail if there are frequent
topology changes with a significant number of MAC addresses learned. For
multiple Spanning Tree Protocols, restart l2cpd-services to come out of the state,
and for the Rapid Spanning Tree Protocol, reboot the corresponding DPC.
[PR/529130]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
command displays the voltage
Partner
57