Specifications

Clarifications and Known Behaviors
ExtremeWare 7.3.1b3 Release Notes 75
primary load share group even though the primary load share group has fewer active ports. However, if
another port in the primary group fails, traffic correctly fails over to the redundant load share group.
For example, ports 1:1-1:5 are the primary load share group and ports 2:10-2:15 are the redundant load
share group. If you remove the cables from ports 1:1-1:3, the load share group fails over to ports
2:10-2:15. If you remove and reinsert the I/O module installed in slot 1 and do not attach the cables to
ports 1:1-1:3, the load share group fails back to the primary load share group. If you then remove the
cable from port 1:4, traffic fails over to the redundant load share group (PD2-223253601, PD2-225707301,
PD2-246246401, PD2-246246404).
Saving ip-mtu Settings
Dynamic TLS (Martini TLS) checks the MTU received from its peer in order for TLS to come to the
established state. It compares against the egress VLAN’s IP-MTU. If the egress VLAN does not have an
IP address defined, any non-default ip-mtu setting will not be saved through a switch reboot
(PD2-64084527).
VLAN priority and STP, EDP
STP and EDP (thus ESRP and EAPS) do not transmit packets in the queue specified by the VLAN
priority (1-5HOZ9).
Default Routes or Static Routes
If you define a default or static route, and then delete the VLAN on the subnet associated with the
default route, the default route entry remains although it is invalid. You must manually delete the
configured route.
If you define multiple default routes, the one with the lowest metric is used. If there are multiple routes
with the same lowest metric, the switch picks one of the routes.
Configuring a Protocol Filter with ‘ffff’
Creating a protocol filter with LLC of value 0xffff and assigning it to a VLAN will not work, and should
not be attempted. Doing so will assign all traffic to the VLANs containing that filter and will prevent
VLANs with no protocol filter to function properly. If configured and saved, you must issue an
unconfigure switch all to restore normal operation (2644, 4935).
Deleting Protocols from a VLAN
Adding a protocol to a VLAN might cause an EPC if the protocol was added to the VLAN, deleted
from the VLAN, recreated by the user, and re-added to the VLAN (6128).
MAC-Based VLANs and DHCP Relay
MAC based VLAN configurations should not be used in conjunction with DHCP. Currently, a host
which enters a MAC-based VLAN will not be able to use DHCP to obtain an IP address.
VLAN to VLAN Access Profiles
VLAN to VLAN access profiles are no longer supported on the BlackDiamond switch in ExtremeWare
6.0 or higher (7022).