Release Notes 4.5.0.41

RELEASE NOTES, VERSION 4.5.0.41
KNOWN ISSUES AND BEHAVIORS
The following are issues that are known to exist with this software version. The number in
parentheses following the description is an internal tracking number.
• Cisco Access Point using the Aironet series of protocols when connect downstream of an
Access Controller could originate traffic with the same source MAC address on multiple
VLANs or VLANs and untagged networks. This may trigger undesirable behavior on the
Access Controller causing it to detect the Access Point as roaming between VLANs. The
behavior of clients downstream of this Access Point is undefined. In order to avoid this
behavior it is recommended that either the Cisco Aironet series of protocols are disabled or
that these series of protocols exhibiting this behavior are blocked through traffic filters that
may be configured on the AP. (21090)
• Windows XP and 2000 clients in NAT mode may not accept a DHCP lease if a domain name
is not defined on the system. (21088)
• An Access Controller may erroneously display an IP address of 42.0.0.2 on the LCD panel.
(21055)
• After migrating to version 4.4, a 1000Base-SX port is described as Ethernet as opposed to
1000Base-SX or 1000Base-SX full-duplex. (20918)
• In a redundant Access Control Server configuration an Access Controller may not show a
connection to an Access Control Server if the secondary Access Control Server is not
reachable. (20578)
• Under certain circumstances the uptime may displayed incorrectly which can be corrected by
manually setting the time and a system reboot. (20825)
• If many Kerberos clients continually log in or out through L2TP every 10-15 seconds
(approx. 120 authentications per 60 seconds totally), some authentications may fail. The
Windows XP clients which fail to authenticate due to system error #691 (i.e. user
name/password invalid in domain) will succeed in the subsequent attempts and ping real-IP
peer client. (21054)
• If an Access Controller is downgraded from version 4.4 to 4.1, several disklabel warning
messages are issued. These errors are harmless and only appear when version 4.1 is started.
(20823)
• Exporting the Rights configuration does not export the list of files used in Logon
Customizations. (19914)
• If bandwidth limits are modified in an Access Policy used by an encrypted client, and if the
encrypted client has completed a roam before the bandwidth limits were changed, the new
bandwidth limits will be displayed correctly in the Client Details page when the “Refresh
User Rights Now” is selected. However, the bandwidth limit changes will not take affect until
the encrypted client logs off and logs on again. If the encrypted client does not roam during
the bandwidth limit changes, the changes take affect immediately after the “Refresh User
Rights Now” is selected. (19910)
• In the 802.1X/WPA authentication service with the built-in RADIUS server configured as a
proxy, if a client keeps getting authentication failures, verify the following:
8