Specifications

 While moving a station, if 802.1x authentication is delayed, the show user

global-user-map command output is not displayed correctly. (6557)

 Wired clients who fail authentication are blacklisted, but they can still try to

 Session mirroring does not update for sessions that are already up. (6829)

 All PPTP connections to Aruba (or any PPTP server) for users with Windows

XP Service Pack 2 firewall enabled, will experience a one minute wait before

being able to reconnect.

 If the username is in the format of domain\username, trim-fqdn does not

remove the domain portion before sending request to the server. (6804)

 There is a BW contract granularity limitation. The effective bandwidth

enforced is not accurate for contracts less than 300 Kbits. (6838)

 The wired-dot1x role-based VLAN is not supported for SecureJack. (7464)

 WiFiMUX wired 802.1x is not supported in this release. (6310)

 Changes in the NTP Servers list on master switches are not being

propagated to local switches. (4944)

 If you are not doing any backend or local database authentication for

administrative users, Aruba recommends that you disable this feature by

using the aaa mgmt-authentication mode disable command.

 To restore the correct syslog facility level from a saved configuration file, do a

write erase before executing a copy flash: <saved-cfg> flash: default.cfg.

 ESI can be used within a multi-switch topology with master and local

switches and full redundancy. However, the following limitations apply in this

release.

1. On the WebUI, using the Back button to move back to previous

browser pages occasionally causes incorrect data, (blanks) to be

filled in some fields. This can result in ESI misconfigurations being

sent to the switch. (7618).

2. By design, in a multi-switch topology, client VLANs should not be

shared across switches. For example, client VLAN 100 cannot be

configured on switch lms1 and lms2 as doing so would cause the

AVF routes to be incorrect when the client moves between the

switches. Use separate VLANs instead on each switch and let

mobility take care of preserving the IP addresses of the client when

the client moves between switches.

3. By design, multi-switch topology will only work in route mode. Bridge

mode requires the AVF servers to be directly connected to the Aruba

switch as server up/down status is detected by the port link status.

4. In redundant switch configurations, do not use bridge mode. Use

route mode to keep redirected packets properly forwarded. (7912)