Hp Procurve Discovery Tool

HP ProCurve was the name of the networking division of Hewlett-Packard from 1998 to 2010 and associated with the products that it sold. The name of the division was changed to HP Networking in September 2010. Please use HP Networking Products for an actual list of products.

The HP ProCurve division sold network switches, wireless access points, WANrouters, and Access Control Servers/Software under the 'HP ProCurve' brand name.

I'm switching laptops and need to re-install the HPE Network Discovery Tool. This was a free download from HPE, but I can no longer find a download link. 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 ProCurve Manager or ProCurve Manager Plus. This chapter explains how to get a ProCurve Routing Switch that supports IPv6 up and running. To configure basic IPv6 connectivity, you must do the following:. Enable IPv6 routing globally on the ProCurve Routing Switch. Configure an IPv6 address or explicitly enable IPv6 on each router interface over which you plan to forward IPv6 traffic.

Switching[edit]

Core Switches[edit]

  • 8212zl Series - (Released September 2007) Core switch offering, 12-module slot chassis with dual fabric modules and options for dual management modules and system support modules for high availability (HA). IPV6-ready, 692 Gbit/s fabric. Up to 48 10GbE ports, 288 Gb ports, or 288 SFPs. Powered by a combination of either 875W or 1500W PSUs, to provide a maximum of 3600W (5400W using additional power supplies) of power for PoE.

Datacenter Switches[edit]

  • 6600 Series - (Released February 2009) Datacenter switch offered in five versions. There are four switches with either 24 or 48 Gb ports, with two models featuring four 10GbESFP ports. There is also a 24 port 10GbE version. All of these feature front to back cooling and removable power supplies.[1]

Interconnect Fabric[edit]

  • 8100fl series - Chassis based, 8 or 16 slot bays. Supports up to 16 10GE ports / 160 Gigabit Ethernet Ports / 160 SFPs.

Distribution/Aggregator[edit]

  • 6200yl - Stackable switch, Layer 3, with 24 SFP transceiver ports, and the capability of 10GE ports
  • 6400cl series - Stackable switch, Layer 3, with either CX4 10GE ports or X2 10GE ports
  • 6108 - Stackable switch, with 6 Gb ports, and a further 2 Dual Personality Gb ports (either Gb or SFPs)

Managed edge switches[edit]

Entry level[edit]

2530 and 2620 lines are Aruba/HPE branded and included for comparison purposes only
PropertyOld version, no longer maintained: 2500Old version, no longer maintained: 2510Old version, no longer maintained: 2520Current stable version:2530Old version, no longer maintained: 2600Old version, no longer maintained: 2610Current stable version:2620
StatusDiscontinuedCurrentDiscontinuedCurrent
Released2000July 200720022008September 2011
LayerLayer 2Layer 3 (lite)Layer 3 (lite) static routingLayer 3 (lite) static & RIP routing
Ports12 or 24 10/100 ports with 2 proprietary Gb transceiver slots.24 (fanless) or 48 (incl. fan) 10/100 ports including 2 Dual Personality Ports (Gb or SFPs).
G models: 20 or 44 Gb ports with 4 Dual Personality Ports (4 x Gb or SFPs).
8 or 24 (PoE or non-PoE). GB and non-GB8, 24 or 48 10/100 ports including 1 or 2 Dual Personality Ports (1 or 2 x Gb or SFPs).24 or 48 (10/100 with 2 Gb ports and 2 SFP ports (no Dual Personality)[2]24 or 48 (PoE and non-PoE) with 2 SFP ports [1]
CPU62.5Mhz264-300Mhz266Mhz800Mhz266Mhz300Mhz400Mhz
Memory26KB64MB (128MB 2510-48)128MB DDR2256MB DDR332MB128MB512MB
Packet buffer6MB385KB (24), 768KB (24G)
512KB (48), 1.5MB (48G)
384KB (512KB on GB models)1.5MB (8,24), 3MB(48)1MB (24), 2MB (48)1MB (24), 2MB (48)
Last soldFebruary 2010February 2014CurrentFebruary 2009May 2012Current
Spec ref[2][3][4][5][6][7][8]

Mainstream[edit]

2920 line is Aruba/HPE branded and included for comparison purposes only
PropertyOld version, no longer maintained: 2800Old version, no longer maintained: 2810Old version, no longer maintained: 2900Old version, no longer maintained: 2910alOlder version, yet still maintained: 2920Old version, no longer maintained: 3400clOld version, no longer maintained: 3500Old version, no longer maintained: 3500yl
StatusDiscontinuedCurrentDiscontinued
Released2006200620092004February 2007
LayerLayer 2 with Layer 3 routingLayer 2Layer 2 with Layer 3 routingLayer 3
Ports20 or 44 Gb ports with 4 Dual Personality Ports (4 x Gb or SFPs).20 or 44 Gb ports with 4 Dual Personality Ports (4 x Gb or SFPs)20 or 44 Gb ports with 4 Dual Personality Ports (2 x Gb or SFPs)
Additionally includes four 10GE ports (two CX-4 and two capable of housing optional 10GE optical transceivers).
20 or 44 Gb ports with 4 Dual Personality Ports (4 x GborSFPs)
Supports up to four optional 10 Gigabit ports in CX4 and / or SFP+. Two versions support PoE and PoE+[3]
20 or 44 Gb port switch, and 4 x Dual Personality Ports (2 x Gb or SFPs). Also capable of supporting 10GE ports.20 or 44 10/100 port switches with two models supportingPoE functionality, and 4 x Dual Personality Ports (2 x Gb or SFPs).[4][5]20 or 44 Gb port switch with PoE functionality, and 4 x Dual Personality Ports (2 x Gb or SFPs). Also capable of supporting 10GE ports.
CPU266Mhz264Mhz667Mhz515Mhz625Mhz266Mhz666Mhz
Memory64MB64MB515MB512MB128MB256MB
Packet buffer768KB (24G), 1.5MB (48G)13.5MB (24G), 22.5MB (48G)6MB11.25MB2MB
Last soldDecember 2009August 2013October 2009May 2014March 2018 (August 2018 PoE)March 2009June 2014
Spec ref[9][10][11][12][13][14][15]

Chassis/Advanced[edit]

Hp Procurve Switch Configuration Guide

SeriesStatusReleasedLayerSizesComments
5400zlCurrentLayer 36 or 12 slot bays. Supports up to 48 10GE ports, 288 Gb ports, or 288 SFPsPowered by a combination of either 875W or 1500W PSU's, to provide a maximum of 3600W (5400W using additional powersupplies) of power for PoE
4200vlDiscontinued4 or 8 slot bays. Supports up to 192 10/100 ports or 128 Gb ports, or 32 SFPs.

Web managed switches[edit]

  • 1800 series - Fanless 8 or 24 Gb ports. The 1800-24G also has 2 Dual Personality Ports (2 x Gb or SFP). No CLI or SNMP management.
  • 1700 series - Fanless 7 10/100 ports plus 1 Gb or 22 10/100 ports plus 2 Gb. The 1700-24 also has 2 Dual Personality Ports (2 x Gb or SFPs). No CLI or SNMP management.

Unmanaged Switches[edit]

  • 2300 series
  • 2124
  • 1400 series
  • 408

Routing[edit]

WAN Routers[edit]

  • 7000dl - Stackable WAN Routers with modules for T1/E1, E1+G.703, ADSL2+, Serial, ISDN, and also IPsecVPN.

German company .vantronix marketed software products until 2009.[6][7]

Mobility[edit]

Due to country laws, ProCurve released different versions of their wireless access points and MultiService Access points.

MultiService Mobility / Access Controllers[edit]

The MSM Access and Mobility Controllers support security, roaming and quality of service across MSM Access Points utilising 802.11 a/b/g/n wireless technology.[8]

  • MSM710 - Supports up to 10 x MSM Access points. Supports up to 100 Guest Users.
  • MSM730 - Supports up to 40 x MSM Access points. Supports up to 500 Guest Users.
  • MSM750 - Supports up to 200 x MSM Access points. Supports up to 2000 Guest Users.
  • MSM760 - Supports 40 x MSM Access Points, plus license support up to 200
  • MSM765 - Supports 40 x MSM Access Points, plus license support up to 200. This is a module form, and based on the ProCurve ONE.

MultiService Access Points[edit]

Most access points are designed to work in controlled mode: a controller manages and provides authentication services for them.

  • MSM310 - Single 802.11a/b/g radio. Includes 2.4 GHz dipole antennas
  • MSM310-R - External use. Single 802.11a/b/g radio. Includes 2.4 GHz dipole antennas
  • MSM313 - Integrated MSM Controller + single radio Access Point
  • MSM313-R - External Use. Integrated MSM Controller + single radio Access Point
  • MSM317 - Single 802.11b/g radio, with integrated 4 port switch[8][9]
  • MSM320 - Dual radios (802.11a/b/g + 802.11a/b/g) for outdoor deployment options. Includes 2.4 GHz dipole antennas. Supports PoE.
  • MSM320-R - External use. Dual radios (802.11a/b/g + 802.11a/b/g). Includes 2.4 GHz dipole antennas. Supports PoE.
  • MSM323 - Integrated MSM Controller + dual radio Access point.
  • MSM323-R - External Use. Integrated MSM Controller + dual radio Access point.
  • MSM325 - Dual radios (802.11a/b/g + 802.11a/b/g) including RF security sensor. Requires PoE
  • MSM335 - Triple radios (802.11a/b/g + 802.11a/b/g + 802.11a/b/g RF security sensor)
  • MSM410 - Single 802.11 a/b/g/n radio. Requires PoE. Internal antenna only.
  • MSM422 - Dual-radio 802.11n + 802.11a/b/g.
  • MSM460 - Dual-Radio 802.11a/b/g/n. Only internal 3x3 MIMO Antenna. Requires PoE.
  • MSM466 - Same as MSM460 but with external 3x3 MIMO antenna connectors, no internal antenna. Requires PoE.

Centralised wireless[edit]

  • Wireless Edge Services Module - Controls Radio ports, and is an integrated module that fits into ProCurve Switches 5300xl / 5400zl / 8200zl only. Redundant Module available for failover. Supports the following Radio Ports:
  • RP-210 - Single 802.11b/g radio and integrated antenna
  • RP-220 - Dual-radio design (one 802.11a and one 802.11b/g); plenum rated; external antennas required
  • RP-230 - Dual-radio design (one 802.11a and one 802.11b/g); features internal, integrated antennas

Hp Procurve Manager Download Free

Wireless access points[edit]

  • M110 - Single 802.11a/b/g radio
  • M111 - Wireless Client Bridge including dual band antennas
  • AP-530 - Wireless access point; Dual radios support simultaneous 802.11a and 802.11b/g transmissions. The AP-530 has two integrated radios (one of which supports 802.11a/b/g; the other of which supports 802.11b/g). The AP supports the Wireless Distribution System.
  • AP-420 - Wireless access point; Features a single, dual-diversity 802.11b/g radio.
  • AP-10ag - Wireless access point; Dual radios support simultaneous 802.11a and 802.11b/g transmissions.

Management Software[edit]

ProCurve Manager' (PCM) is a network management suite for products by ProCurve.

ProCurve Manager[edit]

ProCurve Manager comes in two versions; a base version supplied both free of charge with all managed ProCurve Products and also for download, and a 'Plus' version that incorporates more advanced functionality and also enables plugin support. There is a 60-day trial version including all modules. Both derive from the trial version and need to be activated via Internet.

The Plus version can also be implemented in HP OpenViewNetwork Node Manager for Windows. The software ProCurve Manager is predominantly for ProCurve products.

Protocols[edit]

  • PCM uses Link Layer Discovery Protocol (LLDP, Cisco Discovery Protocol (CDP) and FDP (Foundry) for detecting network devices
  • For identification and deep inspection of network devices SNMP V2c or V3 is used.
  • Network traffic is analysed using RMON and sFlow.

Plugins[edit]

  • IDM (Identity Driven Manager) - Add-on Module for PCM+; contains Intranet Network Access Security using 802.1X; compatible with MicrosoftNetwork Access Protection (NAP) since Version IDM V2.3
  • NIM (Network Immunity Manager) - Add-On Module for PCM+ v2.2 and above; contains Intranet Intrusion Detection and Network Behavior Anomaly Detection (NBAD) using sFlow
  • PMM (ProCurve Mobility Manager) - Add-on Module for PCM+; contains Element Management for ProCurve Access Points (420/520/530) starting from Version PMM V1; WESM Modules and Radio Ports are supported since Version PMM V2. Since PMM v3, the MSM Access Points and Controllers are now supported[10]

Security[edit]

Network Access Control with Endpoint testing[edit]

  • ProCurve Network Access Controller 800 - Management and Security for Endpoints when they access the Network

Firewall[edit]

The Threat Management Services Module is based on the ProCurve ONE Module, and is primarily a firewall with additional Intrusion-prevention system and VPN capabilities[11][12]

Accessories[edit]

External power supplies[edit]

  • ProCurve 600 Redundant external power supply - supports one of six times Redundant Power for series 2600-PWR (not series 2600 w/o PWR), 2610, 2800, 3400cl, 6400cl and 7000dl as well as two times optional External PoE Power for series 2600-PWR, 2610-PWR or mandatory External PoE Power for series 5300 with xl 24-Port 10/100-TX PoE Module only
  • ProCurve 610 External power supply - supports four times optional External PoE Power for series 2600-PWR, 2610-PWR, or mandatory External PoE Power for series 5300 with xl 24-Port 10/100-TX PoE Module only
  • ProCurve 620 Redundant/External power supply - supports two times optional External PoE Power for series 3500yl and two times Redundant Power for series 2900, 3500yl and 6200yl
  • ProCurve Switch zl power supply shelf - supports two times optional External PoE Power for series 5400zl and 8200zl; must be additionally equipped with max. two 875W or 1500W (typical) ProCurve Switch zl power supplies

GBICs and optics[edit]

ProCurve have a range of Transceivers, GBICs and 10GbE optics for use within ProCurve devices.

Transceivers[13] are used in the unmanaged 2100 & 2300 series, and the managed 2500 series of switches

TypeCable TypeMaximum DistanceNotes
Gigabit Stacking KitInterconnect Cable59 cm2 x HSSDC Gigabit Transceiver ports.
Gigabit SX TransceiverMultimodeup to 550 m1000BASE-SX, -SC port.
Gigabit LX TransceiverSinglemode or Multimode10 km or 550 m1000BASE-LX, -SC port.
100/1000-T TransceiverCategory 5 cable plus100 mRJ-45 port.
100-FX TransceiverMultimode2 km full duplex or 412 m half duplex100BASE-FX port.

GBICs[14] are used for most switches for 100 Mbit/s and 1000 Mbit/s fiber connectivity. All fiber GBICs have an LC presentation.

TypeCable TypeMaximum DistanceNotes
100BASE-FXMultimode2 km full duplex or 412 m half duplex
100BASE-BX10-DSinglemodeup to 10 km
100BASE-BX10-USinglemodeup to 10 km
1000BASE-SXMultimodeup to 550 mDependent on fiber cable quality
1000BASE-LXMultimode2 to 550 m
1000BASE-LXSinglemode2 to 10,000 mCompliant with IEEE 1000BASE-LX10 standard
1000BASE-LHSinglemode10 to 70,000 mAttentuators may be required dependent on distance.
1000BASE-BX-DSinglemode0.5 to 10,000 m
1000BASE-BX-USinglemode0.5 to 10,000 m
1000BASE-T TransceiverCat 5 cable plus100 m

ProCurve ONE[edit]

HP ProCurve ONE Services zl Module[edit]

The HP ProCurve ONE Services zl Module is an x86-based server module that provides two 10-GbE network links into the switch backplane. Coupled with ProCurve-certified services and applications that can take advantage of the switch-targeted API for better performance, this module creates a virtual appliance within a switch slot to provide solutions for business needs, such as network security. The ProCurve ONE Services zl Module is supported in the following switches:

  • HP ProCurve Switch 5406zl
  • HP ProCurve Switch 5412zl
  • HP ProCurve Switch 8212zl

The following applications have completed, or will complete the ProCurve ONE Integrated certification on the HP ProCurve Services zl Module in early 2009.

Data center automation

Location

Wireless IPS

Network management

VoIP / Unified Communications

Video distribution

Other - Unsupported

Other 'unofficial' methods for loading alternative platform software such as pfSense and VMware's ESXi on to ONE Service modules have been discovered.

Discontinued Products[edit]

  • 1600M - stackable Layer 2 switch
  • 2400M - stackable Layer 2 switch
  • 2424M - stackable Layer 2 switch
  • 4000M - modular Layer 2 switch
  • 8000M - modular Layer 2 switch
  • 9400 - modular Layer 3 Router
  • AP 520 - Access Point
  • 4100gl - modular Layer 2 switch
  • 2700 series - unmanaged Layer 2 switch
  • 9300m series - modular Layer 3 Router
  • ProCurve Access Controller Series 700wl
  • 745wl
  • ACM (Access Control Module) for the 5300xl only
  • 5300xl series - Chassis based, Layer 3, in either 4 or 8 slot bays.

References[edit]

  1. ^O'Hanlon, Charlene (2009-01-26). 'HP flexes datacenter muscle with new switch'. Channel Insider. Retrieved 2009-05-30.
  2. ^Duffy, Jim (2008-06-02). 'HP ProCurve refreshes edge switches'. www.pcworld.idg.com.au. Retrieved 2009-05-30.
  3. ^Duffy, Jim (2009-03-17). 'ProCurve unveils new SMB switches'. Network World. Archived from the original on 2011-06-15. Retrieved 2009-05-28.
  4. ^April, Carolyn (2009-06-15). 'HP ProCurve Rolls Out New 10/100 Switches'. Channel Insider. Retrieved 2009-06-15.
  5. ^Hickey, Andrew (2009-06-15). 'ProCurve Bulks Up 3500 Switch Series'. ChannelWeb. Archived from the original on 2009-06-17. Retrieved 2009-06-15.
  6. ^'High-secure products based on OpenBSD'. vantronix web site. 2009. Archived from the original on June 5, 2009. Retrieved August 30, 2011.
  7. ^'ProCurve ONE Alliance: .vantronix'. vantronix web site. 2009. Archived from the original on February 1, 2009. Retrieved August 30, 2011.
  8. ^ abHickey, Andrew (2009-06-01). 'ProCurve Goes Mobile, Eyes Convergence'. ChannelWeb. Archived from the original on 2013-01-20. Retrieved 2009-06-02.
  9. ^Cox, John (2009-06-01). 'HP ProCurve converges wireless and wired network access'. Network World. Archived from the original on 2009-06-03. Retrieved 2009-06-02.
  10. ^Cox, John (2009-06-01). 'HP ProCurve converges wireless and wired network access'. Network World. Archived from the original on 2009-06-03. Retrieved 2009-06-02.
  11. ^Fratto, Mike (2009-04-29). 'New ProCurve Threat Module: Flexibility Requires Planning'. Information Week. Retrieved 2009-05-28.
  12. ^Walsh, Lawrence (2009-04-27). 'HP Unveils ProCurve Firewall, Security Ambitions'. Channel Insider. Retrieved 2009-05-30.
  13. ^'FAQs for ProCurve Transceivers'. ProCurve.com. Retrieved 2009-05-28.
  14. ^'FAQs for ProCurve GBICs'. ProCurve.com. Retrieved 2009-05-30.

External links[edit]

Retrieved from 'https://en.wikipedia.org/w/index.php?title=ProCurve_Products&oldid=985409706'

ProCurve Manager Plus version 2.0 includes a fee-based upgrade product to ProCurve Manager Plus 1.x. There are five products available for purchase in this release.

  • J8778A ProCurve Manager Plus 2.0 - 100 device license
  • J9009A ProCurve Manager Plus 2.0 - unlimited device license
  • J8991A ProCurve Manager Plus 2.0 Upgrade to 1.x - 100 device license
  • J8779A ProCurve Manager Plus 2.0 Upgrade to 1.x - unlimited device license
  • J8477A ProCurve Identity Driven Manager 1.0

This compressed, ZIP-format file contains ProCurve Manager 2.0 and a 30-day free trial of ProCurve Manager Plus version 2.0, and ProCurve Identity Driven Manager version 1.0.

These release notes include information on the following:

NOTE: These Release Notes are applicable at the date of the ProCurve Manager Version 2.0 Release. Please check the ProCurve Support Web site for more recent information.

Below is a summary of the new features that are available in ProCurve Manager (PCM) with this release. Please refer to the ProCurve Manager Network Administrator's Guide for a full description on the use of these features:

Hp procurve manager download free

PCM Features:

  • A new Import/Export tool lets you import Device and Subnet data from a .CSV (comma delimited) file into PCM, or export Device and Subnet data from PCM to a .CSV file, for use in other applications.
  • SNMP V3 and SSH are now supported by PCM for device access and management, and for communications between PCM and ProCurve devices.
  • The PCM automatic update feature keeps your system updated with the latest revisions and device driver support for PCM software.
  • When new ProCurve devices are added to the network, PCM's new Automatic Registration feature can collect the necessary data and automatically register the devices with ProCurve support.

PCM Plus Features:

  • PCM now includes a Find Node and Node-to-Node path trace feature to help you quickly and easily locate devices on the network.
  • The PCM Plus Configuration manager now includes the ability to create a Device configuration 'Template' for each device type in the network. A Configuration Template policy can be used to automatically apply templates to new devices when they are found in the network, thus simplifying configuration and management as your network expands.
  • PCM Plus now supports use of Event Driven Policies; that is, you can create a Policy to be launched when a specific alert (event) is received. Then configure the Alert to execute the Policy automatically based on the defined parameters in PCM.
  • With the Network Consistency: Network Analyzer wizard you can check to make sure that the network connections between devices are configured correctly.
  • The new Configurable Integration Platform included in PCM Plus can be used to:
    • Create and manage 'User-defined devices,' that is other ProCurve or non-ProCurve devices not found through auto-discovery.
    • Create user-defined 'Actions' and 'Triggers' to launch 3rd-party applications from within the PCM GUI.
    • Receive and process traps, and log events for user-defined devices and to log events from OV-NNM.

Once you install PCM or PCM Plus Version 2.0, you cannot revert to the previously installed version. If you are uncertain if you want to upgrade to the 2.0 Version, it is best to install it on a system that does not have any ealier versions of PCM or PCM+ installed.

Minimum System Requirements

  • 2 GHz Intel Pentium IV or equivalent
  • 1 GB RAM
  • 1 GB free hard disk space

Supported Operating Systems:

  • MS Windows 2000
  • MS Windows XP Professional (SP 1 or greater)
  • MS Windows 2000 Server, Advanced Server or Professional with SP 4 or better
  • MS Windows 2003 Server
Hp procurve discovery tool kit

Additional processing power and disk space may be required for larger networks and to support extensive traffic monitoring. Also, the online help feature in PCM is only supported on MS Internet Explorer web browser.

Minimum System Requirements

Hp procurve discovery tool
  • 1 GHz Intel Pentium IV or equivalent
  • 1 GB RAM
  • 250 MB free hard disk space

Recommended System Requirements

  • 2 GHz Intel Pentium IV or equivalent
  • 2 GB RAM
  • 500 MB free hard disk space

Supported Operating Systems:

  • MS Windows 2000
  • MS Windows XP Professional (SP 1 or greater)
  • MS Windows 2000 Server, Advanced Server or Professional with SP 4 or better
  • MS Windows 2003 Server

NNM Versions that should be installed prior to PCM 2.0 install

  • NNM 6.4 on Win 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP
  • NNM 7.01 on Win 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP
  • NNM 7.5 on Win 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP, Windows 2003 Standard edition and Windows 2003 Enterprise edition

Additional processing power and disk space may be required for larger networks and to support extensive traffic monitoring. Also, the online help feature in PCM is only supported on MS Internet Explorer web browser.

One Network Management Program per Computer

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 ProCurve Manager or ProCurve Manager Plus.

Note : The above is not applicable when PCM 2.0 is installed on systems running HP Openview NNM.

Working With Multi-homed Systems:

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:

  • A system with two or more network adaptors.
  • A system with a traditional ethernet network adaptor, plus a wireless adaptor.
  • A system with only one network adaptor, but that is running some network tunneling software such as a VPN client. Generally what happens in this situation, is that the system appears to have two network interfaces (each with its own IP address). But in reality the system only has one physical adaptor, and the VPN client software emulates a second adaptor (while using the original adaptor under the covers).

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 ProCurve Manager client application attaches itself to the 166.3.4.5 interface, and the 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:

  1. Find the commIpAddr.txt file. This file exists in the config directory, so for example, for the client this file exists in: C:Program FilesHewlett-PackardPNMclientconfig . For the PCM server, you need to create a text file (with Notepad or similar application) and name it 'commIpAddr.txt' and place it in the C:Program FilesHewlett-PackardPNMserverconfig directory.
  2. Edit the file with a text-based editor (such as Notepad or Wordpad), and enter the IP address of the interface you want the application to attach to. For example for the network illustrated above, you would add the entry ' 15.255.120.25 ' (without the quotes) in the first line of the file. More than one IP address can be used, but each IP Address entry must be on a separate line.
  3. Save your changes.
  4. Restart the application. If this is the ProCurve Manager client, just restart the application. If this is the ProCurve Manager server, you must restart the PCM services (HP ProCurve -Datastore, -Network Manager Server, and -Traffic Launch Service) from the Services control panel.

This issue is also described in the ProCurve Manager Getting Started Guide that comes with the CD package.

Adding Remote Client Stations

When you install 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 'http://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 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 ->ProCurve Manager ->ProCurve Manager Server Discovery

For PCM 2.0 (PCM-NNM version), the PCM Remote Client can only be installed on machines that have NNM Remote console installed. Once installed, the client will always connect to the server attached to the NNM remote console.

Configuring Client/Server Access Permissions

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 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:

15.255.124.84
15.29.37.*
10.*.*.*

*.rose.hp.com
system1.hp.com

To add an entry, open the access.txt file, which can be found in the config directory ( C:Program FilesHewlett-PackardPNMserverconfig ). 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 these instructions:

  1. First you must change an entry in the serverconfigTyphoonServer.cfgfile .
    This file is a text file and can be edited with Notepad or Wordpad. Look for the entry that reads
    'AUTHENTICATION=10 ', and change it to read ' AUTHENTICATION=100 '. Save the file and restart the server (listed as 'HP ProCurve Network Manager Server' in the services list).
  2. Edit the access.txt file as described above, but instead of entering an IP address, just enter the selected password (on a line by itself). Save the file. It is not necessary to restart the server. For example, if we set the password to 'procurve':

procurve
*.rose.hp.com
system1.hp.com

  1. On the client (the client must already be installed), you must edit the riptide.cfg file. This file already has several entries in it. You must add a line similar to the following:

PASSWORD = your password

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 is 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.

NOTE for PCM-NNM Version:

Procurve

The above is not applicable for the PCM-NNM installation. PCM cannot bind to port 162 since it is already used by NNM.All device traps and application events will be displayed on the NNM Alarm browser.

For the ProCurve Wireless Access Point 420 devices, the PCM Switch Software Update utility will only work with switch software versions newer than 2.0.29

For the 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 you to 'downgrade' to an earlier version of the switch software.

AP420 running firmware prior to 2.1.0

  • If the 'Communication Parameters in PCM' tool is used to modify the SNMP settings used to communicate with an AP420 running firmware prior to the 2.1.0 release, the device will become unreachable due to the tool causing PCM to use SNMPv2 for this device. An update will be available shortly, please contact ProCurve support for a release date.

AP420 upgrading to 2.1.0 firmware

  • There is a known issue that causes PCM to not be able to upgrade the AP420 to the 2.1.0 firmware version. An update will be available shortly, please contact ProCurve support for a release date.

Problem scanning configurations on AP420 running 2.1.0

  • Due to a change in the CLI syntax introduced in the 2.1.0 firmware PCM is unable to scan the configurations of AP420s running this software. This issue will also cause the Software Update tool to be unable to successfully update the firmware on these devices. Please contact ProCurve support for a release date.

If you use a 520wl device as the starting point for a managed subnet, Discovery will not work properly unless you manually add the subnet in PCM and then restart Discovery.

To process traps sent from 520wl devices, you must deselect the 'Unknown' option under the 'Select events to ignore' section in the global preferences for Events.

The 'syslog' feature in PCM does not work with 520wl devices.

The following are known issues when using PCM 2.0 with the ProCurve 9300 Series devices:

  • Port based Policies cannot target a range of ports (e.g., A1-A5, etc.) on 93xx devices.
  • LLDP-capable devices connected directly to 93xx devices may not map properly. Using a CDP-capable device between the 93xx and LLDP-capable device will resolve the problem.
  • Support for use of SNMPv3 and SSH Keys on 9300 series devices is not included with PCM 2.0
  • VLAN Management capabilities are not available on 94xx devices.

Installation

  • PCM/PCM+ and Terminal Services are not supported on same server
  • Un-installation of PCM 1.5 leaves the TLS_HPPNM process running.
  • When adding subnets for Discovery in Global Preferences, there is no verification of IP addresses. If an invalid IP address is used, the subnet will not be discovered.
  • If you have a very large network with many subnets, PCM performance can be improved by increasing the discovery interval, and in particular increasing the interval for VLAN discovery.
  • If you have a large network, and are using a Configuration Scan Policy while Discovery and Traffic Monitor are running, it may cause the PCM management server to 'hang' or lose its connection to the 'Typhoon Server'. It is best to use a phased method (use separate policies at staggered intervals to scan by subnets or device group) rather than a single policy. Alternately, you can stop the Discovey and Traffic Monitor processes while the configuration scan is being done.

Network Maps

  • Wide Area Network (WAN) links are not supported (displayed) in the PCM network maps.
  • Path Trace does not work properly in a meshed environment.
  • If the device Display Name preferences are changed, you need to refresh (redraw) the network map in order to view the new device display name.

Event Management

  • Series 93xx traps are not automatically received by the PCM Event Browser. The Agent IP address that is embedded in the SNMP PDU is not the IP address from which the device was discovered. To resolve the problem, run the following command from the CLI:
    snmp-server trap source ve 200
  • Traps will not be generated until modification of Thresholds in RMON Manager is done.
  • Syslog trims entries after 1000 events based on severity, so it trims the events with the lowest severity first.
  • Incomplete syslog message format for ProCurve 2800 and 5300 series devices
  • If the speed of a connection being monitored in the Traffic Manager changes, errors will occur in the utilization rate display, due to the original configuration data cached in PCM. To correct the problem, delete the device from PCM, then use Manual Discovery to add the device back to PCM. This resets the traffic monitoring to match the current settings on the device.
  • On a remote PCM client, the traffic graph and gauges flash correct data then quickly gray out. This occurs when the PCM remote client’s system clock is not synchronized with the server’s system clock. Make sure the PCM remote client’s system clock is synchronized with the server’s system clock (within 5 seconds).

VLAN Management

  • When deleting VLANs directly on the switch, a full discovery cycle must run before changes are displayed in the PCM user interface.
  • Creating VLANs in PCM may take several seconds to take effect on switch. To speed up the process, restart Discovery.
  • If you create a VLAN directly on the switch (not using PCM), PCM will discover the VLAN at the next discovery cycle. To speed up the process, restart Discovery.

PCM Management Server Services

  • PCM Management Server Services must be manually restarted if a network connection is lost.

Configuration Management

  • Configuration labels cannot be removed until the configuration is deleted.
  • When entering IP addresses for devices in PCM, they are not always verified. If an invalid IP address is entered for a device in PCM, then PCM will be unable to communicate with the device.
  • Any change made to a device configuration file will cause the Configuration File change indicator to be displayed, even if it is only to the first line (date and version number) of the file and there are no actual configuation changes.
  • When RADIUS authentication is configured on a switch, PCM does not support use of CLI. Only local password authentication and TACACS is supported. If you use RADIUS on a switch, the CLI commands, and CLI communications Parameters test will not work.

Network Settings

  • The address used for SOCKs proxy in PCM Global Preferences for Network Settings are not validated. If an invalid SOCKS host or port is entered, devices will be unreachable in PCM.
  • If the specified SOCKs server goes down, or it's network connection is lost, devices will be unreachable in PCM.

PCM-NNM synchronization component:

  • Devices deleted in PCM will not be deleted from NNM.
  • Changing subnets from Managed to Unmanaged on PCM will not be reflected in NNM.
  • If SNMP community names are changed on NNM, the change will be not be reflected in PCM until after the next SNMP synchronization cycle. To speed up this process use the manual SNMP synchronization process.

© Copyright 2003, 2005 Hewlett-Packard Development Company, L.P.
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.

Publication Number

August, 2005
Edition 2.0-b

Part #5990-8848

Trademark Credits

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.

PCM and PCM Plus uses two unmodified Open Source packages. The full source code and licenses to these packages can be found on the PCM distribution CD in the OpenSourcePackages directory. These packages are:
1) JDesktop Integration Components. http://javadesktop.org/articles/jdic/index.html
2) JRadiusClient. http://jradius-client.sourceforge.net/

The following applies to both of these packages:

This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Disclaimer

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.

Warranty

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.procurve.com