Specifications

82 ExtremeWare 7.3.1b3 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
ELRP
ELRP and Ingress Rate Shaping
Do not use ingress rate shaping on an ELRP-enabled VLAN (PD2-133066184).
VRRP
Proxy ARP Replies on VRRP Enabled VLANs Are Incorrect
When sending out proxy ARP replies on a VRRP enabled VLAN, the sender MAC address in the ARP
Reply contains “System MAC” instead of “VRRP MAC” (PD3-1275521).
Backup Transition Creates Duplicate Packets
A VRRP transition from backup to master might cause duplicate data packets to be transmitted for a
short period of time. The packets are dropped, so no action is required (PD2-129379226).
QoS
QoS Profiles Applied to Non-Master Ports in Load Sharing Groups
Although QoS profiles should only be applied to the master port in a load sharing group, the CLI does
not enforce this behavior. When a QoS profile is applied to a non-master port, the CLI accepts the
command, issues no error, but does not apply the profile (PD2-243742691).
QoS Profile Statistics Are Not Shown for Non-master Ports in a Loadshared/CMT Group
When a QoS Profile is applied to traffic being transmitted through the trunk ports (CMT), the QoS
profile statistics for some ports is 0, even though the port statistics show that the traffic is being sent
through the same ports (PD2-235114601).
The qosprofile Accepts a Value Greater than 100%
The maxbw parameter in the configure qosprofile command incorrectly accepts values greater than
100%; however, the maximum bandwidth is still 100% (PD2-123662004).
Re-Ordering Access List Precedence Numbers
When you add a new ACL rule with a precedence number, the switch re-orders existing rules with
lower precedence numbers to make room for the new rule. If, during this re-ordering, two rules have a
precedence number difference greater than one, the switch generates an error message similar to the
following:
<WARN:KERN> Access rule does not exist
You can safely ignore this error message (1-FAO8M).