MSM7xx Controllers Release Notes v6.2.1.0
• Configuration backup using IMC fails for all MSM devices.
• The firmware updates feature does not work properly.
• The following misleading error message has been removed:
<CONTROLLER NAME> <IP ADDRESS> debug webredirect: SSL Error occurred
while reading: error:140760FCSL routines: SL23_GET_CLIENT_HELLO:unknown
protocol (336027900)
• When a controller location is set to Morocco, APs can fail to synchronize when a radio is set to
802.11n and the 5 GHz band is being used for local mesh.
• When user is authenticating with a remote trusted domain, if LDAP information cannot be retrieved
and a user group is not found, the user is still allowed to log in.
• An MSM7xx Controller can reboot during heavy simultaneous authentication traffic load.
• Whenever a wireless client roams from one AP to another using MAC Authentication, the client
session is terminated and does not restart until the client issues a new DHCP request.
• The MSM Controller continues to respond to DHCP requests on the LAN port after that feature
has been disabled.
• HTML authentication does not work if the user name contains spaces.
• The PayPal service does not accept guest credit card direct purchases.
• Using SOAP functions directed to a non-configured IP address causes SOAP to fail and add the
following error message to the controller log:
websoap: SOAP FAULT: SOAP-ENV:Client "Internal error" websoap: Unable
to communicate with IPRulesMgr, Timeout occurred.
• Using an external RADIUS server and an access controlled VSC can cause the MSM7xx Controller
to reboot.
• A wireless client moving to a wired connection is not asked to re-authenticate when using 802.1x
and an external Active Directory server, but should be.
• The SOAP command GetAuthenticatedUsers was deprecated. The new function
GetAuthenticatedUsersSessions can be used instead.
• In high capacity environments such as teaming with a large number of APs and with LLDP in use,
APs can randomly lose synchronization during high traffic periods.
• On a rare occasion, when a wireless client roams from one AP to another, the client traffic stops
until it moves to a new AP and the following error message appears on the controller log:
iprulesmgr: The RADIUS Accounting Request packet (id='17') received
contains a Called-Station-Id attribute (length='33') that isn't
recognized as being a MAC address, this may affect Location-Aware
related functionnalities such as restriction or incorrect VSC
assignment.
• When using HTML authentication, the Continue browsing link incorrectly redirects the wireless
client back to the home page.
• Added the following SOAP function to allow mapping of a network profile to a local mesh interface:
nl
AddVLANOnLocalMesh()
• Added the following SOAP commands to autonomous mode APs:
To configure the Station ID delimiter used in the Called-Station-Id content in the RADIUS
request:
nl
◦
UpdateVirtualSC8021XStationIdDelimiterAndCase
nl
8 Fixes










