Specifications

44 ExtremeWare 7.0 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Mirroring
Mirroring IP Multicast Traffic. Due to IGMP Snooping capabilities, Multicast traffic may cease to be
seen on a “mirror port”. If you issue a “restart” command for the mirror port or remove and reinsert the
port connection, multicast traffic will resume for the IGMP Host time out period (260 sec.) (3534).
Mirroring and Flooding. When a mirrored port is configured, the forwarding database for items being
mirrored (e.g. ports or VLANs) are automatically cleared from the forwarding database if the link status
on the mirror port changes. This will result in some temporary flooding until the normal learning
process completes. Thus, removing or inserting a probe device into the mirror port may appear to cause
flooding, however this is expected behavior (5128).
QoS
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).
Access List FDB Entries not Cleaned Up
If you delete an access list with the “f” flag (flow rule), the associated FDB entries might not be cleared
(PD2-110082518).
Access Lists Using the IP Deny Any Rule
When using an access control list with an IP deny any rule, all ICMP traffic will be blocked within a
VLAN (Layer 2). If using an access list with an IP deny any rule across VLANs (Layer 3), ICMP traffic
will not be blocked.
Access Lists and IP Fragmentation
When using IP fragmentation, since the TCP header is treated as data and only the IP header
information is being replicated in each packet, access-lists that apply to that flow will not apply as the
TCP/USP port information is not included after the first fragment (for subsequent fragments).
QoS Configuration Bandwidth Parameters
Minimum and maximum percentage parameters for a specific port on the default VLAN will not be
saved across reboots. The configuration change will be applied when configured. This issue only occurs
on the BlackDiamond (15500).