MSM7xx Controllers Release Notes v6.4.0.0

• When a single VSC egresses user traffic over different VLANs (depending on AP location) and a
client roams from one AP to another, the controller may erroneously detect the user as a Mobility
Traffic Manager (MTM) visitor and block their traffic.
• (Applies to teaming.) Teaming failover causes Mobility Traffic Manager (MTM) clients traffic to
stop, even after the AP is adopted by an alternate team manager controller.
• (Applies to teaming.) If using teaming while an access controlled VSC with 802.1x authentication
and the WPA termination option is enabled, wireless clients might not be able to connect via a
team member controller.
• (Applies to teaming.) APs adopted by a team member controller can appear to be in the pending
state on the management tool, even though the APs are operating and providing service.
• When using HTML authentication, the Continue Browsing link on the Welcome page erroneously
redirects an authenticated user back to the login page.
• The SNMP MIB for LLDP returns the LldpChassisIdSubtype MAC address in an incorrect format.
• When configuring an 802.1x VSC using SOAP, it is not possible to set the Station ID delimiter
or the Station ID MAC.
• After a software upgrade, an AP might drop packets from the user VLAN over the AP tagged
management VLAN.
• When configuring a VSC, if the wireless protection key source is changed to use PSK, the Station
ID delimiter and Station ID MAC case configuration fields disappear from the management tool.
When configuring a VSC using SOAP, if the wireless protection key source is set to use PSK, it
is not possible to set the Station ID delimiter or the Station ID MAC.
• The SNMP process causes high CPU and high memory usage, which can cause the controller to
reboot.
• (Applies to teaming.) The team manager controller can lose its default route when a static IP
address is configured on the Internet port.
Known issues
These issues are present in this release:
• (Applies to teaming.) If the team manager fails, the interim team manager will enable RRM severe
interference mitigation and AP load balancing, even if these options were disabled by the
administrator. As a workaround, promote the interim team manager to team manager, and then
disable undesired options.
• On the Overview > Wireless clients page, the scroll bar might be missing (or partially hidden)
when viewed with Mozilla Firefox. The page displays properly when viewed with Microsoft Internet
Explorer.
• Synchronizing AP configuration changes can be slower if any rates are unchecked in Allowed
wireless rates. As a workaround, do not uncheck any rates in Allowed wireless rates, or wait for
the synchronization to complete.
• (Applies to MSM720.) A timeout can occur when attempting to obtain the Sysinfo file from an
MSM720 team manager when the team manager is under heavy load.
• (Applies to Teaming.) Adding two or more new controllers to a team at the same time can result
in a deadlock situation with the controllers stuck in an uploading configuration state. As a
workaround, remove and then rediscover the controllers.
• If system-wide Auto-channel/Auto-power is enabled, it is not possible to configure the Auto-channel
and Auto-power Interval for an AP radio participating in local mesh.
• A local mesh master AP is unable to maintain a link to slave APs due to a DFS-initiated channel
change. As a workaround, do not use DFS channels when using local mesh.
16 Known issues