MSM7xx Controllers Release Notes v6.4.0.0

(Applies to HP 517.) The Apple Bonjour features (multicast handling and user profiles) are not
supported on the HP 517 wired ports.
The SysInfo file cannot be downloaded when the controller has joined an Active Directory domain
that is configured to use IPv6. As a workaround, do not configure the Active Directory server for
IPv6 when used with an MSM7xx Controller.
When using option Public IP addresses for Guest Access, and there are more wireless clients than
available public IP addresses, the wireless clients with a public IP address already assigned might
lose their address to a new wireless client. As a workaround, make sure that you provision enough
public IP addresses to cover the largest anticipated number of concurrent users.
The % character causes random characters to appear in the name on the controller when used
in creating a profile name. As a workaround, do not use the % character when creating a
profile name.
(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.
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.
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.
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 17