Specifications

14 ExtremeWare 7.0 Release Notes
Overview
The following features are no longer supported on T1 or E1 modules:
— T1 port mirroring
— Static Load sharing
— Software-Controlled Reduntant Ports
— ACLs on a per port basis
— Per Port Egress QOS
— Traffic Grouping for source ports
— BiDirectional Rate Shaping
— DLCS
— MAC address and protocol-based VLANs that include T1 ports
— VLAN aggregation
In addition, layer 2 multicast traffic is treated as broadcast traffic by the T1 and E1 modules.
This feature is not documented in the ExtremeWare 7.0.0 Command Reference Guide or the ExtremeWare
7.0.0 User Guide.
• You can now block the SQL Slammer DoS attack. SQL Slammer causes high CPU utilization on the
next-hop switch servicing multicast requests as IGMP sender entries are quickly populated into the
multicast sender list. This leads to a high number of multicast entries in the IGMP snooping entry
table, and a message similar to the following in the system log (PD2-118292101):
<WARN:HW> tBGTask: Reached maximum otp ExtraMC index allocation
To block and clean up after this attack:
a Block the attack by creating an ACL to block port 1434 using the following command:
create access-list UDP dest any ip-port 1434 source any ip-port any
b Remove affected SQL servers from the network (you can simply disable the port connecting the
server).
c Clean up the existing IGMP snooping entries and IPMC cache using the following commands:
igmp snooping
clear ipmc cache
d Disable IGMP snooping on the affected switches. Disabling IGMP snooping affects routing
protocols using multicast addresses and multicast traffic on that switch.
This feature is not documented in the ExtremeWare 7.0.0 Command Reference Guide or the ExtremeWare
7.0.0 User Guide.
• BGP no longer sends withdraws to a neighbor for routes that were not advertised to the neighbor
(1-8P0O9).
Route filters such as access-profiles, route-maps, or Network Layer Reachability Information (NLRI)
filters filter advertisements of routes to BGP peers. BGP no longer withdraws routes from neighbors
if the routes were filtered. This provides the following benefits:
— Reduces peer routers’ BGP control processing time
— Reduces bandwidth overhead over peer session links
— Improves switch resource utilization by reducing the number of locally originated packets
The output of the
show bgp neighbor <ip address> transmitted-routes command now
displays the local attributes of the routes that were transmitted to the neighbor, rather than the actual
attributes that were transmitted to the neighbor.