Specifications

Clarifications and Known Behaviors
ExtremeWare 7.0 Release Notes 43
Alpine and Cross Module Load Sharing. The I/O module configured to contain the “master” port
must be physically present in a cross-module load sharing group for the system to pass traffic (8589,
PD2-119098401).
Load Sharing and Specific Ports in a Load Share Group. Due to the load sharing algorithm used
for round robin load sharing, when using 3, 5, 6 or 7 ports in a load share group packet loss will be
observed when sending wire-speed traffic across the load share group. This occurs because some ports
will be selected to transmit more packets than other ports resulting in bandwidth over-subscription and
subsequent packet loss. This only occurs with round-robin load sharing configurations (10311).
Load Sharing, Software Redundant Ports, and Smart Redundancy. The smart redundancy feature
is not supported when using software redundant ports and load sharing (12431).
Disabling Load Sharing if the Master is Down Generates Error. If the load sharing master link goes
down, and you disable load sharing, the switch generates a ptag error message (PD2-129379272).
Spanning Tree
Deleting a Port From the STP Domain. If you delete a port from the STP domain and save the
configuration, that change is not saved. You must either delete the port again after rebooting or edit the
configuration file to delete the port from the configuration (PD2-130809831).
Configuring a VLAN from Vista. If you create an STPD using ExtremeWare 6.1.9 (or earlier), add a
VLAN, save the configuration, upgrade to ExtremeWare 6.2.2b68 (or later), and save the configuration,
you receive the following error message when you try to modify the VLAN from Vista:
ERROR: Cannot assign bridge to stpd! HINT: If a port is part of multiple vlans, the
vlans must be in the same Spanning Tree domain.
To work around this problem, make configuration changes from the CLI (PD2-118450190).
STP and VLAN Tagging. VLAN tagging is not supported with 802.1d Spanning Tree (STP) BPDUs.
Therefore, all BPDUs in a 802.1d STP domain are untagged. However, Extreme Multiple Instance
Spanning Tree (EMISTP) and Per-VLAN Spanning Tree (PVST+) do support VLAN tagging of BPDUs.
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).
Upgrading From an ExtremeWare 6.1.9 (or earlier) Configuration. After downloading an
ExtremeWare 6.1.9 (or earlier) configuration to an ExtremeWare 6.2.0 (or later) image, a port belonging
to a non-default VLAN will generate the “Stpd s0, Port 1:1 does not exist” error message because that
VLAN does not belong to domain s0 by default (1-BMP5D).
MAC Security
The source FDB address configuration will not discard ICMP packets (16340).