MSM3xx / MSM4xx Access Points Release Notes

Transcription

1 MSM3xx / MSM4xx Access Points Release Notes Release Notes for the HP ProCurve MSM3xx / MSM4xx Access Points Introduction This document applies to these HP ProCurve MSM products: Model USA Japan WW MSM310 Access Point J9374A/B J9524A/B J9379A/B MSM310-R Access Point J9380A/B J9383A/B MSM317 Access Device J9422A J9423A J9423A MSM320 Access Point J9360A/B J9527A/B J9364A/B MSM320-R Access Point J9365A/B J9528A/B J9368A/B MSM325 Access Point with Sensor J9369A/B J9373A/B MSM335 Access Point with Sensor J9356A/B J9357A/B MSM410 Access Point J9426A/B J9529A/B J9427A/B MSM422 Access Point J9358A/B J9530A/B J9359A/B ( USA identifies USA versions, WW identifies worldwide versions for the rest of the world.) Release Release Release Release Release Release Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

2 MSM3xx / MSM4xx Access Points Release Notes 2 HP ProCurve Networking Release Contents General information Fixes Known issues General information Terminology The following terminology is used in these Release Notes and other 5.3.x documentation as follows:. Term AP Service controller The term access point is generally abbreviated as AP. Refers to the HP ProCurve MSM7xx Controllers. Documentation You can download documentation from the HP ProCurve Networking manuals Web page at: Updating software Customers with support contracts can obtain the latest software updates via Software Upgrade Managers (SUM). For more information on this process, visit the HP Software Releases & Media website at: Customers without support contracts who wish to obtain the latest software updates can purchase a software Care Pack service by contacting their local HP sales representative or authorized HP reseller. (Not applicable to MSM317.) For autonomous APs, update the software as described in the Firmware updates section of the MSM3xx / MSM4xx Management and Configuration Guide. For controlled APs including the MSM317, update the service controller software as described in the Firmware updates section of the MSM7xx Controllers Management and Configuration Guide. Once the service controller is updated, it automatically updates all of its controlled devices to the same software version.

3 MSM3xx / MSM4xx Access Points Release Notes 3 HP ProCurve Networking Regulatory update See also the regulatory information in the updated v5.3.5 Quickstarts available as described under Documentation above. REGULATORY NOTICE for European Union As of July 1st 2010, all wireless devices sold in EU countries and any countries that participate in the EU free market must meet stringent Dynamic Frequency Selection (DFS) requirements for radar detection and avoidance (EN v1.5.1). The MSM APs and the MSM7xx Controllers used to control and configure them are compliant. Other regulatory information In the USA and Canada, no DFS channels are available on Radio 1 of the MSM422 even when operating in legacy modes. Sensors and RF Manager Fixes Sensors (MSM320, MSM325, MSM335) at version are ONLY compatible with RF Manager version If you choose not to upgrade to RF Manager , do not upgrade a Sensor (directly, or via an MSM Controller) that will be used with RF Manager to version See also the MSM7xx Controllers Management and Configuration Guide. The following issue has been fixed since the previous release: X users may sometimes be unable to log in (Applies to autonomous APs.) It is not possible to disable IGMP using the management tool. The AP management tools displays a "page cannot be found" message and logs the user out. As a work around, the following CLI command can be used to deactivate IGMP: no dot11 igmp snooping-helper The MSM710, MSM422, MSM335, and MSM410 may unexpectedly restart L3 roaming may fail for wireless clients roaming between APs on different subnets and VLANs The CLI shows incorrect values for n multicast rate The automatic channel selection feature may cause excessive channel switching in environments where many APs are on the same channel X client stations are not deauthenticated if the user does not enter login credentials within a few minutes of receiving the login prompt. This can cause client stations to be unable to login via 802.1X Wireless protection for a VSC should be set to WPA2 or WPA+WPA2 to ensure the best compatibility and performance with n clients The MSM310 and MSM320 show too many wireless FCS RX errors on Radio 1.

4 MSM3xx / MSM4xx Access Points Release Notes 4 HP ProCurve Networking The CLI command show dot11 statistics client-traffic does not display the correct information for rates An internal problem is causing messages similar to the following to appear in the log: assert: retry.c IsTimeToRetry 52 (aretryinfo->mretrytype == RETRY_TYPE_CONSTANT && aretryinfo->mretry.minterval The ETSI DFS channels for EU countries are not permitted and have been removed for all revision B products with CM9 radio. See also the MSM Access Point Quickstarts (MSM317 only.) In some cases the MSM317 may frequently lose connectivity with the controller and fail to report statistics properly The SNMP object codot11pktsrate54 shows only receive rates. Transmit rates are missing In some cases, 802.1X authentication may not work properly (MSM410 only.) The MSM410 may stop advertising SSs with the following message added to the system log: ar5416getpendinginterrupts: received PCI FATAL interrupt (MSM317 only.) The MSM317 restarts when trying to retrieve debugging information on the Controlled APs > [AP] >> Tools > Debugging tools page The antenna icons (which indicate the mode of operation for an AP) on the Controlled APs >> Overview > Discovered APs page may intermittently disappear when the AP is handling a large amount of wireless traffic Under certain conditions, performance may be dramatically reduced for long periods of time when clients use power save mode (MSM317 only.) If a switch port is configured with a VLAN, after a few days the VLAN is lost and traffic gets sent untagged (MSM317 only.) When the MSM317 is configured to support six or more VSCs, wireless clients may be unable to connect to some of the VSCs When fragmentation was required on a tunnel interface due to the MTU size limitation of a tunnel, a UDP loop detected error was incorrectly being sent to the syslog If you define a custom wireless security filter using the %g placeholder, it will not work because the %g placeholder is not interpreted correctly by the AP (MSM317 only.) If an MSM317 switch port has MAC authentication enabled, or is bound to a VSC with MAC authentication enabled, after a few days, client stations are unable to authenticate through the port When handling a large amount of wireless traffic, an AP may lose its IP address and be unable to get a new one from a DHCP server Changing the time zone to GMT +8 on a controller results in APs not being able to synchronize (MSM317 only.) If the MSM317 Uplink port is connected to a network with a high traffic load, the MSM317 may lose synchronization with the controller Broadcast packets to or from a roaming client are sometimes dropped.

5 MSM3xx / MSM4xx Access Points Release Notes 5 HP ProCurve Networking (MSM422 only.) The MSM422 Ethernet port cannot be manually set to 1000 Mbps, even though the product supports this rate. If you set the port to Auto however, it will operate at 1000 Mbps when connected to another device operating at the that speed. Known issues The following known issues are present in this release: (Only MSM335 and MSM320/325.) The Wireless status light for a radio configured in Sensor mode does not turn on. This is true even when the sensor is enabled and operational (Only MSM422.) When radio 1 is set to n (5GHz) and radio 2 is set to a, and both are configured for local mesh, if one radio is set to a specific channel and the other is configured for auto- channel, both radios can end up to be on the same channel. Therefore, configure each radios for a specific (and different) channel or configure both radios for auto-channel (Only MSM317.) Making any configuration change on an MSM317 results in all wired 802.1X users erroneously having their connections terminated during the synchronization process (Only MSM317.) Applies only when at least one non-access-controlled VSC is configured with Ethernet Switch as the VSC ingress mapping, and one access controlled VSC is configured with a VLAN as the VSC ingress mapping.) This message may appear in the system log: err confighandl Failed to read ingress VLAN information for Virtual Service This message should be ignored (Only MSM317.) The MSM317 may generate a CFG_SYNC_FAILURE in the log when it synchronizes after a number of configuration changes have been made on the controller. The MSM317 will then restart, apply all changes, and operate normally When a third-party DHCP server is used to send alternate IP addresses for service controller discovery using DHCP Option 43, discovery will fail if third-party options appear in the list above the service controller IP addresses. To avoid this problem, ensure that the service controller IP addresses option is the first option in the list When configuring the Allowed wireless rates option under Virtual AP in a VSC, the user can disable support for all n data rates. If the VSC is only operating on n, then one non-msc rate must remain operational or the VSC will not function correctly The Axis2 SOAP client toolkit has issues dealing with some SOAP responses.

6 MSM3xx / MSM4xx Access Points Release Notes 6 HP ProCurve Networking If the radio is set to operate in n/g mode, it continues to provide support for b mode. You can fix this behavior by removing support for the b modes in each VSC (under Virtual AP > Allowed wireless rates) If there are more than 80 APs shown on the Neighbor page, the following message may be logged: "Radio 1's node table is full. Too many nodes in the surroundings (max is 256)." Under a very heavy wireless load, wireless client traffic can become very slow after several large file transfers. Terminating and reassociating client stations does not resolve the issue. The only solution is to restart the AP The online help for the CLI command "rcapture" is incorrect. The correct information is as follows: Syntax: rcapture -u URI [-c count] -i interface : Capture data on a port and send it to a file on an FTP server. Parameters: URI: Address of the FTP site and file where the trace will be saved, for example: ftp://user:pass@ftp.mysite.com/trace.pcap count: Number of packets to capture. interface: Interface to trace, where: eth0 = Internet port eth1 = LAN port wvlan0 = wireless port If you downgrade an AP from to and the AP is operating in controlled mode with both radios set to a on a specific DFS channel, the AP will not be able to synchronize with the controller. To enable the AP to synchronize, go to the radio page and select auto channel or pick a non-dfs channel When set to auto channel, and the radio picks a DFS channel, the unit will not scan a different channel unless the auto channel interval is set (MSM317 only.) If wired devices with static IP addresses are connected to the switch ports, the devices are able to communicate with each other regardless of the type of authentication that is enabled on the VSCs bound to the ports, as long as the ports have the same VLAN or no VLAN (untagged) If you plan to connect APs (as slaves) to a controller via local mesh, the APs must first be upgraded to the same software version that is running on the controller. For example, APs running version cannot connect to a controller as local mesh slaves when the controller is running If you define custom wireless security filters for a non-access-controlled VSC, they may not be applied after the AP is restarted.

7 MSM3xx / MSM4xx Access Points Release Notes 7 HP ProCurve Networking Revision B APs (J number ends with B ) do not support a Turbo mode. Setting a controlled AP to a Turbo mode and selecting DFS channel will cause the configuration to be reset.

8 MSM3xx / MSM4xx Access Points Release Notes 8 HP ProCurve Networking Release Fixes The following issue has been fixed since the previous release: (Applies when Auto Channel is being used.) APs attempt to re-allocate channels at the same time. This has been corrected by introducing a more random behavior. The first channel re-allocation will be done at a random time within plus or minus 50 percent of the configured interval. For example, if the configured interval is 24 hours, the first reallocation will occur anytime within 12 to 36 hours, and subsequent allocations will be done every 24 hours.

9 MSM3xx / MSM4xx Access Points Release Notes 9 HP ProCurve Networking Release Fixes The following issues have been fixed since the previous release: MAC Authentication does not support RADIUS assigned VLANs for wireless clients that are not access controlled (Only MSM422.) Radio 2 is has difficulty dealing with noise in the 2.4GHz range (Only MSM410 and MSM422.) When the n radio Wireless mode is set to g (not n/g or n/b/g), and Automatic power control is enabled, the radio stops transmitting (Only MSM317.) The MSM317 reboots or does not operate correctly when seeing a large number of stations on its Uplink port (Only MSM410 and MSM422 with v5.3.2 software.) Legacy clients connected to an n radio will experience poor performance.

10 MSM3xx / MSM4xx Access Points Release Notes 10 HP ProCurve Networking Release Fixes The following issues have been fixed since the previous release: X WPA2 clients that do not have a valid value for the Descriptor Type field are not able to connect (Only MSM410 and MSM422 (MAP-625).) In environments with substantial wireless interference, some client stations may experience low throughput when connected via n Spanning Tree Protocol is not supported on the MSM317 switch ports (Only MSM317.) Wireless throughput on higher channels may be reduced when the transmission power is set to maximum An AP with a valid sensor license will not report it to the controller, causing the controller to wrongly flag the AP as having a "License violation." When both L3 mobility and WPA2 opportunistic key caching are enabled on a VSC, and client stations frequently roam between several APs, the APs may unexpectedly restart.

11 MSM3xx / MSM4xx Access Points Release Notes 11 HP ProCurve Networking Release Fixes The following issues have been fixed since the previous release: (Only MSM410 and MSM422 / MAP-625.) Enabling Spectralink VIEW on an AP with an n radio causes the AP to become unresponsive When the main web management tool certificate is missing or corrupted the fallback mechanism to the default certificate does not work (Only European Union.) DFS (5 GHz range) channels 120, 124, and 128 have been removed due to regulatory changes When 802.1X authentication is enabled on a VSC it is now always mandatory. There is no longer the ability to choose whether 802.1X authentication is mandatory in a VSC. If you enable 802.1X authentication, wireless devices must be authenticated via 802.1X to access the network The spanning tree protocol s no longer enabled by default on APs operating in controlled mode Service Sensor (Security > Access control > Service sensor) does not work after a radio configuration change The 802.1x supplicant time-out value fails to be applied to EAP Request Identity packets The CLI command mac authenticate radius profile <radiusprofile> is missing (Only MSM422 / MAP-625.) A Local Mesh link between a Master node and Slave node does not always recover when the Master node is restarted On APs operating in b/g mode, if the Allowed Wireless Rates options are modified for a VSC, all supported wireless rates will be advertised as BSS Basic, which can cause problems for b-only clients attempting to connect (Only MSM410, MSM422 / MAP-625.) Performance has been improved in power saving mode when operating in n mode (Only MSM410, MSM422 / MAP-625.) Poor performance may be experienced with Intel n clients (4965, 5100 and 5300) when they have power-saving enabled.

12 MSM3xx / MSM4xx Access Points Release Notes 12 HP ProCurve Networking Release Fixes The following issues have been fixed since the previous release: For L2 mobility, the L2 Update frame sent upon client association/re- association is not sent on the VLAN associated with the client device For SOAP, the.net 2.0 wsdl.exe is unable to properly process the WSDL file (Applies only to MAP-625 with radio 1 set to n, with local mesh.) A software upgrade may require a subsequent manual reboot of the Alt-Master and/or Slave devices Radio 1 on a MAP-625 can stop transmitting. Must reset radio to recover On an AP in autonomous mode, it is not possible to delete a local mesh profile if it contains a VLAN in use by other resources (VSC or local mesh Profile) When multiple clients are connected, MAP-625 throughput is not as good as expected When MAC address filters are set to Allow for an access-controlled VSC, the clients that match a MAC address in the list are not able to associate with the SS and login to access the network After setting a DFS channel on a slave local mesh AP, the configuration update fails and the AP is never synchronized with the service controller (Applies only to n on the MAP-625.) Some n client devices occasionally lose IP connectivity The CLI command no ingress interface wireless <name> does not work If the real user name is returned in the RADIUS Access Accept via the User name RADIUS attribute, we now use this user name in the RADIUS accounting frames (start/ stop/interim) instead of the anonymous name The wireless range of the MAP-625 in 5GHz mode is less than expected A RADIUS-assigned VLAN does not override the AP egress VLAN Broadcast frames are not propagated correctly when VLANs are mapped to VSCs with 802.1X/RADIUS The BSS assigned to a given VSC, and therefore its SS, can change when a previous VSC is deleted. The BSS should remain constant When the connectivity is provisioned on a MAP running in controlled mode, the MAP wrongly tries to find the VLANs available on its wired port and wrongly attempts service controller discovery on the VLANs The public forwarding CLI command is missing.

13 MSM3xx / MSM4xx Access Points Release Notes 13 HP ProCurve Networking Changing a particular combination of radio settings sometimes reboots an AP or resets its configuration.