MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 12 HP ProCurve Networking
Release 5.3.0
Fixes
The following issues have been fixed since the previous release:
ID Description
34073 For L2 mobility, the L2 Update frame sent upon client association/re- association is not
sent on the VLAN associated with the client device.
34660 For SOAP, the .NET 2.0 wsdl.exe is unable to properly process the WSDL file.
34974 (Applies only to MAP-625 with radio 1 set to 802.11n, with local mesh.) A software
upgrade may require a subsequent manual reboot of the Alt-Master and/or Slave
devices.
35097 Radio 1 on a MAP-625 can stop transmitting. Must reset radio to recover.
35223 On an AP in autonomous mode, it is not possible to delete a local mesh profile if it
contains a VLAN in use by other resources (VSC or local mesh Profile).
35385 When multiple clients are connected, MAP-625 throughput is not as good as expected.
35388 When MAC address filters are set to Allow for an access-controlled VSC, the clients
that match a MAC address in the list are not able to associate with the SSID and login to
access the network.
35473 After setting a DFS channel on a slave local mesh AP, the configuration update fails and
the AP is never synchronized with the service controller.
35485 (Applies only to 802.11n on the MAP-625.) Some 802.11n client devices occasionally
lose IP connectivity.
35520 The CLI command no ingress interface wireless <name> does not work.
35647 If the real user name is returned in the RADIUS Access Accept via the User name
RADIUS attribute, we now use this user name in the RADIUS accounting frames (start/
stop/interim) instead of the anonymous name.
35676 The wireless range of the MAP-625 in 5GHz mode is less than expected.
35778 A RADIUS-assigned VLAN does not override the AP egress VLAN.
35865 Broadcast frames are not propagated correctly when VLANs are mapped to VSCs with
802.1X/RADIUS.
36148 The BSSID assigned to a given VSC, and therefore its SSID, can change when a
previous VSC is deleted. The BSSID should remain constant.
36231 When the connectivity is provisioned on a MAP running in controlled mode, the MAP
wrongly tries to find the VLANs available on its wired port and wrongly attempts service
controller discovery on the VLANs.
36295 The public forwarding CLI command is missing.
To Next Page
Loading...
Need help?
General
