MSM3xx, MSM4xx, HP 425, and HP 517 APs Release Notes v6.4.0.0

• 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.
• 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.
• (Applies to HP 517.) The Apple Bonjour features (multicast handling and user profiles) are not
supported on the HP 517 wired ports.
• (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 MSM410, HP 425, MSM430, MSM460, MSM466, MSM466-R.) 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.
• (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R in autonomous mode.) After
a reboot or a modification of the radio configuration, some error messages may be generated
by rfmgr_ap. These messages do not indicate a malfunction and can be ignored. The services
offered by the radio will work properly.
• (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R in controlled and autonomous
mode, and the HP 425 in controlled mode.) A Dynamic Local Mesh Slave configured in Promiscuous
Mode will not establish a link even in the presence of multiple Masters. As a workaround, specify
a Local Mesh Group ID in the Local Mesh Profile.
• (Applies to MSM410, HP 425, MSM430, MSM460, MSM466, MSM466-R in controlled mode.)
Changing the Wireless > Radios > Neighborhood Scanning parameters can lead to false radio
down alarms.
• (Applies to MSM320 and MSM325 in autonomous mode.) After upgrading to firmware 6.0,
MSM320 and MSM325 sensors working in autonomous mode may present GUI instability when
a radio or radios are setup to work in Network Detector mode. Downgrade to 5.7.x or previous
firmware version if sensor mode operation is desired.
• (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R in controlled and autonomous
mode, and the HP 425 in controlled mode.) Scan ratios with a value above 1% can have a
negative effect on iOS 4 and iOS 5 iPad devices. As a workaround, lower the scan ratio to 1%
or less if there are performance issues on the network.
• (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R in controlled and autonomous
mode, and the HP 425 in controlled mode.) The SNMP OIDs that report information about the
configuration of the Autochannel features “COLUBRIS-DEVICE-WIRELESS-MIB
coDevWirIfStaAutoChannelEnabled” and “coDevWirIfStaAutoChannelInterval” may report incorrect
information.
• (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.
Known issues 9