MSM7xx Controllers Release Notes v6.2.1.0

Although enabled in MSM software release 6.2.0.0, the following SOAP functions should not be used
on a controller team. If you attempt to use any of these functions when teaming is enabled, an error
is returned.
• ExecuteBackupUserAccountsPersistentData
• ExecuteUserAccountRenewPlan
• AddSubscriptionPlan
• DeleteSubscriptionPlan
• DeleteAllSubscriptionPlans
• UpdateSubscriptionPlanName
• UpdateSubscriptionPlanOnlineTimeState
• UpdateSubscriptionPlanValidityPeriodState
• UpdateSubscriptionPlanOnlineTime
• UpdateSubscriptionPlanValidityPeriodMethodState
• UpdateSubscriptionPlanValidityPeriodFor
• UpdateSubscriptionPlanValidityPeriodBetween
• UpdateSubscriptionPlanValidityPeriodFrom
• UpdateSubscriptionPlanValidityPeriodUntil
• UpdateSubscriptionPlanBooleanAttribute
• UpdateSubscriptionPlanIntAttribute
• UpdateSubscriptionPlanBandwidthLevelAttribute
Note on SOAP function UpdateUserAccountRemovalSettings
The Removal due to invalidity option of this function works in a teaming environment. However, the
Removal due to inactivity option should be avoided when teaming because it could cause the controllers
to wrongly remove active accounts.
Fixes
Version 6.2.1.0 includes fixes to the following issues:
• In dense environments, false "Radio down" alarms can be raised.
• In high traffic environments, DNS resolution by the controller can cause authentication delays and
require multiple retries by clients.
• If a user deletes a RADIUS profile and re-creates it with a new secret key, this setting does not
come into effect until another modification is made to the RADIUS profile.
• (Applies to teaming.) AP group names longer than 20 characters may prevent IMC from properly
communicating with the MSM7xx Controller.
• (Applies to teaming.) When inheritance is enabled, AP configuration changes do not propagate
to the team member controllers.
• The Internet network interface NAT option is disabled.
• The MSM7xx Controller restarts after a client tries to authenticate with the Windows 2008 R2
RADIUS server.
• A beacon containing an invalid channel occurs when multiple SSIDs are configured on the same
radio.
• VLAN tag mapping and uplink port data was not included in the output of the CLI show config
all command.
Fixes 7