Specifications

62 ExtremeWare 7.4.3 Installation and Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Port Sharing Between G24T and G8X I/O Modules is not Working Correctly
Cross module port sharing involving a G24T and G8X I/O module is not working correctly and
generates the following error message:
* BD6808:21 # en shar 7:1 g 7:1,8:1
ERROR: Ports 7:1 and 8:1 are running at different speeds.
You can only load share on links operating at same speed.
(PD3-37325552)
Some APs Reboot in Heavy Traffic and High RF Interference
A switch with 20 plus APs and a high level of RF interference may experience up to three AP reboots in
a 24-hour period (PD3-36148261).
Enabling HTTP on a Non-SSH ExtremeWare 7.4 Image
In ExtremeWare 7.3, the CLI command syntax used to enable HTTP is enable web http even when
upgrading a non-ssh image. In ExtremeWare 7.4, the
enable web command is use with the option
http/https. This command option is only available with the ssh image. Therefore, when upgrading an
ExtremeWare 7.3 non-ssh configuration to an ExtremeWare 7.4 non-ssh configuration, the
enable web
http
command will fail.
# enable web http
Syntax error at token http
Next possible completions:
<cr> access-profile
Upgrading the Switch to ExtremeWare 7.4 from ExtremeWare 7.2 or Earlier
When the BlackDiamond, Alpine, and Summit switches are upgraded from ExtremeWare 7.2 or earlier
to ExtremeWare 7.4, you may see the following error messages. These error messages are harmless as
these commands are not supported on the management VLAN in ExtremeWare 7.4.
- configure vlan "Mgmt" priority 0
ERROR: Cannot modify 802.1P Priority for the Mgmt Vlan
configure vlan "Mgmt" qosprofile "QP1"
ERROR: vlan "Mgmt" cannot be configured
configure vlan Mgmt qosprofile ingress none
WARNING: This command only applies to the G16X3 and G24T3 I/O modules.
(PD3-1303781)
Load Sharing Group Cannot be Rate Shaped with Loopback Port
You cannot configure a load sharing group for rate shaping with a loopback port, nor can you tag a rate
shaped port, even though the CLI is allowing you to do so (PD2-243742672).
CPU DoS Protect and ACL Precedence
If you configure the CPU DoS protect feature with a filter precedence of x, you cannot create an access
list with a precedence of x, x+1, or x+2. All other values are acceptable.
If you configure an access list with a precedence of x, you cannot configure the CPU DoS protect feature
with a filter precedence of x, x-1 or x-2. All other values are acceptable (PD2-129163428).