These release notes include information on the following:
Below is a summary of the new features that are available in HP ProCurve Manager (PCM) with this release. Please refer to the HP ProCuvre Manager Network Administrator's Guide for a full description on the use of these features:
Additional processing power and disk space may be required for larger networks and to support extensive traffic monitoring
If you are installing PCM 1.5 on a system running PCM 1.0 with patch 1.0a, and you would like a clean installation, (you do not want to save the PCM 1.0 database or configuration), please follow the installation steps below:
Before initiating the
installation process, it is recommended that you back up the
PCM/server/db/solid.db database
file. This will allow you to back out to the previous version if necessary
and prevents the existing database from being lost or corrupted during the
database migration process.
Because of resource conflict that will occur if you have multiple network management tools running on the same computer, for example during discovery of the network devices, make sure you uninstall any other network management programs from your computer before installing HP ProCurve Manager or HP ProCurve Manager Plus.
A multi-homed system is a server or PC that has more than one IP address. Generally this is achieved by installing more than one network card in the system, but there are other ways that a system can be multi-homed. Here are a few of the situations that meet this definition:
When ProCurve Manager (either client or server) starts up, it attaches itself to the primary network interface. All network traffic between the client and server will be directed to the selected network interface. For example, if the HP ProCurve Manager client application attaches itself to the 166.3.4.5 interface, and the HP ProCurve Manager server is running on the 15.255.120.* network, there is no way that the client will ever connect successfully to the server.
To resolve this problem PCM has a configuration file that you can change to correct this situation. To setup this file, follow these steps:
When you install HP ProCurve Manager Plus, the server and client functions are installed on the computer. You can also install the client function on any number of other computers in your network that have network access to the server computer.
To install the client function on another computer, simply start a web browser, such as Microsoft Internet Explorer, and for the URL type in the IP address of the server computer followed by a colon and the port ID 8040. For example, if the IP address of the server computer is 10.15.20.25, then you would enter 10.15.20.25:8040 on the web browser address line. That will launch the client installation wizard and step you through the installation process.
If you have multiple HP ProCurve Manager servers in the network, when you install a remote client you will be prompted to select the server to which you want the client to attach. This server will be used each time the client program is launched. You can change the server that is being accessed by selecting the "ProCurve Manager Server Discovery" option that was included when you installed the client. From the Windows "Start" menu, select Programs ->HP ProCurve Manager ->HP ProCurve Manager Server Discovery
The ProCurve Manager server maintains a list of authorized clients that are permitted to log into the server. By default, when the ProCurve Manager server is installed, the only client allowed to log in is the client on the same system as the server--that is, no remote servers are allowed. This can be a problem for customers who are unaware of this security feature, because they will try to install remote clients using the browser, and will be unable to connect to the server after completing the client installation.
There are two files associated with HP ProCurve Manager client/server security that can easily be configured to allow access to any set of actual or potential clients. There are two ways that this file can be configured, depending on what you know about the clients that need to connect.
The access.txt file can be configured with a list of IP addresses specifying the clients that are authorized to log into the server. The file may contain as many addresses as needed, one IP address per line; or you may configure IP addresses with wildcards. DNS names are also allowed in the file, including DNS names with wildcards (this is useful for DHCP environments where a system's DNS name remains unchanged, although it's actual IP address may change from time to time). For example, below is an example of a valid access.txt file:
To add an entry, open the access.txt file, which can be found in the config directory ( C:\Program Files\Hewlett-Packard\PNM\server\config ). Be sure to edit the file using a text-based editor such as Notepad or Wordpad. Edit the file as necessary, one entry per line, then save it. It is NOT necessary to restart the server; the changes will take effect immediately.
There are situations where it is not possible to know ahead of time what IP address a potential client will have. This is particularly the case in situations where the client comes in through some sort of VPN, where the IP address of the client is assigned externally. To solve this problem it is possible to add client passwords to the access.txt file that correspond to specially configured clients. Note that even though you will be modifying the same access.txt file as for method 1 (above), the two mechanisms can freely co-exist--that is, the access.txt file can contain a combination of IP addresses and passwords. To enable password access for a particular client, follow the following instructions:
Do not change any of the other entries in the file, as they are necessary for the correct operation of the client.
A sample Riptide.cfg file, once edited with the password "procurve", would look like this:
LEASE_LENGTH = 40000
TRACING_PROPERTY_KEY
= CoreServices.Main
MANUFACTURER = Hewlett-Packard
SERVICE_NAME = Typhoon
COMPONENT_DB = config/Components.prp
TRACING_DBFILE =
config/Loggers.prp
NETWORK_DELAY = 25000
VERBOSE = true
PASSWORD = procurve
Once you have saved the riptide.cfg file, start the PCM Client and enter (select) the address of the PCM Server in the Direct address field of the "Search for Servers" dialog. The client should now connect successfully to the server.
A trap is an alert sent by a device via UDP protocol to notify one or more hosts that something has occurred. A device may send a trap when a link on a port comes up, when a device has received an excessive amount of errors, or when a device has detected an excessive amount of broadcasts. In order to receive traps from a particular device, the switch must be configured with the host's address. This accomplished in multiple ways, such as CLI SNMP, and ProCurve Manager.
When ProCurve Manager (server) starts up, it binds to port number 162. Port 162 is the port that all incoming traps arrive on. The problem arises when a previous process is already bound to that port, in which case ProCurve Manager will not be able to receive traps because the port is in use.
To resolve the problem, make sure no process is bound to port 162. Examples of applications that bind to port 162 are the Windows SNMP Trap Receiver Service*, TopTools, HP OpenView and MG-Soft MIB Browser Trap Ringer. In the event that a process was bound to port 162 when ProCurve Manager was started simply terminate the process and restart the ProCurve Manger (server). To restart the ProCurve Manager (server) in Windows 2k go to Control Panel->Administrative Tools-> Services. Double click on the HP ProCurve Network Manager Server, click the Stop button, and then click the Start button. In Windows XP/2003 go to Control Panel->Administrative Tools-> Services, double click on the HP ProCurve Network Manager Server, click the Stop button, and then click the Start button.
Telnet is a protocol used for connecting to remote devices or machines for administration. SSH is a protocol that allows the same functionality as Telnet but provides a secure connection to the remote device or machine.
PCM currently only allows the user to use the Telnet protocol to connect. Telnet sends all information between the client and the server in plain text. The situation may arise where a customer wants to connect to a device over a secure connection.
TelnetCommand=C:\Program Files\SSH\ssh.exe
TelnetCommand=C:\SSH\putty.exe -ssh
If the ssh program is run from a DOS prompt it may be necessary to precede the ssh command with the "start" command, for example:
TelnetCommand=start C:\ssh.exe
After the command has been changed save the file and close the text editor.
For the HP ProCurve Wireless Access Point 420 devices, the PCM 1.5 Switch Software Update utility will only work with switch software versions newer than 2.0.29
For the HP ProCurve Wireless Access Point 520wl devices, if you upgrade to version 2.4.5 of the switch software, the PCM Switch Software Upgrade utility will not allow your to "downgrade" to an earlier version of the switch software.
New to HP ProCurve Manager Plus is the ability to use a TACACS+ user account when accessing HP ProCurve switches that support TACACS, through use of the CLI wizard.
Due to a limitation in the PCM 1.5 database, the TACACS+ user account MUST have the same password for login, as well as enable mode. A TACACS+ username and password allow access to the switch with user rights, and does not allow the user to view/modify the switch configuration; whereas, the enable password can provide manager access to the switch.
© Copyright 2003, 2004 Hewlett-Packard Company
All Rights Reserved.
This document contains information which is protected by copyright. Reproduction, adaptation, or translation without prior permission is prohibited, except as allowed under the copyright laws.
Microsoft, Windows, Windows 95, and Microsoft Windows NT are registered trademarks of Microsoft Corporation. Internet Explorer is a trademark of Microsoft Corporation.
Ethernet is a registered trademark of Xerox Corporation.
Netscape is a registered trademark of Netscape Corporation. Cisco® is a trademark of Cisco Systems, Inc.
The information contained in this document is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard.
See the Customer Support/Warranty booklet included with the product.
A copy of the specific warranty
terms applicable to your Hewlett-Packard products and replacement parts
can be obtained from your HP Sales and Service Office or authorized dealer.
Hewlett-Packard Company
8000 Foothills Blvd, m/s 5551
Roseville, CA 95747-5551
http://www.hp.com/go/hpprocurve