Specifications

Page 36 ExtremeWare v6.2.1 Release Notes
Release Notes for ExtremeWare v6.2.1
DHCP Server
The DHCP server is not supported as a standalone feature. It is used as part of the Network Login
feature only. (1-8SAI6)
DLCS
DLCS is only supported on “i” series modules (8389).
Virtual Chassis
The Virtual Chassis is not supported in ExtremeWare v6.0 or higher.
Issues Resolved in this Release
General
nslookup Function Did Not Handle Multi-answer DNS
The nslookup function in ExtremeWare did not correctly handle a multi-answer DNS response. In turn,
this meant that ExtremeWare
ping and traceroute commands used with name arguments were
unreliable since there was no way to tell whether there were multiple answers to the DNS request.
(14903/15097)
FDB Aging Value Incorrect After Change to Aging Timer
After changing the FDB aging timer value, the age values of entries in the FDB table could become
incorrect. (16043/12632)
SNMP
SNMP Unresponsive After snmpwalk Command
Executing an snmpwalk command in certain situations would cause the switch to become unresponsive
to any other SNMP requests until the switch was rebooted. (12890)
Trap Sent Only to Last Trapreceiver After “clear iparp”
After a “clear iparp” command was issued, which removed the next hop MAC from the iparp table,
the default route would be used, and an SNMP trap would be sent only to the last trap receiver.
(14939/14929/14932)
Server Load Balancing
When switching from ping health checking to L4 port health checking only one next hop would stay
up. When switching back to ping health checking, one next hop would continue to stay down. (148793)
Disconnecting and recoonecting one next hop could also cause the next hop to stay down. (16363)