Release Notes 4.5.0.39

Release Notes, Version 4.5.0.39
10
802.1X/WPA authentication service is configured correctly within the 700wl Series
system and for each component (access point, remote RADIUS server, and client). For
instance:
- Shared secret and IP address of the remote RADIUS server is correct
- Access Control Server is a client on the remote RADIUS server configuration
If all of the above is correct and the client still cannot authenticate, restart the built-in
RADIUS server by rebooting the Access Control Server, or contact ProCurve Technical
Support for assistance. (19884)
QoS classification cannot be performed on encrypted (L2TP, PPTP, IPSec) client data.
Encrypted data paths consist of inner and outer tunnels, where the outer tunnel is the
encryption tunnel and the inner tunnel contains the data packets. QoS classification is
currently performed on the outer tunnel. (19871)
In a redundant system, if there is loss of connectivity between the preferred primary Access
Control Server and the secondary Access Control Server, the secondary will promote itself to
acting primary. If clients log on to an Access Controller connected to the new acting primary
Access Control Server and then connectivity is restored between the preferred primary and
secondary Access Control Servers, the restored preferred primary Access Control Server may
have a different view of the network than actually exists. This could result in inaccurate
information being displayed in the Client Status page. Note that clients do not experience a
disruption of service and clients will reappear in the Client Status page once their rights
expire or when they logout and log back in. (19808, 19677)
In a redundant system, 802.1X/WPA Authentication Service configuration is sometimes not
replicated on the secondary Access Control Server when redundancy is enabled after the
802.1X/WPA Authentication Service is configured. The workaround is to enable redundancy
and let the Access Control Servers peer up before configuring the 802.1X/WPA
Authentication Service. (19793)
In a redundant system, if the secondary Access Control Server is disconnected from the
network, an Access Controller will maintain connectivity to the preferred primary Access
Control Server and will remove the secondary Access Control Server’s IP address from its
configuration under the assumption that redundancy has been disabled. The Access
Controller will not know about the secondary Access Control Server unless the preferred
primary Access Control Server is shutdown, at which point the preferred primary Access
Control Server will send a message telling the Access Controller to try to connect to the
secondary Access Control Server and will include the IP address of the secondary Access
Control Server.
If the preferred primary Access Control Server is disconnected from the network, the Access
Controller connects to the secondary Access Control Server and keeps trying to connect to
the preferred primary until eventually after several unsuccessful attempts to connect, the
Access Controller removes the preferred primary IP address from its configuration under the
assumption that redundancy has been disabled. (19758)
When the Access Control Server is configured to use the internal Access Controller’s HTTP
proxy server, clients will not be able to access web sites that use HTTPS. (19749)
Clients using a Real IP with L2TP or PPTP authentication that are authenticated through an
Access Controller connected to a Cisco Catalyst 2950 have their IP address associated with
that Access Controller by the Catalyst 2950. If the clients log out and attempt to log in again
to another Access Controller connected to the same Cisco Catalyst 2950, or roam to another