Release Notes:
ProCurve Manager Version 2.1,
Identity Driven Manager 2.0, and
Mobility Manager 1.0
The following products are included and available for purchase in this release.
ProCurve Manager Plus
ProCurve Manager Plus 2.0 (PCM+) is licensed by number of network devices (switches
and access points) managed. There are two levels of license: 100-device limited
license, and an unlimited device license.
Note: Licenses for PCM+ 2.0 work for PCM+ 2.1
- 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 from PCM 1.6 - 100-device license
- J8779A ProCurve Manager Plus 2.0, upgrade PCM 2.0 100-device license to an unlimited device license
Note: To upgrade from PCM 1.6 to the PCM 2.0 unlimited license, you must
purchase both the 100-device license (J8991A) and the unlimited license (J8779A)
ProCurve Mobility Manager
ProCurve Mobility Manager 1.0 (MM 1.0) is a plug-in module to PCM+ 2.0 (PCM+
2.1) that provides additional management capabilities for ProCurve wireless
access points.
- J8990 ProCurve Mobility Module 1.0
ProCurve Identity Driven Manager 2.0
ProCurve Identity Driven Manager 2.0 (IDM 2.0) is a fee-based upgrade to IDM
1.0. For IDM 2.0, there are two levels of license, based on the number of managed
users. The base product license is for 500 users, and you can purchase additional
2000-user licenses as needed to manage large user environments.
- J9012A ProCurve Identity Driven Manager 2.0 base product - 500-user license
- J9013A ProCurve Identity Driven Manager 2.0 base product - upgrade from IDM 1.x
to IDM 2.0, 500-user license
- J9014A ProCurve Identity Driven Manager 2.0 additional 2000-user license
Free Trial Versions
This compressed, ZIP-format file contains a 30-day free trial of these three
products:
- ProCurve Manager Plus version 2.1,
- ProCurve Mobility Manager version 1.0., and
- ProCurve Identity Driven Manager version 2.0
NOTE: In order to use the trial version of ProCurve Identity
Driven Manager v 2.0, you must install it on a system that does not have a previous
version of ProCurve Identity Driven Manager installed.
These release notes include information on the following:
NOTE: These Release Notes are applicable at the date of the ProCurve Manager
Version 2.1 Release. Please check the ProCurve
Support Web site for more recent information.
New Features
Below is a summary of the new features
that are available in ProCurve Manager Plus (PCM+) with this release. Please
refer to the ProCurve Manager Network Administrator's
Guide for a full description on the use of these features:
ProCurve Manager Plus v2.1 Features:
- The Device Manager feature now lets you assign "friendly"
port names to simplify tracking of port configurations throughout the
network. When the "Use Friendly Port Names" option in the
Device Preferences is enabled, PCM will display the friendly port name
instead of the interface name.
- Ability to target hosts with policies if identified by Connection-Rate-Filtering
(CRF) and InMon Security (IS) events. This allows you to configure a policy
that is triggered by CRF or IS events, which will look-up and target the switch
port that the identified host is connected to.
- Configuration Manager now generates events when a configuration change
is detected on a device. These events can be used to trigger alerts
that notify the network administrator of the configuration change.
- The Find Node feature has been enhanced to provide improved performance.
Mobility Manager 1.0 Features:
ProCurve Mobility Manager (MM) is a simple yet powerful management tool
to centrally configure, update, monitor and troubleshoot a ProCurve wireless
LAN. Mobility Manager extends the capabilities of ProCurve Manager Plus,
with functions specific to the management of wireless APs, including radio
properties and configuration of WLANs.
- Mobility Manager discovers and gathers wireless access point (AP)
and radio information and displays it in the PCM GUI.
- With Mobility Manager you can perform commonly used operations on
multiple radios simultaneously, such as setting the channel, transmission
power, RF detection parameters, and radio state.
- Mobility Manager lets you review and revise security related information
in“WLAN security configurations”. These include SSID, VLAN, closed
system, encryption, authentication, and key management for static WEP, WPA-PSK,
and RADIUS authentication servers.
- You get easy to use wizards for deploying WLAN security configurations
across multiple radios, as well as dialogs for managing keys, such as
static WEP, WPA-PSK, and RADIUS authentication server secret keys.
Identity Driven Manager 2.0 Features:
- User-based ACLs for configuring user access to network resources.
- Importing of users and groups from MS Active Directory, LDAP, or XML files
is now supported with an easy to use User Import wizard. You can also use
the wizard to synchronize user entries in IDM to the source data.
- Integration with standards-based endpoint integrity solutions that let you
incorporate the endpoint integrity status with the access profile applied
when a user is authenticated.
.
- Support for Funk Steel-Belted RADIUS.
- Global rules that can be applied to all users, or individual users or access
groups. This lets you manage network access for special cases, such as for
preventing log ins during network maintenance or site shutdowns.
- User Session information to help you track usage patterns for specific users.
The session information also provides a "Find User" feature so you
can trace the user by name or MAC address.
- Improved, easier to use GUI, simplifies the configuration and set up process
in IDM.
- New reports and reporting improvements, and performance and scalability
improvements.
Installation Requirements– PCM 2.1 Standalone Version
Minimum System Requirements
- 2 GHz Intel Pentium IV or equivalent
- 1 GB RAM
- 1 GB free hard disk space
Recommended System Requirements
- 3 GHz Intel Pentium IV or equivalent
- 2 GB RAM
- 2 GB free hard disk space
Supported Operating Systems:
- MS Windows 2003 Server
- MS Windows XP Professional (SP 1 or greater)
- MS Windows 2000 Server, Advanced Server or Professional with SP
4 or better
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.
Installation Requirements– PCM-NNM Version
Following are the requirements for installing the ProCurve Manager for HP Openview
Network Node Manager (PCM-NNM), for managing ProCurve network products in a
multi-vendor environment.
Minimum System Requirements
- 1 GHz Intel Pentium IV or equivalent
- 1 GB RAM
- 1 GB free hard disk space
Recommended System Requirements
- 2 GHz Intel Pentium IV or equivalent
- 2 GB RAM
- 2 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
NNM Versions that should be installed prior to PCM 2.0 install
- NNM 6.41 on Win 2000 Professional, Windows 2000 Server, Windows
2000 Advanced Server, Windows XP
- 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.
Installation Notes - General
- Note: Once you install PCM or PCM+ version 2.1, you cannot
revert to the previously installed version. If you are uncertain if you want
to upgrade to the 2.1 version, it is best to install it on a system that does
not have any earlier versions of PCM or PCM+ installed.
- Once the PCM installation starts to copy files to your system, do not cancel
out of the installation. Please finish the installation, and then run the
uninstall via "add/remove programs" in the Windows control panel
to remove the installed files. If you do cancel out, you may not be able to
uninstall.
- If you are upgrading from ProCurve Manager 1.6, back up the \PNM\server\db\solid.db
database file before beginning the installation wizard. This will allow you
to restore your data in the event that the existing database gets lost or
corrupted during database migration
- If you are upgrading ProCurve Manager 2.0, back up the \PNM\server\mysql
directory before beginning the installation wizard. This will allow you to
restore your data in the event that the existing database gets lost or corrupted
during database migration.
- ProCurve Management software is not localized for non-English versions of
Windows.
One Network Management Program per Computer
Make sure you uninstall any other network management programs from your computer
before installing ProCurve Manager or ProCurve Manager Plus, because a resource
conflict will occur if you have multiple network management tools running on
the same computer, for example during discovery of the network devices.
Note : The above is not applicable when PCM 2.1
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
192.3.4.5 interface, and the ProCurve Manager server is running on the 10.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:
- Find the commIpAddr.txt
file. This file exists in the config directory, so for example, for the client this
file exists in: C:\Program Files\Hewlett-Packard\PNM\client\
config.
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 Files\Hewlett-Packard\PNM\server\config
directory.
- 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 " 10.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.
- Save your changes.
- 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.10.20.25, then you would enter "http://10.10.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 the PCM-NNM version, the PCM Remote Client can only be installed on machines
that have the NNM Remote console installed. Once installed, the client will
always connect to the server attached to the NNM remote console.
If a PCM remote client attempts to connect to a PCM server, and that server
has a firewall turned on, the PCM remote client will come up with the message
"no context defined" and a grey (empty) display. The firewall prevents
the PCM remote client from getting the necessary connection and data files
from the PCM server. You must disable the firewall on the PCM server, or configure
the firewall to allow the PCM remote client and PCM server to communicate.
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.
IP addresses
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:
10.255.124.84
10.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 Files\Hewlett-Packard\PNM\server\
). 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.
Passwords
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 a 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:
- First you must change an entry in the server\config\TyphoonServer.cfg
file.
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).
- Edit the access.txt file as described above, but instead of entering
an IP 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
- 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
= user_password
where user_password is the password the client will use to access
the server.
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.
Receiving Traps Using ProCurve Manager
A trap is an SNMP alert sent by a host 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. A 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 2000 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 server, 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 Users:
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.
Support for ProCurve Wireless Devices
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 software, the PCM Switch Software Upgrade utility will not allow
you to "downgrade" to an earlier version of the software.
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.
Support for ProCurve 9300 & 9400 Series Devices
The following are known issues when using PCM 2.1 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 of SNMPv3 and SSH Keys on 9300 series devices is not included with
PCM 2.1
- VLAN discovery will work for ProCurve 9400 devices; however, the VLAN Manager
configuration features are disabled.
- On the 9400s the sFlow SNMP MIB is only visible when sFlow has been previously
enabled via the device console. To ease the burden on the user, PCM will attempt
to enable the MIB during discovery using the configured CLI login parameters.
If these are not correctly configured, the 9400 will not be discovered as
an sFlow-capable device; this is evident when attempting to configure the
device for traffic monitoring as the Sampler column of the Traffic Device
Configuration screen contains "N/A". If this situation arises and
the user wishes to collect sFlow sampled data using PCM, the following steps
are required.
- The 9400 device must be deleted from PCM.
- The user must either manually enable sFlow on the device using its console
or must correctly configure the device's CLI parameters in PCM.
- The 9400 must be manually rediscovered from PCM. It should now appear
as a device on which sampling can be enabled.
Mobility Manager 1.0 Notes
- If the network contains access points that are not configured with the
default CLI passwords used by PCM then the elements associated with those
access points (e.g., radios, SSIDS) may not be discovered. The user should
either pre-configure the devices with the access credentials used by PCM
prior to starting discovery or wait until the device is discovered and use
the “Communication Parameters in PCM” wizard to override the
global defaults. You can then use Manual Discovery to re-discover the device,
and its related radios and SSIDs, or you can simply wait until the next
regularly scheduled discovery cycle collects the information.
Identity Driven Manager 2.0 Notes
- If you are upgrading IDM 1.0 to IDM 2.0, you must also upgrade the IDM
agent. On your system with the RADIUS server, download the latest IDM
agent install.exe via http://<hostname of IDM server>:8040.
Run this install.exe to upgrade to the IDM 2.0 agent. See the "Getting
Started Guide" for additional details.
- When upgrading from IDM 1.0 to IDM 2.0, if there are users logged in
prior to the upgrade the users will appear as logged in after the upgrade.
This is not necessarily a problem but, the users will never be shown as
logged out even after they logout. There are two possible fixes for this,
one is to make sure all users are logged out before the customer performs
the upgrade. The other is to reset session accounting statistics after
the upgrade has completed, this is done by navigating to Preferences ->
Identity Management and clicking on the “Reset accounting statistics”
link.
- When upgrading from IDM 1.0 to IDM 2.0 all previous user session histories
will be discarded.
- Depending on the number of users in your environment, IDM performance
may be degraded due to large number of events logged during peak usage
hours. Symptoms of this include:
- the login bar chart not reflecting the current number
of logins for a given hour,
- the users’ last login time not reflecting the
correct time, and
- more than the max allowed number of events in the
IDM and PCM event browser.
You can improve IDM performance in either of the following ways:
- turn off "Session Start/Stop events" in the Preferences
for Identity Manager, or
- by setting the "events to ignore: Link up and
Link down" options in the Preferences for Events (in PCM).
- If you experience problems with the Logins/Hour chart in the GUI after Daylight Savings Time,
you can restart the PCM/IDM server and GUI to work around the problem
- IDM now allows you to configure all 'default' attributes for users that
have not yet been configured in IDM to belong to a specific Access Policy
Group. In IDM 1.0, you could only set the "default VLAN". In
IDM 2.0, you use the 'Default Access Policy Group' to set any access rules
and rights to be applied to users that do not yet belong to an Access
Policy Group.
- If you experience performance issues on the PCM/IDM server, consider
turning off the "Session start and stop events" (from the Preferences
window under Identity Management). Session accounting will still be active,
but fewer events will be logged in the event browser.
- When using the IDM User Import function, even if no user is selected
to be removed a warning event is displayed in the IDM event viewer about
the users being deleted.
- When requesting reports and session information, there may be some delay
as the database is processed to find the matching records. This is normal
and a function of the size of the database and the performance of the
system on which PCM/IDM is running.
- By default you will receive warning messages when IDM sets attributes
(e.g. QoS, or rate-limits, or ACLs) that a specific device does not support
(e.g. an older device such as a 2500). If you wish to disable these messages
you can do so via the Preferences window under Identity Management.
- By default IDM does not show the Endpoint Integrity State as an input
to rules in Access Policy Groups. If you are using Endpoint Integrity,
you should enable this setting in the Preferences window under Identity
Management
Other PCM Known Issues
Installation
- PCM/PCM+ and Terminal Services are not supported on same server
Discovery
- 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 Discovery 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 93xx CLI:
snmp-server trap source ve 200
- Syslog trims entries after 1000 events based on severity,
so it trims the events with the lowest severity first.
Traffic Management
- 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.
- The link speed from a port is sometimes unavailable, meaning that it
is specified in the device's SNMP MIB as 0 (zero). Without link speed
PCM cannot present any traffic data as it is unable to compute a utilization
value. This causes PCM's traffic gauges to appear blank, without an internal
"needle". Depending upon the device, this can happen on Ethernet
ports that are not being used and may also happen on the WAN ports of
7000s that are running protocols other than PPP (note that traffic monitoring
of PPP over ISDN is unsupported). Traffic monitoring of HDLC and Frame
Relay WAN links on the 7000s will be available when a firmware update
provides link speed for those protocols.
- A bug in the SNMP library used by the traffic data collector can erroneously
cause an SNMP error to be reported by the PCM Events
viewer. This condition appears only for devices that cannot be used by
PCM anyway because another sFlow-capable management station has already
"locked" the sFlow MIB of the device. However, when this condition
is encountered it can generate a large number of events in a relatively
short time.
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.
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 configuration
changes.
- When RADIUS authentication for managers 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
"Test Communications Parameters" will not work.
Device Management
- When launching the “Communication Parameters On Device”
wizard a communication test is performed. If the device is unreachable,
or the CLI and SNMP connections cannot be established then a warning
is displayed. The user may continue to use the wizard but some operations
may fail as a result of the communication problem. It is recommended
that the user run the “Test Communication Parameters”
tool and resolve any problems reported.
SSH Support:
- SSH support is not enabled by default for 25xx series switches. To enable
SSH support the user should ensure that they have upgraded their 25xx
devices to a software version that supports SSH (F.04.08 or newer), and
then edit the files PNM\server\config\devconfig\sw25*.oid so
that the “isSSH=false” line is changed to “isSSH=true”.
Once this is done the PCM server services should be restarted. SSH support
should now be enabled on the 25xx devices.
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
November, 2005
Edition 2.1
Part #5990-8848
Trademark Credits
Microsoft and Windows, Windows
95, and Windows XP are registered trademarks of Microsoft Corporation. Internet
Explorer is a trademark of Microsoft Corporation.
Open Source Software Acknowledgement
PCM and PCM+ 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