Specifications

80 ExtremeWare 7.3.1b3 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Output of show stpName port detail Command in Hex Format
The output of the show stpName port detail command displays the PortID in hex format instead of
decimal format. If you do not specify the
detail parameter, the output correctly displays in decimal
format (PD2-136044001).
If You Delete a Port from the STPD, You Cannot Add It Through a VLAN
If you delete a port from the STPD, then add a VLAN containing that port to the STPD, the deleted port
is not added. To work around this, add the port back to the STPD (PD2-144382901).
The unconfigure stp Command Does Not Clear All Configurations
The unconfigure stpd command does not clear the tag, VLAN, operational mode, rapid root failover,
port mode, or port link-type. To clear these configurations, use the
delete stpd command
(PD2-137310575).
Enabling ignore-bpdu or ignore-stp
If you enable ignore-bpdu or ignore-stp on a VLAN and then enable STP, the switch still participates in
STP election. To work around this, reboot the switch (PD2-140533593).
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 and 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 generates the “Stpd s0, Port 1:1 does not exist” error
message because that VLAN does not belong to domain s0 by default (1-BMP5D).