44-10-0320-33

5.2.4

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx 5.2.4 Release Notes

Introduction
These Release Notes apply to the HP ProCurve / Colubris Networks access points as follows: MSM310 / MAP-320, MSM310-R / MAP-320R, MSM320 / MAP-330, MSM320-R / MAP-330R, MSM335 / MAP-630, MSM422 / MAP-625.

HP ProCurve Product Naming - - - - - - - - - - - - - - - 2 Release 5.2.4 - - - - - - - - - - - - - - - - - - - - - - - - 3 Release 5.2.3 - - - - - - - - - - - - - - - - - - - - - - - - 8 Release 5.2.2 - - - - - - - - - - - - - - - - - - - - - - Release 5.2.1 - - - - - - - - - - - - - - - - - - - - - - 10 12

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

HP ProCurve Product Naming

As of October 1st, 2008, Colubris Networks has been acquired by HP ProCurve. HP ProCurve has begun integrating the Colubris product line into its ProCurve Networking product portfolio (www.procurve.com/news/colubris-10-01-08.htm). Colubris product names are being changed to their equivalent HP ProCurve product names. In this 5.2.4 release, the management tool user interface and online help use the new HP ProCurve product names. However, the documentation continues to use the Colubris product names.
Note: SOAP and SNMP MIBs retain the Colubris naming so you do not need to change

your existing SOAP and MIB usage. The Colubris Networks product names and their corresponding new HP ProCurve product names are as follows:

Colubris name
MSC-5100 MultiService Controller MSC-5200 MultiService Controller MSC-5500 MultiService Controller MSC-3200 MultiService Controller MSC-3200R MultiService Controller MSC-3300 MultiService Controller MSC-3300R MultiService Controller MAP-320 MultiService Access Point MAP-320R MultiService Access Point MAP-330 MultiService Access Point MAP-330R MultiService Access Point MAP-330 AP+Sensor MultiService Access Point MAP-625 MultiService Access Point MAP-630 AP+Sensor MultiService Access Point WCB-200 Wireless Client Bridge Visitor Management Tool RF Manager 1500 Enterprise RF Manager 1300 Basic RF Planner

HP ProCurve name
MSM710 Controller MSM730 Controller MSM750 Controller MSM313 Access Point MSM313-R Access Point MSM323 Access Point MSM323-R Access Point MSM310 Access Point MSM310-R Access Point MSM320 Access Point MSM320-R Access Point MSM325 Access Point MSM422 Access Point MSM335 Access Point M111 Client Bridge Guest Management Software RF Manager 100 IDS/IPS system RF Manager 50 IDS/IPS system RF Planner

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

Release 5.2.4
Contents
General information - - - - - - - - - - - - - - - - - - - - - - - - - - 3 Fixes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5 Known issues - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

General information
Terminology
The following terminology is used in these Release Notes and other 5.2.x documentation as follows:

Term
AP Service controller

Description
The term access point is generally abbreviated as AP. Refers primarily to the HP ProCurve MSM7xx controllers / Colubris MSC-5xxx controllers. May also refer to the HP ProCurve MSM313 and MSM323 integrated services access points / Colubris MSC-3000 series controllers. Specifics are used where necessary.

Updating to COS 5.2.4 software

Update the AP to COS 5.2.4 as described in the Firmware updates section of the MAP Admin Guide.
Note: All pre-5.2.4 devices updated to 5.2.4 will use the new HP ProCurve product names

in the management tool as identified in HP ProCurve Product Naming on page 2.

Regulatory update
Colubris Networks products at COS 5.2.2 or higher are compliant with this Radar Avoidance regulation: (Europe) EN301893 v1.4.1 (5GHz DFS). In the USA and Canada, no DFS channels are available on radio 1 of the MSM422 / MAP-625 even when operating in legacy modes. As of COS 5.2.4, the 802.11a Turbo mode (local mesh) is certified for use in the following countries (For the MSM422 / MAP-625, this only applies to Radio 2):
Argentina Canada Egypt Hong Kong Lithuania Norway Slovenia Australia China Estonia Hungary Luxembourg Panama Sweden Azerbaijan Colombia Finland Iceland Macau Philippines Switzerland Belgium Costa Rica France India Malaysia Poland Taiwan Belize Cyprus Georgia Iran Mexico Portugal Turkey Bolivia Czech Republic Germany Ireland Monaco Puerto Rico Brazil Denmark Greece Italy Netherlands Singapore Brunei Dominican Republic Guatemala Liechtenstein New Zealand Slovakia Venezuela

United Kingdom United States

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

Sensors and RF Manager

Notice:
MSM325 / MAP-330 sensors and MSM335 / MAP-630 sensors at COS 5.2.4 are ONLY compatible with RF Manager version 5.5.187. If you choose not to upgrade to RF Manager 5.5.187, DO NOT upgrade a sensor, that will be used with RF Manager, to COS 5.2.4. See also, the RF Manager 5.5 Release Notes.

Information for APs operating in controlled mode

Notice:
At COS 5.1 and above, Controlled mode is the default AP operating mode. Operation, including status light behavior, differs from Autonomous mode. Controlled mode did not exist prior to COS 5.1. APs that are upgraded from a release prior to COS 5.1, boot into their default Autonomous mode. Please familiarize yourself with all Controlled mode information in this section and in the MSC-5000 Series Admin Guide.

Controlled mode lets you take advantage of centralized management of APs at the service controller and plug-and-play installation. When operating in controlled mode: The AP must be installed in conjunction with an MSC-5000 series service controller. AP network connections must be made using port 1 only. The AP management tool provides only limited configuration changes. The AP must be configured and managed through the service controllers management tool. For more information see the MSC-5000 Series Admin Guide. For information on AP status lights, see the Working with controlled APs chapter of the MSC-5000 series Admin Guide.

MAC addressing
APs in controlled mode have a MAC address whose last digit is incremented by 1 over the Ethernet Base MAC address that is printed on the AP label and applies when the AP is in autonomous mode. For example, an AP with an Ethernet Base MAC address that ends with the digits 8C use this address for autonomous mode, but when in controlled mode, the last digit of the MAC address changes from 8C to 8D. These MAC address changes make it necessary to perform some additional tasks.

Switching operation modes

When switching an AP from controlled mode to autonomous mode or vice versa, delays in the mode switch of up to several minutes may occur unless you clear the ARP (address resolution protocol) cache on your computer after switching modes. To clear the ARP cache in Windows, for example, open a command prompt and enter the following command: arp -d

Using a DHCP server with static leases based on MAC address

When upgrading APs on an existing controlled-mode network to COS 5.2.1 or higher, it will be necessary to adjust your DHCP server static lease configuration by incrementing the last digit of the MAC address by 1 for all affected APs. For example, if an AP at COS 5.1 was configured in your DHCP server with MAC 00:03:52:BF:03:8C, you must edit that last digit so that it becomes 00:03:52:BF:03:8D.

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

When adding a factory-delivered AP at COS 5.2.1 or higher to a controlled-mode network, you must similarly configure the static lease in your DHCP server with a MAC address whose last digit has been incremented by 1 over the Ethernet Base MAC address printed on the AP. For example, if the AP label shows MAC 00:03:52:BF:03:8C, configure your DHCP server with MAC address 00:03:52:BF:03:8D.

Local mesh in controlled mode

Ignore any statements in the documentation indicating that only autonomous APs can be used for local mesh. Both autonomous and controlled APs support local mesh. For information on working with controlled APs and local mesh, look for the Configuring and Provisioning Local Mesh in Controlled Mode Technical Note on the Colubris Extranet (http://extranet.colubris.com).

Fixes
The following issues have been fixed since the previous release:

ID
17662

Description
(Applies only to MSM422 / 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. (Applies only to MSM422 / MAP-625.) With a compatibility (n/a, n/bg) wireless mode selected, AND a legacy client is present on the same channel, the MAP-625 802.11n protection mechanism overrides the powersave behavior. This results in the MSM422 / MAP-625 dropping its data rate because of communications interruption with the client. The data rate keeps decreasing until it drops below MCS7, at which point it starts working normally. With a provisioned MSM422 / MAP-625 with radio 1 in A mode, it will not establish a local mesh link with the master. Radio 1 on a MSM422 / MAP-625 can stop transmitting. Must reset radio to recover. (Applies only to the MAP-330R.) It is not possible to set a specific radio channel. The MSM422 / MAP-625 does not reject 802.11n clients using TKIP encryption. TKIP is deprecated for 802.11n and should be rejected. The MSM422 / MAP-625 reverts to legacy data rates when VSC bindings are changed. When multiple clients are connected, MSM422 / MAP-625 throughput is not as good as expected. Wireless clients can no longer connect when Spectralink VIEW is enabled. 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 802.11n on the MSM422 / MAP-625.) Some 802.11n client devices occasionally lose IP connectivity. The CLI command no ingress interface wireless <name> does not work.

17742

17750 17785 17890 17993 18022 18073 18122 18161 18173 18208

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

ID
18336

Description
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 MSM422 / 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. 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 CLI command public forwarding is missing. Changing a particular combination of radio settings sometimes reboots an AP or resets its configuration. Service Sensor (Security > Access control > Service sensor) does not work after a radio configuration change.

18365 18467 18554 18920

18984 19008 19332

Known issues
The following known issues are present in this release:

ID
7150 7668 10716

Description
VLAN attributes returned by a RADIUS server are dropped when MAC authentication is enabled on a VSC. 802.1x user cannot re-authenticate in the event the RADIUS accounting STOP message is not acknowledged by the RADIUS server. The Wireless > Neighborhood feature alters the beacon timestamps when it is executed. This can cause some wireless devices to lose connectivity and re-associate. The workaround is to turn off neighborhood scanning. In certain cases, the APs may not appear in in the Satellite list. This occurs when the AP can only communicate with the service controller through a VLAN interface. (Only applies to the MAP-630 and MAP-330.) Do not attempt to change the radio 1 channel and the radio 2 channel at the same time (error message "The same frequency exists on other radios" will appear). Instead, change the radio 2 channel first and Save. Then change the radio 1 channel and Save. (Applies only to a MAP-330 and MAP-630 with sensor operating in controlled mode.) An AP operating in controlled mode may not be able to synchronize with a service controller when more than one service controller is discovered on the network (it assumed that the priority setting of each service controller is different).

12857 13075

13246

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

ID
16285

Description
(Applies only to MAP-630 and MAP-330.) 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. (Applies only to MSM422 / MAP-625.) 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. (Applies to Provisioning of Autonomous APs.) If you switch an Autonomous AP to Controlled mode using the management tool (Maintenance > System > Switch to Controlled mode), the AP will switch to controlled mode but will also use the Autonomous provisioned elements in its discovery process 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.

16857

17674

18076

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

Release 5.2.3
Fixes
The following issues have been fixed since the previous release:

ID
10463

Description
If administrator authentication for the management tool is set to use a RADIUS server, the failover to a secondary RADIUS server does not occur when the primary server does not respond. DFS on Local Mesh is supported on 802.11a/b/g radios (no DFS support is provided on 802.11n radios). Previous workarounds are no longer required. If a user authenticates with 802.1x/RADIUS (e.g., WPA Enterprise) and the RADIUS server is down or sends no response, and then the client disassociates, the AP continuously retries the RADIUS request at the configured interval. (Applies to local mesh links.) When there is a security mismatch, the local mesh link is still allowed to come up. With the fix, it will not connect to a remote node if the security does not match. The local mesh security settings, when changed, were not always taking effect, requiring the link to be manually disabled and re-enabled. APs that are rebooted at the same time are synchronizing their scanning for open channels and as a result are picking the same channels. Multiple APs end up on the same channel. In a controlled mode local mesh network, if there was a large amount of data going through the mesh, the service controller would not always be able to retrieve the state of APs, or push configuration changes. High gain antennas can cause false DFS radar hits. The Antenna gain is now configurable on the Wireless > Radio page and must be adjusted to the actual antenna gain when operating on DFS channels. (Applies only to MAP-630 and MAP-330.) In some cases, the Sensor or Network Detector function of the MAP-330 or MAP-630 would not work after the provisioned IP address of the AP was changed. (Applies only to MAP-630 and MAP-330 with local mesh.) Saving radio 2 causes the link on radio 1 to temporarily go down. The link with the slave is no longer responding and it is consequently brought down. The link is re-established automatically and remains up and running from then on. (Applies only to the MAP-630 in controlled mode.) The Network Detector feature does not work. (Applies only to APs running in autonomous mode.) On the Local Mesh configuration screen, clicking the Force link button will initiate a connection with the node, but this node will deny the connection under certain conditions (even if it is configured to accept forced connections).

12856 12969

13048

13135 15378

15391

16014

16040

16162

16177 16205

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

ID
16250

Description
(Applies only to the MAP-630 in controlled mode.) The MAP-630 includes internal antennas in its flaps and it supports the connection of external antennas. However, only the internal antennas can be selected when provisioning an AP to operate over local mesh. Affects page Controlled APs >> Provisioning > Connectivity on the service controller and page Provisioning > Connectivity on the MAP-630. When a wired local mesh link is deleted, the group considers there to be too many links and no longer accepts any connections. (Applies only to 802.1X authentication.) When the Access controller shared secret was changed on the AP, a reboot was necessary for the change to take effect. The system name is now displayed in the management tool top banner. It is configured by the System name item on the Management > SNMP page. It defaults to the device serial number. When performing a configuration backup, the default file name is now named config_(system name).txt, where (system name) is configured by the System name item on the Management > SNMP page. It defaults to the device serial number. Shared secret configuration changes only apply after a restart. It is not possible to start a packet trace from the SNMP TOOLS MIB. On the local mesh configuration page, the preshared key for TKIP and AES is no longer displayed in clear text. A radio could not be switched to sensor mode if its mode was set to 802.11a Turbo. It is not possible to seamlessly upgrade from local mesh autonomous to controlled mode. (Applies only to the MAP-625 and MAP-630.) In some cases, when connected to a gigabit switch, the Ethernet receiver can get stuck at boot up, causing communication to fail. Clicking the Provisioning menu of an unprovisioned AP does not yield expected results. Ethernet 802.1X traffic was not allowed to go through through a local mesh link. Now, if STP is disabled on the bridge, this type of traffic will be forwarded as well. There was a problem with the WMM-Power Save implementation which caused the client to wake up often, causing, for example, increased battery drain on voice handsets. If the SOAP management interface is disabled and then re-enabled, it will no longer start automatically on power up. IGMP roaming support (IGMP snooping helpers) is not working when encryption is enabled on the VSC. The IGMP request is sent by the AP prior to key negotiation completion. This affects roaming users receiving a multicast stream when APs are connected to a switch with IGMP snooping enabled. (Applies to the SNMP Maintenance MIB.) Object certificateExpiryDate returns the wrong date.

16276 16318 16347

16348

16350 16572 16772 16981 17092 17299

17389 17404 17460

17510 17536

17653

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

10

Release 5.2.2
This section is not applicable to the MSM422 / MAP-625.

Fixes
This section is applicable to the MAP-630, MAP-320, MAP-320R, MAP-330, and MAP-330R. The following issues have been fixed since the previous release:

ID
16330

Description
The same 802.11 association ID could be used by two clients simultaneously, if one of them had been previously de-authenticated due to encryption errors. This could cause problems with the 802.11 power saving mechanism and reporting discrepancies in the SNMP MIBS. In the SNMP MIB, the iftype for the third radio on the MAP-630 is set to other whereas it should be set to ieee802.11. A voice call between two phones associated with the same AP can fail if one of the phones temporarily moved to an adjacent AP and then came back to the original AP. This only occurs if the phone traffic is mapped to a VLAN. An XML deserialization problem causes an interoperability problem with Microsoft .NET 2.0, and possibly all other versions of .NET. The AP will never scan channels not available in the US, such as channels 12 and 13 (802.11b) or channels 100-140 (802.11a). When using autochannel, these channels will therefore always be selection candidates regardless of their current usage. When using local mesh, a slave will never find a master using one of these channels. If a MAP-630 or MAP-330 in controlled mode is configured as a dedicated Network Detector (no radios configured as sensor) reboots, the AP will not reconnect to the RF Manager. Encrypted (TKIP only) static local mesh links are not always re-established correctly. With local mesh when RADAR is detected on a DFS channel on the master node while a slave node is in auto-channel mode, the link does not fully recover. With a dynamic local mesh link, performance would be low and the link could be lost in less-than-perfect RF conditions. On the WCB-200, in similar conditions, many frames could be dropped. Untagged broadcast traffic was forwarded to VSCs even if the VSCs were mapped to a VLAN. This problem could also cause SSID mis-classifications in RF Manager. The CLI command to enable the Spectralink VIEW support was missing. Changing allowed wireless rates causes AP errors when syncing, causing the AP to restart and mapconf errors to appear in the system log.

16400 16420

16525 16560

16567

16580 16588 16624

16627 16687 16697

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

11

ID
16718 16720 16730 16777 16849 17036

Description
When the AP radio was set to local mesh it would continue scanning in the background on a regular basis, causing lost frames. Using the web-management tool, it is not possible to replace the X.509 certificate with another certificate that has the same certificate subject or name (DN). The AP could reboot if the radio or VSC configuration was changed while the AP was receiving a continuous wireless stream of data from a client. A local mesh slave node may stop trying to connect to a master node if it had been previously refused. Support for the Network EAP 802.11 authentication method, allows Cisco client bridges to connect with WPA2 EAP-TLS. Even though an AP could be configured to accept 255 associations, the maximum number of associated clients could only be 252. APs now accepts a maximum of 255 associations across all VSCs. The default NTP time servers have been changed to 0.colubris.pool.ntp.org and 1.colubris.pool.ntp.org.

17065

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

12

Release 5.2.1
This section is not applicable to the MSM422 / MAP-625.

Contents
New features and enhancements - - - - - - - - - - - - - - - - - - - - - 12 Fixes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13

New features and enhancements

COS 5.2.1 contains new features and enhancements as described here:

ID
12638 13298 13318 14115 14143 14553

Description
The Network trace interface has been improved to run more than one capture in parallel, on different ports. The promiscuous feature has been added to local mesh. Local mesh profiles can now be added and removed. New CLI commands are introduced to support this, along with an updated interface in the management tool. Available wireless data rates can now be configured independently for each VSC. It is now possible to configure a different RADIUS server for authentication and for accounting, when using 802.1X or MAC based authentication. The Colubris DHCP Option 60 (vendor Class Identifier) information is now included in the AP DHCP Discovery packet. It was already being sent as part of the DHCP Request packet. Additional authentication types have been added to the SOAP/XML interface. In addition to HTTPS X.509 certificate authentication, it is now possible to use HTTP authentication, with or without SSL. For local mesh, 802.11a Turbo rates (108Mbps) (channel bonding) are now available in certain countries. The bridge spanning tree function (STP) is now turned off during the discovery and join when a controlled AP is connecting to a service controller. This improves compatibility on certain networks. STP can still be enabled in the configuration for the AP and will take effect once the configuration is applied (AP in synchronized state). APs that are not-yet managed by a service controller can be provisioned directly through the APs Provision menu.

14650

14853 16180

n/a

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

13

ID
n/a

Description
WMM PS (Wi-Fi Multimedia Power Save) support has been added. Wi-Fi-Power Save description from the Wi-Fi Alliance: Wi-Fi mobile devices require advanced power-save mechanisms to offer a rich user experience for voice, audio, and video applications. WMM (Wi-Fi Multimedia) Power Save extends the battery life of Wi-Fi devices by increasing the efficiency and flexibility of data transmission. It is an addition to WMM, the technology that enables Quality of Service (QoS) functionality in Wi-Fi networks by prioritizing traffic from different applications. WMM Power Save has been optimized for mobile devices running latency-sensitive applications such as voice, audio, or video, but can benefit any Wi-Fi device. WMM Power Save uses mechanisms included in the IEEE 802.11e amendment and is an enhancement of IEEE 802.11 legacy power save, which was designed for data applications. With WMM Power Save, the same amount of data can be transmitted in a shorter time and using fewer frames, while allowing the Wi-Fi device to remain longer in a low-power, dozing state. For additional information see: http://www.wi-fi.org/files/wp_12_WMM%20Power%20Save%20White%20Paper.pdf

Fixes
The following issues have been fixed since the previous release:

ID
10222 11672

Description
To obtain the best wireless performance (such as for voice applications) wireless neighborhood scanning should be kept disabled (the default). (Applicable to local mesh.) Changing from one radio to another in a local mesh group using TKIP/AES requires that the local mesh Master AP be rebooted for the change to take effect. Autochannel runs at 12-hour intervals even if the interval is disabled. (Applies only to local mesh.) The security settings are not refreshed when a new radio is selected. A VLAN over local mesh link is not created when the local mesh link is already up. If this occurs, reboot the AP. (Applies only to some Windows Vista clients.) An AP in controlled mode can lose all its 802.1X associated clients when a 802.1X client does many associations / disassociations in a short period of time. An AP in controlled mode could lose all its 802.1X associated clients, when a 802.1X based client does many associations/ disassociation in a short period of time, as seen with a specific Windows Vista client.

12975 13085 13180 13190

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

14

ID
14068

Description
An L2 broadcast frame is now sent out by the AP whenever a client reassociates with the AP. The source MAC address of the L2 frame is set to the wireless client, and allows bridges on the network to learn the new location of the client. Not all clients use the REASSOC management frame when moving to a different AP, so now a similar L2 frame is send for normal ASSOC management frames as well. This change corrects long delays that could occur on frame forwarding after a client roamed using only the ASSOC method. Local mesh links recover too slowly after a Master failover. (Applies only to South Korea.) When a radio is in sensor mode, the 802.11a band is not available. Spectralink phones configured with WMM and WPA-TKIP experience unwanted deauthentications. An unexpected system reset occurs if a client sends an invalid wireless packet (length of packet is shorter than what is set in the packet). It is not possible to start a trace on a VLAN interface built over a local mesh link. (MAP-320 only.) Spanning tree protocol on VLANs is not functioning and therefore never detects and disables any VLAN interface in the VLAN bridge even if spanning tree protocol traffic is sent on the VLAN. APs can lose data from an Intel 3945 wireless client when WMM is enabled. Time of Day scanning in auto-channel selection uses a 12 hour clock, resulting in two scans per day, 12 hours apart. When two wireless clients are mapped to the same VLAN and communicating with each other, and one of them moves to another access point and the wireless client does not send an 802.11 deauthentication to the original AP, the communication is lost. This affected only some clients. (Applies to SNMP MIB.) A walk of MIB COLUBRIS-VIRTUAL-AP-MIB may fail when there was more than one VSC configured. When the Video or Voice queues have a high traffic load, the application can experience multiple retries. The AP and its users are no longer reachable on a VLAN if the bridge has blocked one of the two Ethernet ports or a local mesh link, and if these ports are used and part of a redundant network. With local mesh, lower performance is experienced when when Channel is set to Automatic. Autochannel with a scan interval of less than 24 hours stops scanning after 24 hours. The AP sometime restarts when its clients are using WPA/TKIP and WMM (QoS frames). If a controlled mode AP needs to rediscover the service controller, the status lights do not properly indicate that an AP discovery is occurring.

14399 14525 14549 14632 14701 14703

14792 14824 14986

15033 15210 15223

15287 15453 15648 15702

5.2.4 Release Notes:

HP ProCurve MSM3xx/MSM422 / Colubris MAP-3xx/MAP-6xx

15

ID
15796

Description
(Applies only to the MAP-330 concerning the COLUBRIS-IEEE802DOT11.my MIB.) A row is missing (for radio 2) in tables coDot11PhyDSSSTable and coDot11PhyOFDMTable when one radio is set to the 2.4GHz band and the other is set to the 5GHz band. When upgrading from 5.1, the local mesh discovery interval is changed from 10 seconds to 1 second. This change greatly improves the local mesh network convergence time. Wireless user and AP statistics do not show accurate noise values. (Applies to the wireless neighborhood list in Monitor mode.) APs are aged out of the list too quickly.

15977 15986 15987