MSM7xx Controllers Release Notes v6.2.0.1

Fixes
Version 6.2.0.1 includes a fix to the following issue:
• (Applies to HP 425.) The potential for a flash memory error was detected in the software. This
error has a low probability of occurrence, but if it does occur, the unit might reboot.
Version 6.2.0.0 includes fixes to the following issues that were seen with MSM720, MSM760, and
MSM765 zl controllers:
• IP routing cache does not flush, potentially causing the controller to behave sluggishly after 24
hours of use.
• An MSM7xx Controller does not send disassociation messages from a Bradford Sentry authenticator
to a wireless user.
• IDS does not allow users to manually change a Rogue AP into an Authorized AP.
• The AP Load Balancing feature in RRM does not function properly, causing an uneven distribution
of clients amongst APs.
• When Band Steering is enabled on a VSC and the number of clients connecting to an AP is 100
or more, all association requests are rejected.
• MSM APs are unable to be reclassified as Authorized on IDS.
• Aeroscout tags connected through an WDS AP can not be seen in MobileView.
• Wireless clients streaming data or downloading large files may get disconnected, and the following
messages are shown in the system log:
iprulesmgr: Keep-Alive for station (ip-address='5.5.5.10') failed
iprulesmgr: Terminating session (session-time='198') for user
• With Mobility Traffic Manager (MTM) enabled on one VSC, users connecting to a non-MTM-enabled
VSC may get blocked trying to reach other network resources.
• When teaming is enabled, the following message appears in the system log:
GetNewDatabaseConnectionObject: Cannot create the database connection
object for <IP addr>'
This message can be ignored.
• The number of wireless clients shown on VSC >> Overview > Wireless clients is not accurate.
• Enabling L3 roaming may cause the controller to reboot intermittently.
• On a wireless deployment with 200 or more access points, after a firmware upgrade to 6.0.1.0,
the APs can not synchronize back to the MSM7xx Controllers.
• (Applies to teaming.) When a team is configured to authenticate users against an external Active
Directory server, it shows an empty Active Directory “joined” status. The authentications remain
fully functional, however.
• When an access-controlled VSC gets the Access Control option removed, the DHCP Server and
DHCP relay configuration options are not disabled.
• When trying to downgrade firmware from Version 6.x.x to Version 5.7.x using the Command
Line Interface, the controller reboots but does not actually downgrade the firmware.
• The controller GUI becomes unresponsive, and the system log reports the following message:
monitord Stopping [3,8]: 'webs' [pid 917, up for 188709 sec(s)]
• When MTM is enabled on a VSC, wireless users are unable to reach network resources (navigate).
• When upgrading from Version 5.5.x to 6.0.1.3, the Zero Config feature is disabled.
• When a VLAN interface is created on the primary controller of a team, the secondary controllers
cannot synchronize to the team.
12 Fixes