HP MSM310 How to use

5998-0557 5.3.5
© Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
MSM3xx / MSM4xx Access Points
5.3.5 Release Notes
Release Notes for the HP ProCurve MSM3xx / MSM4xx Access Points
Introduction
This document applies to these HP ProCurve MSM products:
(“USA” identifies USA versions, “WW” identifies worldwide versions for the rest of the world.)
Release 5.3.5 - - - - - - - - - - - - - - - - - - - - - - - - 2
Release 5.3.4 - - - - - - - - - - - - - - - - - - - - - - - - 8
Release 5.3.3 - - - - - - - - - - - - - - - - - - - - - - - - 9
Release 5.3.2 - - - - - - - - - - - - - - - - - - - - - - - 10
Release 5.3.1 - - - - - - - - - - - - - - - - - - - - - - - 11
Release 5.3.0 - - - - - - - - - - - - - - - - - - - - - - - 12
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

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 2HP ProCurve Networking
Release 5.3.5
Contents
General information - - - - - - - - - - - - - - - - - - - - - - - - - - - 2
Fixes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3
Known issues - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5
General information
Terminology
The following terminology is used in these Release Notes and other 5.3.x documentation as follows: .
Documentation
You can download documentation from the HP ProCurve Networking manuals Web page at:
www.hp.com/go/procurve/manuals.
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:
www.hp.com/softwarereleases/releases-media2/SUM/How_to_be_a_SUM_customer.htm.
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.
Term Description
AP The term “access point” is generally abbreviated as AP.
Service controller Refers to the HP ProCurve MSM7xx Controllers.

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 3HP 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 301.893 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
Sensors (MSM320, MSM325, MSM335) at version 5.3.5 are ONLY compatible with RF Manager
version 5.9.203. If you choose not to upgrade to RF Manager 5.9.203, do not upgrade a Sensor
(directly, or via an MSM Controller) that will be used with RF Manager to version 5.3.5. See also
the MSM7xx Controllers Management and Configuration Guide.
Fixes
The following issue has been fixed since the previous release:
ID Description
42387 802.1X users may sometimes be unable to log in.
43076 (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
44396 The MSM710, MSM422, MSM335, and MSM410 may unexpectedly restart.
44894 L3 roaming may fail for wireless clients roaming between APs on different subnets and
VLANs.
44905 The CLI shows incorrect values for 802.11n multicast rate.
45142 The automatic channel selection feature may cause excessive channel switching in
environments where many APs are on the same channel.
45239 802.1X 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.
45542 Wireless protection for a VSC should be set to WPA2 or WPA+WPA2 to ensure the best
compatibility and performance with 802.11n clients.
45806 The MSM310 and MSM320 show too many wireless FCS RX errors on Radio 1.

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 4HP ProCurve Networking
46012 The CLI command show dot11 statistics client-traffic does not display the correct
information for 802.11 rates.
46019 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
46293 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.
46383 (MSM317 only.) In some cases the MSM317 may frequently lose connectivity with the
controller and fail to report statistics properly.
46512 The SNMP object “coDot11PktsRate54” shows only receive rates. Transmit rates are
missing.
46554 In some cases, 802.1X authentication may not work properly.
47634 (MSM410 only.) The MSM410 may stop advertising SSIDs with the following message
added to the system log:
ar5416GetPendingInterrupts: received PCI FATAL interrupt
47773 (MSM317 only.) The MSM317 restarts when trying to retrieve debugging information on
the Controlled APs > [AP] >> Tools > Debugging tools page.
47831 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.
47916 Under certain conditions, performance may be dramatically reduced for long periods of
time when clients use 802.11 power save mode.
47980 (MSM317 only.) If a switch port is configured with a VLAN, after a few days the VLAN is
lost and traffic gets sent untagged.
48057 (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.
48594 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.
48666 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.
50105 (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.
50485 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.
50806 Changing the time zone to GMT +8 on a controller results in APs not being able to
synchronize.
51473 (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.
51940 Broadcast packets to or from a roaming client are sometimes dropped.
ID Description

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 5HP ProCurve Networking
Known issues
The following known issues are present in this release:
52009 (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.
ID Description
ID Description
33604 (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.
34173 (Only MSM422.) When radio 1 is set to 802.11n (5GHz) and radio 2 is set to 802.11a,
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.
38305 (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.
38621 (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.
38750 (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.
38984 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.
39804 When configuring the Allowed wireless rates option under Virtual AP in a VSC, the
user can disable support for all 802.11n data rates. If the VSC is only operating on
802.11n, then one non-MSC rate must remain operational or the VSC will not function
correctly.
39994 The Axis2 SOAP client toolkit has issues dealing with some SOAP responses.

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 6HP ProCurve Networking
45094 If the radio is set to operate in 802.11n/g mode, it continues to provide support for
802.11b mode. You can fix this behavior by removing support for the 802.11b modes in
each VSC (under Virtual AP > Allowed wireless rates).
48316 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)."
49182 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.
52305 The online help for the CLI command "rcapture" is incorrect. The correct information is
as follows:
Syntax:
rcapture -u URI [-c count] -i interface
Description:
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:[email protected]/trace.pcap
count: Number of packets to capture.
interface: Interface to trace, where:
eth0 = Internet port
eth1 = LAN port
wvlan0 = wireless port
52840 If you downgrade an AP from 5.3.5 to 5.3.1 and the AP is operating in controlled mode
with both radios set to 802.11a 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.
52846 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.
52848 (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).
53553 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 5.3.3 cannot connect to a controller as local mesh slaves when the
controller is running 5.3.5.
54095 If you define custom wireless security filters for a non-access-controlled VSC, they may
not be applied after the AP is restarted.
ID Description

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

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 8HP ProCurve Networking
Release 5.3.4
Fixes
The following issue has been fixed since the previous release:
ID Description
42885 (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 re-
allocation will occur anytime within 12 to 36 hours, and subsequent allocations will be
done every 24 hours.

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

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 10 HP ProCurve Networking
Release 5.3.2
Fixes
The following issues have been fixed since the previous release:
ID Description
39248 802.1X WPA2 clients that do not have a valid value for the Descriptor Type field are not
able to connect.
39292 (Only MSM410 and MSM422 (MAP-625).) In environments with substantial wireless
interference, some client stations may experience low throughput when connected via
802.11n.
40332 Spanning Tree Protocol is not supported on the MSM317 switch ports.
40434 (Only MSM317.) Wireless throughput on higher channels may be reduced when the
transmission power is set to maximum.
41519 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."
42595 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.

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 11 HP ProCurve Networking
Release 5.3.1
Fixes
The following issues have been fixed since the previous release:
ID Description
16439 (Only MSM410 and MSM422 / MAP-625.) Enabling Spectralink VIEW on an AP with an
802.11n radio causes the AP to become unresponsive.
16564 When the main web management tool certificate is missing or corrupted the fallback
mechanism to the default certificate does not work.
18450 (Only European Union.) DFS (5 GHz range) channels 120, 124, and 128 have been
removed due to regulatory changes.
18452 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.
19087 The spanning tree protocol s no longer enabled by default on APs operating in
controlled mode.
36647 Service Sensor (Security > Access control > Service sensor) does not work after a
radio configuration change.
36991 The 802.1x supplicant time-out value fails to be applied to EAP Request Identity
packets.
36998 The CLI command mac authenticate radius profile <radiusprofile> is missing.
37054 (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.
37097 On APs operating in 802.11b/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 802.11b-only clients attempting to connect.
38307 (Only MSM410, MSM422 / MAP-625.) Performance has been improved in power saving
mode when operating in 802.11n mode.
38531 (Only MSM410, MSM422 / MAP-625.) Poor performance may be experienced with Intel
802.11n clients (4965, 5100 and 5300) when they have power-saving enabled.

MSM3xx / MSM4xx Access Points 5.3.5 Release Notes 12 HP ProCurve Networking
Release 5.3.0
Fixes
The following issues have been fixed since the previous release:
ID Description
34073 For L2 mobility, the L2 Update frame sent upon client association/re- association is not
sent on the VLAN associated with the client device.
34660 For SOAP, the .NET 2.0 wsdl.exe is unable to properly process the WSDL file.
34974 (Applies only to MAP-625 with radio 1 set to 802.11n, with local mesh.) A software
upgrade may require a subsequent manual reboot of the Alt-Master and/or Slave
devices.
35097 Radio 1 on a MAP-625 can stop transmitting. Must reset radio to recover.
35223 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).
35385 When multiple clients are connected, MAP-625 throughput is not as good as expected.
35388 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 SSID and login to
access the network.
35473 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.
35485 (Applies only to 802.11n on the MAP-625.) Some 802.11n client devices occasionally
lose IP connectivity.
35520 The CLI command no ingress interface wireless <name> does not work.
35647 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.
35676 The wireless range of the MAP-625 in 5GHz mode is less than expected.
35778 A RADIUS-assigned VLAN does not override the AP egress VLAN.
35865 Broadcast frames are not propagated correctly when VLANs are mapped to VSCs with
802.1X/RADIUS.
36148 The BSSID assigned to a given VSC, and therefore its SSID, can change when a
previous VSC is deleted. The BSSID should remain constant.
36231 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.
36295 The public forwarding CLI command is missing.

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