HP MSM3xx / MSM4xx APs v5.7.2.0 Release Notes HP Part Number: 5998-4055 Published: January 2013 Edition: 1
Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Windows is a U.S. registered trademark of Microsoft Corporation.
Description Version: MSM v5.7.2.0 These Release Notes provide important release-related information. NOTE: In this document, except when identifying specific models, the generic term controller is used in place of MSM7xx Controller product names and the generic term AP is used in place of MSM3xx / MSM4xx AP product names. Product models This document applies to these HP products: Model WW Americas TAA Israel MSM430 J9651A J9650A J9654A J9653A MSM460 J9591A J9590A J9655A J9618A MSM466 J9622A J9621A J9656A J9619A MSM466-R J9716A J9715A J9718A WW identifies worldwide regions not otherwise explicitly named. Model WW USA Japan Israel MSM410 J9427A/B/C J9426A/B J9529A/B J9616A MSM422 J9359A/B J9358A/B J9530A/B J9617A MSM310 J9379A/B J9374A/B J9524A/B MSM310-R J9383A/B J9380A/B MSM317 J9423A J9422A J9423A MSM320 J9364A/B J9360A/B J9527A/B MSM320-R J9368A/B J9365A/B J9528A/B MSM325 J9373A/B J9369A/B MSM335 J9357A/B J9356A/B IMPORTANT: The Israel MSM466-R (J9718A) requires at least software version 5.7.1.0. Earlier versions cannot be used. Online documentation You can download documentation from the HP Support Website at: www.hp.com/support/manuals. Search by product name or part number. Software Updates and Licensing portal The Software Updates and Licensing portal provides access to the latest software updates to customers with a support contract. An HP Passport is required to access the Software Updates and Licensing portal at www.hp.com/go/hpsoftwareupdatesupport and it is available to customers who have purchased a maintenance and support agreement. Description 3
Mandatory channel change required prior to software upgrade; discontinue use of channel 132 Applies to these Americas/USA models: MSM410 (J9426A/B), MSM422 (J9358A/B), MSM430 (J9650A), MSM460 (J9590A), MSM466 (J9621A), MSM466-R (J9715A), MSM310 (J9374A/B), MSM310-R (J9380A/B), MSM320 (J9360A/B), MSM320-R (J9365A/B), MSM325 (J9369A/B), MSM335 (J9356A/B). IMPORTANT: PRIOR to upgrading to MSM software version 5.7.2.0, all applicable APs (autonomous or controlled) that are manually configured to use channel 132 must be either re-configured to use a different channel or be re-configured to use auto channel. This is required because channel 132 is no longer available for use. NOTE: Due to a problem with AP channel use validation, a banner similar to this may appear at the top of the Home screen: AP CNxxxxxxxx, Radio 1 channel configuration has been set to autochannel because the previously configured channel Auto is not supported by this version of software. The same message is added to the system log. These messages can be safely ignored. Updating software (Not applicable to MSM317.) For autonomous APs, update the software as described in the Software updates section of the MSM3xx / MSM4xx APs Configuration Guide. For controlled APs including the MSM317, update the controller software as described in the Software updates section of the MSM7xx Controllers Configuration Guide. Once the controller is updated, it automatically updates all of its controlled devices to the same software version. Downgrading software If you upgrade from version 5.7.0.x (or any other previous version) to version 5.7.1.x (or newer), and then you wish to return to the version that you had been running prior to upgrading, the configuration that you used originally with that version will still be available. If you have made configuration changes while using version 5.7.2.x, those changes will not be present when you downgrade to the previous version. If you factory reset your device after upgrading to version 5.7.2.x, your previous configurations will be lost, and when you downgrade to any previous version you will be in a factory reset state. MSM management tool now requires web browser with SSLv3 support NOTE: Starting with MSM software version 5.7.0.3, a web browser that supports SSLv3 is mandatory for running the MSM web-based management tool. SSLv3 is supported by Microsoft Internet Explorer 7 and 8 but must be enabled. Microsoft Internet Explorer 9 only uses SSLv3. Mozilla Firefox also supports SSLv3 but support may need to be enabled or you may need to update to a more recent version. 4 Mandatory channel change required prior to software upgrade; discontinue use of channel 132
RF Manager software and MSM software version compatibility RF Manager versions 5.9.x and 6.0.x work with MSM software version 5.5.x and higher. However, to use the WLAN Integration feature in RF Manager 6.0.x, the RF Manager and MSM software versions must be matched as follows: MSM7xx software version Compatible RF Manager version(s) Sensor-only devices (MSM415) Sensor devices version AP/Sensor combo devices (MSM320*, MSM325, MSM335) 5.7.1.0/5.7.1.1/5.7.2.0 5.7.0.2/5.7.0.3/5.7.0.4 6.0.177 or above 6.0.162 or above Upgraded automatically by RF Manager Upgraded automatically by MSM7xx Controller 5.5.3.x 6.0.157 or above 5.5.1.x/5.5.2.x 6.0.154 or above 5.5.0.x 5.9.203, 6.0.147 or above *MSM320 APs that have been upgraded to MSM325 RF sensor via HP MSM320 RF Sensor License J9384A. NOTE: If with RF Manager 6.0.x you choose to use mismatched software versions, you should first turn off the WLAN Integration in RF Manager. NOTE: Upgrading an MSM7xx Controller to v5.7.2.0 will also automatically upgrade any MSM325 and MSM335 Sensors it manages to MSM software v5.7.2.0 and sensor code v6.0.177. NOTE: The MSM415 Sensor has no MSM software dependency. It is managed and upgraded directly by RF Manager. Wireless feature changes (for 802.11n radios) NOTE: These changes only apply to APs with 802.11n-capable radios (MSM410, MSM422 (radio 1), MSM430, MSM460, MSM466, MSM466-R). Older APs (MSM3xx) are not affected. Wireless modes changed and restricted 802.11n access added With this release, MSM430 and MSM46x APs can now have their radios set to support legacy wireless modes 802.11a and 802.11b/g. This release also provides the ability for an 802.11n radio to be configured only to allow 802.11n clients to associate with it. The goal of this feature is to allow administrators to segregate 802.11n traffic to ensure that 802.11n clients do not experience performance degradation when sharing a wireless network with legacy (slower) client stations. This feature is supported on the following APs: MSM410, MSM422, MSM430, MSM460, MSM466, and MSM466-R. In order to support this functionality, the following changes have been made to the Radios configuration page: Supported wireless modes have been changed (see table on next page for details). A new parameter, Allow 802.11n clients only, has been added under Advanced wireless settings. RF Manager software and MSM software version compatibility 5
Wireless modes supported in this release Mode MSM410 MSM422 MSM430 MSM460 Radio 1 Radio 1 Radio 2 Radio 1 or 2 when in Monitor mode Mode MSM466 and MSM466-R Radio 1 (Monitor only) Radio 2 (except Monitor) (except Monitor) 6 Wireless feature changes (for 802.11n radios)
Wireless modes no longer supported in this release The following wireless modes are no longer supported in this release: 802.11b 802.11g 802.11n (5 802.11n (2.4 802.11n/g When upgrading, radios that are currently configured to use these modes are automatically converted to the new modes as described in the next section. Wireless mode conversion when upgrading When upgrading to this release, existing wireless settings are converted to the new wireless settings as follows: Configuration before upgrade Configuration after upgrade Wireless mode 802.11b 802.11b/g 802.11g 802.11a 802.11n (5 802.11n/a 802.11n (2.4 802.11n/g 802.11n/b/g Wireless mode Allow 802.11n clients only (not available) (not available) (not available) (not available) Enabled Disabled Enabled Disabled Disabled Local mesh wireless modes changes Wireless mode changes also affect configuration of local mesh profiles for controlled APs when selecting Controlled APs >> Provisioning > Connectivity. AP New wireless modes Radio 1 Radio 2 MSM410 MSM422 802.11n/a n/a 802.11b (2.4 Wireless feature changes (for 802.11n radios) 7
MSM430, MSM460 MSM466, MSM466-R 802.11g (2.4 NOTE: When upgrading to this release, existing wireless settings for local mesh are also converted to the new wireless settings as described in the table on the previous page. The wireless modes available for local mesh configuration are automatically determined by the wireless operating mode that is set. Local mesh is only supported between two APs when the radios on each AP are configured with identical wireless modes. For example, if AP 1 is set to 802.11a, then AP 2 must also be set to 802.11a and not 802.11n/a. Multicast rates for 802.11n radios In order to allow 802.11n clients to take advantage of High Throughput data rates for multicast traffic, the list of allowed multicast rates now takes into account the Allow 802.11n clients only setting of the radio. Supported multicast rates in this release are as follows: MSM410, MSM422, and MSM430 Wireless mode Allow 802.11n clients only 802.11 n/b/g (2.4 802.11 b/g (2.4 Enabled 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, and MCS 0 to MCS 15. Default: 24 Mbps n/a 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, and MCS 0 to MCS 15. Default: 11 Mbps n/a Disabled 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0. Default: 24 Mbps 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0 Default: 24 Mbps 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0. Default: 11 Mbps 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 8.0, 24.0, 36.0, 48.0, 54.0 Default: 11 Mbps 8 Wireless feature changes (for 802.11n radios)
MSM460, MSM466, and MSM466-R Wireless mode Allow 802.11n clients only 802.11 n/b/g (2.4 802.11 b/g (2.4 Enabled 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, and MCS 0 to MCS 23. Default: 24 Mbps n/a 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, and MCS 0 to MCS 23. Default: 11 Mbps n/a Disabled 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0. Default: 24 Mbps 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0. Default: 24 Mbps 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, and MCS 0 to MCS 23. Default: 11 Mbps 1.0, 2.0, 5.5, 11.0, 6.0, 9.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0. Default: 11 Mbps Wireless support changed for Israel The 5 GHz band cannot be used outdoors in Israel. Therefore on the MSM466-R, when the country code is set to Israel: Radio 1 will be disabled and all options will be greyed out. The setting for Operating mode will be changed to Monitor. Radio 2 will still be configurable, but Wireless mode will only contain options for 2.4 GHz operation. NOTE: The 5 GHz band can still be used indoors in Israel, therefore operation of the MSM466 is not affected by this change. Wireless feature changes (for 802.11n radios) 9
CLI command changes Changes have been made to the CLI to support the new wireless modes and the new Allow 802.11n clients only parameter. dot11 Syntax: dot11 <mode> <frequency> The syntax of this command has not changed. However the wireless modes supported by the <mode> option are now as follows: a: selects 802.11a in the 5 GHz frequency band. an: selects 802.11n + 802.11a in the 5 GHz frequency band. bg: selects 802.11b + 802.11g in the 2.4 GHz frequency band. bgn: selects 802.11n + 802.11g + 802.11b in the 2.4 GHz frequency band. To maintain backward compatibility with the previous version of this command, the dot11 command will automatically map old settings for the mode option to the new settings as follows: If mode is set to 802.11b 802.11g 802.11n-5 GHz 802.11n-2.4 GHz 802.11gn It is mapped to 802.11bg 802.11bg 802.11an 802.11bgn 802.11bgn The dot11 command does not allow setting the operating frequency of radio 2 to 5 GHz when the country code of an AP is set to Israel. dot11 allowedclients This new command in the Wireless Interface context allow a radio to be configured to only support 802.11n client stations. Syntax: dot11 allowedclients <clients> Where <clients> is: n only: configures the radio to only allow 802.11n clients to associate. all: configures the radio to allow all clients to associate. provisioning local mesh type Syntax: provisioning local mesh type <type> The syntax of this command has not changed, however the wireless modes supported by the <type> option are now as follows: 802.11a 802.11n+a 802.11b+g 802.11n+b+g 10 CLI command changes
To maintain backward compatibility with the previous version of this command, this command will automatically map old settings for the type option to the new settings as follows: If type is set to 802.11b 802.11g It is mapped to 802.11b+g 802.11b+g Fixes The following issues are fixed in this release: APs might drop packets for Cisco 792x IP phones, which can cause poor audio quality or disconnecting calls. (Applies to MSM410, MSM420, MSM460, MSM466, MSM466-R.) When operating in 802.11b/g mode, the radio transmits using all data rates, regardless of which rates are configured on the VSC page. The MSM422 sometimes restarts spontaneously. The MSM320 sometimes restarts spontaneously. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) The AP may restart spontaneously, and clients sometimes disconnect and are unable to reconnect. (Applies to MSM430, MSM460, MSM466, MSM466-R.) When using Automatic channel selection on radios configured for 2.4 GHz operation, the radio will only choose from channels 1, 6, and 11. The Channel exclusion list cannot be used to have Automatic channel select from other available channels (3, 5, 9, and 13, for example). When using Subnet-based mobility, wireless clients may be unable to get an IP address. (Applies to MSM430, MSM460, MSM466, MSM466-R.) Due to an internal error, the AP restarts. An alternate Master in local mesh using both radios set to auto channel updates the second radio with the wrong channel information. The management tool automatically refreshes on occasion, causing Javascript errors and high memory usage. When a RADIUS VSC is removed, the controller should remove all references to the RADIUS server from the configuration file to prevent APs from failing synchronization to a controller during a firmware upgrade. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) Under certain circumstances, transmitting AMSDU (Aggregated Mac Service Data Unit) data can cause the radio to stop working properly, requiring an AP restart. (Applies to MSM410 in controlled mode.) Output from the SOAP command GETDHCPFixedLeases has unreadable ASCII characters. (Applies to MSM430, MSM460, MSM466, MSM466-R.) When wireless clients enter Powersave mode, the AP may run out of transmission buffers, causing the radio to stop forwarding packets. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) The SNMP command to disassociate users does not work. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) APs send data to clients in Powersave mode. AP names longer than 13 characters are not displayed properly on some management tool pages. (Applies to MSM430, MSM460, MSM466, MSM466-R.) A race condition on the UDP traffic tunnel may cause the AP to reboot when wireless clients connect to an access controlled VSC. Fixes 11
(Applies to MSM430, MSM460, MSM466, MSM466-R.) Autopower does not increase radio power after neighboring APs on the same channel are no longer present. (Applies to all MSM APs in Autonomous mode.) The fourth WEP key of the VSC configuration page does not have its length validated, and when configured with a key of invalid length, clients will not be able to connect using standard size passwords. (Applies to MSM422 acting as a Slave in a Local Mesh configuration.) If the AP was directly provisioned before being adopted by a controller, the AP will not synchronize with the controller. This may be caused by a specific configuration where the alternate Master only has the Local Mesh provisioning profile enabled rather than having an additional Local mesh profile for the slave(s). (Applies to MSM430, MSM460, MSM466, MSM466-R.) APs may drop client traffic and need to be rebooted for clients to regain network access. When a new browser tab is opened, the new page may fail to load. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) Due to a software design change, 802.11 LEAP authentication (some devices use terminology such as Network EAP ) is no longer supported. For Autonomous APs, if the Accounting Delay option is set to 0, then the accounting delay is disabled (Default). If the Accounting Delay option is set to any value higher than 0, then the accounting delay is inserted. When DST is enabled on the system with timezone set to Newfoundland (GMT-03:30), the time erroneously increases by one minute instead of one hour. Known issues These issues are present in this release: (Applies to MSM430, MSM460, MSM466, MSM466-R.) When L3 Mobility is enabled, an AP is adopted by the controller and an error similar to following may appear in the system log: eapolserver: <serial number> Error while getting BSSID for virtual AP: <AP name> eapolserver: <serial number> WIRELESS_essid_get_status(wvlan0) cfgerr:(22) syserr:(invalid argument) As a workaround, avoid using L3 Mobility or enable it after all APs have been adopted. High bandwidth multicast streaming may cause high CPU levels in the MSM317. APs may randomly stop advertising a VSC, preventing wireless clients from connecting. As a workaround, restart the AP. When Autopower is enabled, the performance of radio 1 on the MSM422 drops. As a workaround, disable Autopower. (Applies to MSM430, MSM460, MSM466, MSM466-R.) If Radio 1 is disabled, channel 1 cannot be used on Radio 2. As a workaround, enable Radio 1. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) Automatic channel selection in the 2.4 GHz band only works on channels 1, 6, and 11. If you add one or more of these channels to the exclusion list then the AP will remain on channel 1. (Applies to MSM410, MSM430, MSM460, MSM466, MSM466-R.) If a radio Channel setting of Automatic is enabled and all APs (affected by this issue) happen to boot up at the same time, for example after a power outage, then they are likely to end up on the same channel. This will happen mostly with autonomous APs. APs managed by an MSM7xx Controller are less likely to experience this. As a workaround, APs can be restarted/re-synchronized at specific intervals or fixed channels can be selected. (Applies to MSM430, MSM460, MSM466, MSM466-R.) The APs support a maximum of 125 WPA2 clients per radio. 12 Known issues
Regardless of the actual 802.11 standard and speed, sflow always reports the speed as 11 Mbps and the standard as 802.11b. (Applies to MSM410.) You must add an extra VLAN to pass traffic over a local mesh link in controlled mode. In earlier MSM410 software versions you could discover and pass data over the same VLAN. You now cannot send data over the discovery VLAN. (Applies to MSM422, MSM430, MSM460, MSM466, MSM466-R.) The Band Steering feature will have no impact when the 5 GHz radio operates on a DFS channel. As a workaround, select a non-dfs channel, or if using auto-channel, exclude all DFS channels from the available channel list. (Applies to MSM430, MSM460, MSM466, MSM466-R.) When a local mesh master node switches to a new channel, it may take slave nodes up to two minutes to follow and synchronize on the new channel. Known issues 13