Resolved Issues In Junos Release 10.1 For Ex Series Switches; Access Control And Port Security; Bridging, Vlans, And Spanning Trees - Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note

JUNOS 10.1 Software Release Notes

Resolved Issues in JUNOS Release 10.1 for EX Series Switches

The following are the issues that have been resolved since JUNOS Release 10.1R2
for EX Series switches. The identifier following the descriptions is the tracking number
in our bug database.

Access Control and Port Security

Bridging, VLANs, and Spanning Trees

196
Resolved Issues in JUNOS Release 10.1 for EX Series Switches
When both DHCP relay and DHCP snooping are configured on an EX2200 switch,
the DHCP snooping database might not be built on the switch. [PR/480682: This
issue has been resolved.]
When Multiple VLAN Registration Protocol (MVRP) and MSTP are enabled together
on EX Series switches, convergence does not occur between MVRP and MSTP.
[PR/449248: This issue has been resolved.]
On EX4200 switches with the access interface through which traffic enters the
switch configured as trusted (
), VLAN Spanning Tree Protocol (VSTP) bridge protocol data units
dhcp-trusted
(BPDUs) are sent to the Routing Engine with the learning CPU code 37 instead
of the reserved learning CPU code 306. [PR/468095: This issue has been resolved.]
On EX3200 and EX4200 switches with large VLAN configurations (more than
1024 VLANs), stale dynamic VLAN entries might be found in the Ethernet
switching process ( eswd ) after you delete VLANs or deactivate the Multiple VLAN
Registration Protocol (MVRP). [PR/471647: This issue has been resolved.]
On an EX2200 switch, when there is no spanning-tree protocol or redundant
trunk group configured in the network and there is traffic looping, after the
network loop is broken, sometimes MAC learning might not occur. As a
workaround, restart the forwarding (
been resolved.]
On EX Series switches, in a scaled environment with more than 4000 VLANs,
MVRP advertisements might not be sent intermittently when the VLAN
membership is modified. [PR/475701: This issue has been resolved.]
When MVRP and VSTP are enabled together on EX Series switches, convergence
does not occur between MVRP and VSTP. [PR/477019: This issue has been
resolved.]
On EX3200 and EX4200 switches, when MVRP dynamic VLAN creation is
disabled, deregistration of VLANs on trunk interfaces does not occur even after
the tag associated with the VLAN has been modified. [PR/479636: This issue has
been resolved.]
On EX3200 and EX4200 switches, stale MVRP VLAN membership entries might
be found on blocked interfaces even after MVRP has been deactivated on the
peer switch. [PR/482126: This issue has been resolved.]
secure-access-port interface interface-name
) process. [PR/473454: This issue has
pfem