MSM7xx Controllers Release Notes v6.2.1.0

• When a VLAN is configured as an egress VLAN and also to be monitored by IDS, wireless traffic
is blocked.
• (Applies to teaming.) When a MAC list is deleted from a team member controller, the team member
controller may experience a reboot and the APs are synchronized to the team manager.
• (Applies to teaming.) When using teaming and WPA termination at the controller, wireless clients
that are connected through a team member controller might not get a DHCP lease.
• VLAN tag settings might not be removed after an AP reboot, causing new DHCP leases to be on
the incorrect VLAN or denied.
• The MSM7xx Controller might fail to apply VLAN settings to an AP when only the default VSC is
configured.
• (Applies to teaming.) The management tool might show that there are no APs synchronized on
the team member controllers, even though there are.
• The MSM7xx Controller can experience reboots if a VSC is configured to use WPA2 & PSK and
Terminate WPA at the controller is enabled.
• (Applies to controllers with a Premium licence installed) The MSM7xx Controller forwards incorrect
DHCP requests when more than 32 VSCs are configured.
• When an AP loses the communication channel with its controller and then reconnects, wireless
clients that are still connected to the AP through a Mobility Traffic Manager (MTM) VSC will have
their traffic blocked by the AP.
• If the % character is used when creating a profile name, random characters appear in the name
on the controller.
• (Applies to teaming.) When teaming is enabled, wired clients connected to the MSM317 ports
are not able to authenticate.
• Wireless clients connected to an access-controlled VSC might get a DHCP lease on the default
VLAN instead of the egress VLAN configured for the VSC.
• (Applies to teaming.) Wireless clients connected to an 802.1x non-access-controlled VSC are
disconnected when the team manager fails over to an alternate team manager.
• (Applies to teaming.) When a team manager recovers after a failover, some of the APs
synchronized to the alternate team manager automatically reset to synchronize back to the
recovered team manager.
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.
• (Applies to teaming.) When there are a large number of APs associated with a team of controllers,
IMC may incorrectly report that a controller team is unreachable. The situation should recover
after a short time.
• (Applies to MSM720 when authenticating several clients.) Teamed controllers Home displays
Authentication system without any value and Authenticated users as n/a. It is not possible to see
if the Authentication system is running and how many clients are authenticated.
• (Applies to teaming.) Due to an SNMPD issue, AP group names longer than 20 characters might
prevent IMC from properly communicating with the MSM7xx Controller. As a workaround, use
less than 20 characters when naming AP groups
• If Terminate WPA at the controller is enabled in a VSC, the controller may randomly reboot. As
a workaround, do not enable the Terminate WPA at the controller option.
10 Known issues