MSM7xx Controllers Release Notes v6.2.0.1

• The IP address for a VLAN interface cannot be set on a controller after it has been set up for
teaming (even after the controller has left the team).
• (Applies to teaming.) The primary controller on a team is unable to remove IDS AP authorization
on the secondary controllers.
• The MSM7xx Controller experiences high CPU utilization and eventually reboots when IMC or a
similar SNMP intensive software is used to manage the controller or a team of controllers.
• After a reboot, not all APs synchronized to a controller report as Already Seen.
• If RRM is enabled and a controlled AP is configured to use a reserved DFS channel when a radar
event is detected on the channel, the AP will shut down the radio instead of switching to a different,
available channel.
• VLANs cannot be added to a controller if the controller was removed from a team and set to
operate in standalone mode.
• Controllers are unable to team when the subscription plan is configured on the primary controller.
• (Applies to IMC WSM 5.2 or later.) Controllers in a team with several hundred APs may experience
trouble with connections to IMC.
• After running an RRM analysis, the list of detected foreign APs cannot be filtered by MAC address.
• APs appear grayed out on the Controller >> Controlled APs page.
• The IF-MIB SNMP MIB does not contain accurate descriptions for all interfaces.
• Management software such as PMM or IMC may not display all information properly.
• When an MSM7xx Controller is upgraded to a 6.x version from an older version where the Access
Point Name is not an available option for the System name (Controlled APs >> Configuration >
LLDP), the Access Point Name option should not appear as Enabled.
• HMAC tag secret is now configurable in the Internal Public Access web server.
• There is no RF Manager version 6.7 sensor software update for the MSM325 and MSM335
sensors. An error indicating that there is a version mismatch may be displayed, but the sensors
will continue to operate normally.
• The MSM7xx Controller sends RADIUS accounting-request messages without setting a value for
the "input/output packets" attribute.
• (Applies to teaming.) When a set of MSM7xx Controllers are configured to create a team and
communicate using the LAN port, the secondary controllers may fail to synchronize to the primary
controllers.
• RRM is not able to automatically configure the settings for a given radio unless 3 co-channel
neighbor radios are detected.
• When IDS is enabled, the following error messages are displayed on the system logs:
<ip-address>crit store-devices: <serial#> Unable to get type definition
for type=3a37463a32435d0d
<ip-address>crit store-devices: <serial#> assert:
payloadserializationapi.c PayloadGetSerializedSize 197
• The VSC>>Overview>Wireless Clients page fails to load when there are more than 3,000 users.
• When RRM is enabled, the following message appears multiple times on the system log, but does
not affect RRM operation:
warn rfmgr_sc (radio-tracking-node) Reporter 98:4B:E1:21:B0:A0 unknown
• (Applies to teaming.) When multiple teams of MSM7xx Controllers synchronize to a single iMC
server using WSM, the second and subsequent teams of MSM7xx Controllers fail to synchronize
with the iMC server.
Fixes 13