MSM7xx Controllers Release Notes v6.2.0.1

• (Applies to MSM410, HP 425, MSM430, MSM460, MSM466, MSM466-R.) When Intrusion
Detection System (IDS) is enabled, AP radios on that (team of) controller(s) should not be configured
in Access Point and Local Mesh or Local Mesh only. As a workaround, IDS must be disabled on
the controller if Access Point and Local Mesh or Local Mesh only operation is required.
• (Applies to MSM422.) When an AP is configured to egress traffic on a given VLAN, the wireless
clients connecting to the AP fail to receive an IP address from the external DHCP server.
• (Applies to HP 425, MSM410, MSM422, MSM430, MSM460, MSM466, MSM466-R.) An
access controlled VSC using MAC-based authentication with the MAC filtering ALLOW option
enabled, allows clients to connect. As a workaround, use only the DENY option.
• If using teaming while an access controlled VSC with 802.1x authentication and the WPA
termination option is enabled, wireless clients may not be able to connect via a team member
controller. As a workaround, disable WPA termination or use WPA termination with Mobility
Traffic Manager (MTM) enabled and access control disabled.
• When IMC establishes a connection to the MSM7xx Controller, the following error messages are
displayed on the system log:
err pmmclient: setVLANSubsectionIndexFromVLANNetworkProfileName: Unknown
vlan name 'Internet port network'.
err pmmclient: setVLANSubsectionIndexFromVLANNetworkProfileName: Unknown
vlan name 'LAN port network'.
err pmmclient: DB: Unable to prepare the SQL statement.
err pmmclient: Could not get data from the database.
These messages can be safely ignored.
• MTM is not supported when APs are adopted by controllers using NAT.
• iPads/iPods/iPhones cannot authenticate using the secondary RADIUS server with the default
configuration. As a workaround, reduce the retry interval in the RADIUS Profile configuration to
5 seconds.
• Re-deploying an AP from one controller to another controller might generate false attacks reported
by IDS on the original controller. As a workaround, reboot the controller after removing the AP.
• In some cases, the network subnet information about rogue APs reported by the intrusion detection
system (IDS) is incorrect. The IP address will display as 0.0.0.0.
• Clients using the PPTP VPN server might experience connectivity issues when sending large packets.
• The SNMP OIDs that report information about the configuration of the Autochannel features
“COLUBRIS-DEVICE-WIRELESS-MIB coDevWirIfStaAutoChannelEnabled” and
“coDevWirIfStaAutoChannelInterval” may report incorrect information on the MSM410, MSM430,
MSM460, MSM466, and MSM466-R.
• (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R in autonomous mode.) The
Neighborhood Scanning feature configured to scan on all channels only scans on channels within
the regulatory domain's approved channel list rather than all channels in the respective band.
For example, with the location set to the United States, Neighborhood Scanning will not scan
channels 12 or 13 since they are not part of the U.S. regulatory domain. This is true in both the
2.4 GHz and 5 GHz bands. There is no workaround.
• Wireless clients connected to a VSC that is directly mapped to a VLAN are unable to reach wired
clients on the same VLAN.
Known issues 15