Specifications

Clarifications, Known Behaviors, and Problems
ExtremeWare v6.2.1 Release Notes Page 25
EMISTP and Ingress Rate Shaping. If a loop exists in your network, but STP is not enabled but
Ingress Rate Shaping is, the switches appear to hang and are rebooted by the watch-dog timer. A similar
situation exists if a loop is covered by STP on both sides and is disabled on one side; normally the other
switch immediately blocks the right port(s), but when Ingress Rate Shaping is present, both switches
appear to hang and are rebooted by the watch-dog timer (1-5E9R1).
MAC Security
The source FDB address configuration will not discard ICMP packets (16340).
CLI Changes for MAC Security
The command for specifying a MAC address learning limit has been changed in v 6.2.1. In v 6.2.0, the
command
config vlan <vlan> add port <port> mac-limit [no-limit | <number>] was used
to set a limit on the number of entries that could be learned. In v6.2.1, the mac-limit option has been
removed from the
config vlan command. Instead, a MAC address learning limit can be set using the
following command:
configure port <port-list> vlan <vlan> [limit-learning <number> | unlimited-learning]
If you do a direct upgrade from v6.2.0 to v6.2.1, the 6.2.0 command will be converted to the 6.2.1
command. However, a 6.2.0 configuration that is downloaded to a switch running the 6.2.1 image will
not automatically be converted, and will produce syntax errors related to the MAC-limit configuration.
(1-85QDI)
Mirroring
Mirroring Combined with Load Sharing. The following limitations apply when doing mirroring that
also involves load-sharing ports:
• Mirroring VLANs or mirroring a VLAN on a specific port is known to cause behavioral problems
when used in combination with load sharing. If enabled, load sharing will only make use of the
master port and will not fail-over correctly. Deleting the mirror entry will restore normal operation
(3735).
• If the master port of a load-shared port group is down, mirroring will not provide the traffic for the
load-shared port group (4486).
Mirroring IP Multicast Traffic . Due to IGMP Snooping capabilities, Multicast traffic may cease to be
seen on a “mirror port”. If you issue a ‘restart’ command for the mirror port or remove and reinsert the
port connection, multicast traffic will resume for the IGMP Host time out period (260 sec.) (3534).
Mirroring Bandwidth. Performing mirroring on gigabit ports running at line-rate will reduce the traffic
throughput by approximately thirty percent (4151).
Mirroring and Flooding. When a mirrored port is configured, the forwarding database for items being
mirrored (e.g. ports or VLANs) are automatically cleared from the forwarding database if the link status
on the mirror port changes. This will result in some temporary flooding until the normal learning
process completes. Thus, removing or inserting a probe device into the mirror port may appear to cause
flooding, however this is expected behavior (5128).