Release Notes: Version WT.01.
© Copyright 2007-2009 Hewlett-Packard Development Company, LP. The information contained herein is subject to change without notice. Publication Number Part Number 5991-8624 June 2009 Applicable Product ProCurve Wireless Edge Services zl Module (J9051A) ProCurve Redundant Wireless Services zl Module(J9052A) Trademark Credits Microsoft®, Windows®, and Windows NT® are US registered trademarks of Microsoft Corporation. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Contents Software Management Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Downloading Software and Documentation from the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Downloading Software to the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Saving Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release WT.01.17 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Release WT.01.20 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Software Fixes Release WT.01.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Release WT.01.10 . . . . . . . . . . . . . . . . . . . . .
Software Management Software Updates Software Management Software Updates Check the HP ProCurve Networking Web site frequently for software updates for the various ProCurve products you may have in your network. Downloading Software and Documentation from the Web You can download software updates and the corresponding product documentation from HP ProCurve Networking’s Web site as described below.
Software Management Saving Configurations Downloading Software to the Module Caution The startup-config file generated by the latest software release is compatible with the same file generated by earlier software releases. HP recommends that you backup your current configuration before performing any software update. See the module’s Management and Configuration Guide (5991-8626) for instructions and more information.
Software Management Saving Configurations Saving the Current Configuration as the Start-Up Configuration When you use the CLI to make a configuration change, the module places the change in the running-config file. If you want to preserve the change across reboots, you must save the change to the startup-config file. Otherwise, the next time the module reboots, the change will be lost. To save configuration changes while using the CLI: 1.
Software Management ProCurve Switch, Routing Switch, and Router Software Keys ProCurve Switch, Routing Switch, and Router Software Keys Software Letter ProCurve Networking Products C 1600M, 2400M, 2424M, 4000M, and 8000M CY Switch 8100fl Series (8108fl and 8116fl) E Switch 5300xl Series (5304xl, 5308xl, 5348xl, and 5372xl) F Switch 2500 Series (2512 and 2524), Switch 2312, and Switch 2324 G Switch 4100gl Series (4104gl, 4108gl, and 4148gl) H Switch 2600 Series, Switch 2600-PWR Series: H.07.
Support Notes and Clarifications Release WT.01.03 Support Notes and Clarifications Release WT.01.03 WT.01.03 is the first software version for Wireless Edge Services zl Modules. ProCurve switches that support this module (Switch 5400zl Series and Switch 8212zl) require software version K.12.43 (or later). The Management and Configuration Guide (5991-8626) includes detailed information on the features in software release WT.01.03.
Support Notes and Clarifications Release WT.01.03 Clear the Internet Explorer (IE) Browser Cache The following steps detail the process of clearing the cache in IE version 6. If you are using a different version, your steps might vary slightly. Follow these steps to clear the cache: 1. Open IE. Figure 1.
Support Notes and Clarifications Release WT.01.03 2. Select Tools > Internet Options. The Internet Options window is displayed. Click this button Figure 2. Tools > Internet Options 3. Make sure that you are in the General tab. 4. In the Temporary Internet files section, click Delete Files. The Delete Files window is displayed. Figure 3. Delete Files 5. 7 Check the Delete all offline content box.
Support Notes and Clarifications Release WT.01.03 6. Click the OK button. 7. In the Internet Options window, click the OK button. Clear the Java Cache The following steps explain how to delete the cache for Sun Java version 1.5 or higher on a Windows XP machine. The steps vary depending on whether your Java version is above or below. See either: ■ “Clear the Cache for Sun Java Versions 1.5 and Higher” on page 8 ■ “Clear the Cache for Sun Java Versions Prior to 1.
Support Notes and Clarifications Release WT.01.03 Click this button Figure 5. Java Control Panel 3. 9 In the Temporary Internet Files section, click the Settings button. The Temporary Files Settings window is displayed.
Support Notes and Clarifications Release WT.01.03 Click this button Figure 6. Temporary Files Settings (Java Control Panel) 4. Click the Delete Files button. The Delete Temporary Files window is displayed. Figure 7. Delete Temporary Files (Java Control Panel) 5. Make sure that the Applications and Applets box is checked. 6. Click the OK button. 7. In the Temporary Files Settings window, click the OK button. 8. In the Java Control Panel window, click the OK button.
Support Notes and Clarifications Release WT.01.03 Clear the Cache for Sun Java Versions Prior to 1.5. Follow these steps to delete the Java cache: 1. Select Start > Settings > Control Panel. Java Plug-in Option Figure 8. Control Panel 2. Select Java Plug-in. The Java Plug-in Control Panel window is displayed. Note If your workstation has more than one Java applet, the Control Panel will display multiple Java Plugin options.
Support Notes and Clarifications Release WT.01.03 Click this button Figure 9. Java Plug-in Control Panel 4. You are prompted to confirm clearing the cache. Click the Yes button. Figure 10. Java Plug-in Confirmation Needed Screen 5. Click the Apply button; then close the screen. Restart the Browser You are now ready to access the Wireless Edge Services zl Module’s Web browser interface: 1. Close and re-open your browser. 2.
Support Notes and Clarifications Release WT.01.03 Figure 11. Activate the Java Applet 4. After about a minute, the Login screen is displayed. Figure 12.
Support Notes and Clarifications Release WT.01.03 Configuring Authentication for Web-Users Note Use this section to supplement the information in the chapter “Configuring the ProCurve Wireless Edge Services zl Module” in the Management and Configuration Guide (5991-8626). Instead of (or in addition to) using the local list to authenticate users, you can use a RADIUS server. If the RADIUS server authenticates a user, that user has the rights configured on the RADIUS database.
Support Notes and Clarifications Release WT.01.03 If the server does not send the proper VSAs, the user receives the monitor role (read-only) to the Web browser interface. The module’s internal server does not support VSAs, so you should use the local server only to authenticate users that require read-only access. Note If you do not correctly configure the RADIUS server, you can lock yourself out of the Wireless Edge Services zl Module Web browser interface.
Support Notes and Clarifications Release WT.01.03 Clarification: For Layer 3 Adoption, DHCP Server Option 189 Requires Value Type ‘String’ You must properly set up your DHCP server to support Layer 3 adoption of Radio Ports. Refer to your DHCP server documentation for instructions on adding private options and the configurations that your Radio Ports will receive.
Support Notes and Clarifications Release WT.01.13 Clarification: Setting Intrusion Detection with TKIP Countermeasures Intrusion Detection System (IDS) commands can be used to filter a station that set off IDS. Setting the following ids parameters will blacklist the client for the amount of time set in the ageout (ageout time can be up to one day).
Support Notes and Clarifications Release WT.01.28 Release WT.01.28 Logging Aggregation Time The operation of the Logging Aggregation Time parameter as described in the Management and Configuration Guide and the Web interface Help require clarification. Any message is immediately printed, unless it is identical to the previous one. If it is identical, then a counter is incremented instead.
Enhancements Release WT.01.03 Enhancements Enhancements Unless otherwise noted, each new release includes the enhancements added in all previous releases. To review the enhancements associated with the most recent general release, see “Release WT.01.17 Enhancements” on page 21. Release WT.01.03 Enhancements WT.01.03 is the first software version for Wireless Edge Services zl Modules.
Enhancements Release WT.01.03 Enhancements Feature Description sFlow support A module’s sFlow agent monitors each radio and samples wireless traffic for an sFlow collector. Secure NTP Configure the module to take its time from an Network Time Protocol (NTP) server, or act as a secure NTP server for other devices. Web-Users accounts Create accounts for Web-Users, allow various levels of access to the module’s Web browser interface.
Enhancements Release WT.01.13 Enhancements Release WT.01.13 Enhancements Support for Client Location Confidence in ProCurve Mobility Manager To support the client location confidence feature in ProCurve Mobility Manager 2.0 Automatic Update 1 (AU1), the logging of client probe requests (a “Probe List”) can be enabled through the switch’s Command Line Interface (CLI). To enable logging of client probe requests, use the station probe-history enable command from the wireless configuration context.
Software Fixes Release WT.01.03 Software Fixes Unless otherwise noted, each new release includes the software fixes added in all previous releases. To review the software fixes associated with the most recent general release, see “Release WT.01.16” on page 24. Release WT.01.03 Release WT.01.03 was the first software release for the ProCurve Wireless Edge Services zl Module. Release WT.01.10 Release WT.01.10 was released to Manufacturing only, and is not a general release. Problems resolved in Release WT.
Software Fixes Release WT.01.13 Release WT.01.13 Release WT.01.13 is a special release for WESM zl modules purchased prior to April 1, 2008, in the European Union and selected countries/regions. Problems resolved in Release WT.01.
Software Fixes Release WT.01.16 Release WT.01.16 Release WT.01.16 was not a general release. Problems resolved in Release WT.01.16 ■ Infrastructure (PR_0000002266) — Configuration file may fail to load properly onto the redundant module from the update server. ■ Security (PR_0000002283) — When using Web Authentication, a Guest group member with valid credentials may not be allowed access to the network.
Software Fixes Release WT.01.19 ■ Wireless (PR_0000004763) — Wireless clients may be unable to roam between modules within the same SSID after being authenticated. Release WT.01.19 Release WT.01.19 was not a general release. Problems resolved in Release WT.01.19 ■ Security (PR_0000003978) — Web-authenticated clients do not disconnect after user logs off. Release WT.01.20 Release WT.01.20 was not a general release. Problems resolved in Release WT.01.
Software Fixes Release WT.01.21 ■ Web UI (PR_0000005723) — On the Web User Interface, updated Help information for Web Authentication features. ■ Radio (PR_0000006089) — Increased character limit in the radio description field to 32. ■ WMM (PR_0000006215) — WES module resets when using WMM with dhcp-sniff enabled. ■ CLI (PR_0000006367) — Using the CLI to configure the 'hostname' and/or 'snmp-server sysname' results in different data field restrictions.
Release WT.01.22 Release WT.01.22 was not a general release. Problems resolved in Release WT.01.22 ■ MAC Authentication (PR_0000004541) — MAC authentication fails when using multicolon format as MAC Address format. ■ Reboot (PR_0000012106) — Module would hang and/or reboot with high CPU and RAM usage. ■ Web Authentication (PR_0000015682) — Reset limit for multiple web authentication redirects during authentication process. Release WT.01.23 Release WT.01.23 was not a general release.
Software Fixes Release WT.01.26 ■ Reboot (PR_0000016358) — WES module may freeze or reboot with high CPU utilization. Release WT.01.26 Release WT.01.26 was not a general release. Problems resolved in Release WT.01.26 ■ DHCP (PR_0000000757) — RP adoption using DHCP does not work when DHCP server is configured with Option 43 and Option 189. ■ Neighbor AP (PR_0000000866) — Incorrect RSSI values captured from Neighbor AP detection.
Software Fixes Release WT.01.27 ■ RADIUS (PR_0000018213) — Unable to create a Shared Secret key of less than 4 characters in a Domain Proxy Server. ■ Web UI (PR_0000018223) — Sort by VLAN is not working properly in the Network Setup page. ■ Reboot (PR_0000018541) — While executing a tech dump, the WES module may intermittently reboot.
Known Software Issues and Limitations Release WT.01.03 Known Software Issues and Limitations This section identifies known issues and limitations that you may encounter when using a ProCurve Wireless Edge Services zl Module (J9051A) or a ProCurve Redundant Wireless Services zl Module (J9052A). For the issues and limitations associated with the most recent general release, see “Release WT.01.10” on page 37. Note When updating software from version WT.01.
Known Software Issues and Limitations Release WT.01.03 ■ Applet (41387) — The "wrong value" error triggered by configuration of overlapping excluded DHCP ranges is uninformative. The error should mention that overlapping IP address ranges are not permitted. ■ Applet (40023) — The web management interface should disable (gray out) the Delete button when both the startup-config and running-config are chosen.
Known Software Issues and Limitations Release WT.01.03 ■ Applet (41761) — When inserting DHCP IP address ranges (Network Setup -> DHCP Server -> Configuration -> Add -> Included Ranges window of the web management interface), use of the tab key cycles the curser between the Start IP and End IP fields without progressing to other fields. The user will have to use the mouse to get to the other parameter fields.
Known Software Issues and Limitations Release WT.01.03 ■ Applet (1000460349) — The web management interface Help section for the Security -> NAT -> Configuration page states that the "list is empty". ■ Chassis (40367) — The switch does not consistently report the correct module status after execution of the halt command. Typing show wireless-services at the switch CLI after the halt has been executed may show a status of "not responding" even though the module has been successfully shut down.
Known Software Issues and Limitations Release WT.01.
Known Software Issues and Limitations Release WT.01.03 ■ L2-L3 (39840) — A second default gateway configuration will not overwrite the originally configured value, but will be ignored. Workaround: Remove the default gateway address prior to configuring a new address. ■ L2-L3 (41737) — Attaching an IP ACL with an allow any ACE to the downlink port stops all the traffic on the downlink, even if there is a MAC extended ACL to explicitly allow ARPs.
Known Software Issues and Limitations Release WT.01.03 ■ Security (1000460306) — MAC filter rules are designed to apply to the association process. If a wireless station is already associated, a new “deny” MAC filter configured through Security -> MAC Filter in the web management interface does not take effect until the station re-associates.
Known Software Issues and Limitations Release WT.01.10 ■ Wireless (40983) — Rate limiting is not applied to wireless stations that have roamed or have reconnected to the network if cached PMK is configured. Workaround: Disable PMK caching when vendor specific attributes are required for rate limiting a wireless client (e.g. when using IDM).
Known Software Issues and Limitations Release WT.01.28 ■ Security (45550) — When the local RADIUS server has the maximum number of clients, and an attempt is made to add another client, the error message displayed is "Error:Maximum proxy realm configured" rather than "Error:Maximum client config reached". Release WT.01.28 Infrastructure (PR_41333) — When log level is set higher than level 5, the log message below will constantly be logged to syslog.
Technology for better business outcomes To learn more, visit www.hp.com/go/procurve/ © Copyright 2007-2009 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.