Specifications

42 ExtremeWare 7.0 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
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 may 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).
Load Sharing
Load Sharing and Software Redundant Ports. If you configure software redundant ports with load
sharing, saved configurations do not load properly via TFTP. The configuration file executes the
software redundant port configuration before the load sharing configuration, but you must configure
load sharing first. To avoid this, edit the configuration file so that the load sharing configuration is
executed first (PD2-130597269).
Autonegotiation. Load sharing ports must be configured with autonegotiation set to on. Load sharing
ports will not transmit traffic correctly using any other setting (PD2-64617405).
Round Robin Load Sharing. If a port in a round robin load share group is removed, the traffic that
was being transmitted on that link will be distributed on only 1 of the other active load share links in
the round robin group. The traffic is not distributed evenly between the remaining ports (6977).
Port Based Load Sharing on Summit7i. Port-based load sharing on the Summit7i requires ingress
ports to be on the same side of the switch (ports 1 - 4, 9 - 12, 17 - 20, and 25 - 28 on the left, ports 5 - 8,
13 - 16, and 21 - 24 on the right) as the 8 ports in the load share group for all ports in the load share
group to transmit/receive traffic (6975).