Specifications

34 ExtremeWare 7.0 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Smart Redundancy Enabled in Saved Configuration
Smart redundancy is always enabled in a saved configuration. To work around this, disable smart
redundancy after downloading a configuration (PD2-128133503).
Microsoft Load Balancing
When using Microsoft load balancing, if you replace existing hardware and use the same IP address on
the new hardware (thus associating the same IP address with a new MAC address), IP traffic through
the IPFDB is not forwarded. To work around this, manually clear the IPFDB (PD2-124851229).
Telnet and the show ports Command
If you telnet to the switch and use the show ports info detail command, the line feeds might not be
recognized, resulting in output lines overwriting previous lines (PD2-130127501).
The show configuration Output
After using the unconfigure switch all command, the show configuration output displays the
VLAN default without any ports assigned. The ports still belong the to VLAN default, as the
show vlan
output correctly displays (PD2-128233941).
Configure Slots or VLANs Before Uploading a Configuration
If you do not configure any slots or VLANs, upload the configuration, reboot the switch, and download
the configuration, all ports are deleted from the default VLANs (PD2-110787427). The workaround is to
configure slots or create a VLAN before you upload the configuration.
LACP not Supported
Contrary to the information in the ExtremeWare 7.0 Software User Guide and ExtremeWare 7.0 Command
Reference Guide, LACP is not supported.
Upgrading to ExtremeWare 7.0 and Bi-Directional Rate Shaping
When you directly upgrade from ExtremeWare 6.2.2 to ExtremeWare 7.0, bi-directional rate shaping
does not work if the loopback ports were in autonegotiation mode. This behavior is not displayed by
10/100Base-T or Gigabit fiber ports. A workaround is to remove and re-add the loopback ports to the
VLAN (PD2-107820904).
Upgrading to ExtremeWare 7.0 and Debug-Trace
When you directly upgrade from ExtremeWare 6.2.2 to ExtremeWare 7.0, the debug-trace configuration
might change. Verify the debug-trace configuration, if any, after upgrading. Use the
show debug-trace
command to display the configuration. You can either re-configure manually, or download the
ExtremeWare 6.2.2 configuration instead of doing a direct upgrade (PD2-106733988).
Upgrading to ExtremeWare 7.0 and OSPF
If you upgrade directly from ExtremeWare 6.2.2 to ExtremeWare 7.0, the OSPF metric for 10 Gigabit
interfaces is incorrect. A workaround is to manually configure the OSPF metrics, or to upload the
configuration before upgrading and then download the ExtremeWare 6.2.2 configuration
(PD2-108161623).