Specifications

 WEP/TKIP traffic no longer experiences memory contention issues and thus
no longer freezes up. (6842)
SNMP
 A trap is now generated when the switch role is changed. (8262)
Soft AP
 The problem with in-band destined traffic occasionally being routed through
the out-of-band (mgmt) interface has been fixed. (6629)
 The max-client limit is no longer being ignored. (8218)
 The Network Summary now correctly reports AP status. (8117).
 AP 60s no longer stop sending beacons while configuring virtual APs. (7972)
VPN
 Switches are now able to handle more than 100 PPTP connection
requests.(7997)
xSec
 The xSec client is now assigned the correct role as configured in 802.1x.
(8175)
 2.4.0.0 users were able to configure an xSec client on the same VLAN as the
AP this client associated with, (which while permitted was not
recommended). This is not allowed in 2.4.1.0. Configuring xSec clients on
the same VLAN as the associated AP now results in the xSec client not
receiving an IP address as the mobility controller does not communicate with
the client using xSec if the client is on the same VLAN as the AP.
Known Issues and Limitations in this
Release
The following features and functionality have the following issues for Release 2.4.1.0.
Where bug IDs are applicable, they are included in the description of the issue.
 If a line card is removed and the switch is rebooted before the line card is
replaced, the VLAN configuration reverts to default values. (6226)
 Enabling NAT for source addresses on Aruba switches is compatible with
Nortel VPN clients provided a rule is added before the src-nat rule. To
support RSA token and time syncing, specify a rule on the client firewall.
 Access Points that are indirectly connected to Aruba Mobility Controllers
through third-party switches may have problems processing IP packets larger
than 1500 bytes. Aruba recommends setting the maximum transmission unit
3