workaround, restart the forwarding (
pfem
) process. [PR/473454: 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.]
Class of Service
■
On an EX2200 switch, when a queue is oversubscribed and you modify a
scheduler with the
buffer-size exact
option on it such that it reduces the allocated
buffers on the queue, the queue can stop dequeueing packets. As a workaround,
stop traffic going out on the port, and deactivate and reactivate class of service
(CoS). You can also reboot the switch. [PR/481401: This issue has been resolved.]
Firewall Filters
■
The
accept
action and the
log
and
syslog
action modifiers in the firewall filter
configuration might not work as expected for packets destined for the switch.
[PR/406714: This issue has been resolved.]
■
On EX3200 and EX4200 switches, if you configure an egress firewall filter with
the match condition
source-address
or
destination-address
on a VLAN and its
routed VLAN interface (RVI), the firewall filter might not work properly.
[PR/476626: This issue has been resolved.]
■
On an EX2200 switch when you add a
syslog
action modifier to the firewall filter,
the forwarding (
pfem
) process might create a core file when the filter binding is
changed from an egress VLAN to an ingress VLAN. [PR/495572: This issue has
been resolved.]
Resolved Issues in JUNOS Release 10.1 for EX Series Switches
■
195
Resolved Issues in JUNOS Release 10.1 for EX Series Switches
