Specifications

Page 24 ExtremeWare v6.2.1 Release Notes
Release Notes for ExtremeWare v6.2.1
packets are transmitted from the switch in the event that lower priority queues are congested. This
mechanism uses internal resources and limits the number of VLANs that can be configured on a switch.
The following CLI command must be used to set the CPU-transmit priority:
config cpu-transmit-priority [high | normal]
To view the configured CPU-transmit priority, use the following command:
show switch
Note that the switch must be rebooted for this change to take effect. The default setting for the
CPU-transmit priority is “high” (7120).
If non-“i” series I/O modules are installed in a BlackDiamond Chassis, the maximum number of
VLANs supported will be 1024 (8908).
VLAN to VLAN Access Profiles
VLAN to VLAN access profiles are no longer supported on the BlackDiamond switch in ExtremeWare
v6.0 or higher (7022).
Load Sharing
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 as the 8 ports in the load share group for all ports in the load
share group to transmit/receive traffic (6975).
Alpine and Cross Blade Load Sharing. The I/O module configured to contain the “master” port
must be physically present in a cross-blade load sharing group when the system is rebooted (8589).
With four or more blades, configuring load sharing across blades can cause a slot mismatch. If you
create a load share group with ports from four different blades, you will get a mismatch error upon
reboot. (1-9W4T6)
Load Sharing and Specific Ports in a Load Share Group. Due to the load sharing algorithm used
for round robin load sharing, when using 3, 5, 6 or 7 ports in a load share group packet loss will be
observed when sending wire-speed traffic across the load share group. This occurs because some ports
will be selected to transmit more packets than other ports resulting in bandwidth over-subscription and
subsequent packet loss. This only occurs with round-robin load sharing configurations (10311).
Load Sharing Port Configuration. All the ports in a load sharing group must have the same exact
configuration, including auto negotiation on/off, duplex half/full, ESRP host attach (don’t-count), and
so on.
Spanning Tree
STP not Supported with ESRP. Spanning Tree is not supported and should not be attempted in
conjunction with ESRP.