Specifications

Clarifications and Known Behaviors
ExtremeWare 7.4.3 Installation and Release Notes 63
Alpine
EPICenter/SNMP Does not Show Port Display String
When configuring a port string using an Alpine switch and viewing the port information from
EPICenter, the configured port string is not shown in the port information (PD3-40520509).
BlackDiamond 6800
BlackDiamond Switch Generates L2 Known Unicast Traffic
A BlackDiamond switch is generating L2 known unicast traffic after disabling and enabling a slot
(PD3-40044661).
Summit 200, Summit 300-48, and Summit 400 Switches
AP Not Coming Up in Remote Connect
The AP is not coming up in remote connect after switching from direct connect.
Workaround. Create a separate VLAN for the discovery switch for the AP upgrade (direct connect).
(PD3-46430702)
Loopback Detect Does Not Work on ExtremeWare 7.4e.1b5
On a Summit 300-48 switch running ExtremeWare 7.4e.1b5, if you connect loopback on a specific port
and then enable loopback detect, loopback is detected and the port is brought down after 3 or 4 hours.
The port is then bought up and down continuously (PD3-39424321).
Opnext ER XENPAKs Generate an Error Message
Opnext ER XENPAKs used in a Summit-400-48t switch generates the following error message and
causes the switch port to not come up:
04/05/2005 14:15:20.38 <Erro:PORT> Xenpak on port 49 detected, unable to read Oui,
possible mdio read error.
(PD3-38955593)
Bi-Directional Rate Shaping
Changing the Configuration of a Loopback Port
If you change the configuration (speed, duplex setting, etc.) of a loopback port, you must either save the
configuration and reboot the switch, or delete the port from the VLAN and add it back (PD2-128242637,
PD2-127582534).