HP OpenView Network Node Manager and Performance Insight Integration Module

Release Notes

November 2004

This document provides an overview of the changes made to the HP OpenView Network Node Manager and Performance Insight Integration Module (NNM and OVPI Integration Module) for version 2.0. It contains important information not included in the manuals or online help.

In This Version
Installation Notes and Installed Files
Software and Hardware Requirements
Installation Problems
Known Problems, Limitations, and Workarounds
Verified Environments


In This Version

The objective of the NNM and OVPI Integration Module is to provide a symbiotic integration between HP OpenView Network Node Manager (NNM) and HP OpenView Performance Insight (OVPI). The integration of the fault management capability of NNM with the performance management capability of OVPI enhances the user's fault diagnostic capabilities.

The following list provides functionality new to this NNM and OVPI Integration Module release:

Installation Notes

Instructions for installing the NNM and OVPI Integration Module are documented in the NNM and OVPI Integration Module User Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the Reporting and Netowrk Solutions CD media as:


After installation the document can be found at:


Software and Hardware Requirements

Before installing the NNM and OVPI Integration Module, make sure that your system meets the following minimum requirements:

Installation Problems

OVPI packages of NNM and OVPI Integration Module Fail to Install on Windows

The installation of Report Packs fails on Windows operating systems in which the OVPI product has been installed in a directory location that contains spaces in the name. It is recommended that OVPI be installed in a directory location that does not contain spaces.

Uninstalling NNM and OVPI Integration Module Leaves ICO_RNS Service on Windows

QXCR1000191673: When you uninstall the NNM and OVPI Integration Module from a Windows system, the ICO_RNS service remains on the Windows system. Disable this service to avoid a service startup error at boot time.

Known Problems, Limitations, and Workarounds

Specifying Fully-Qualified Hostname for OVPI Server During Installation of NNM Components

When configuring the NNM server to support the NNM and OVPI Integration Module, you must enter the fully-qualified DNS name or IP hostname for the OVPI server. If Netscape is used as the default browser on the NNM server, a non-fully-qualified OVPI server hostname is modified, appending www. at the beginning and .com and the end. This results in the use of www.<hostname>.com as the URL, which causes the report launching functionality to fail.

Uninstalling the NNM and OVPI Integration Module on an NNM Server

The uninstall.ovpl script is provided in the following directories:

When using this script to remove the integration components from the NNM server, stop all ovw sessions (ovstop ovsessionmgr) prior to running the script. Failure to do this causes ovw sessions to be in an inconsistent state, where OVPI items remain on menus, but the menus do not have application registration files defining actions.

OVPI-THRESHOLD-CLEAR Event Displays Incorrect Message in the NNM Alarm Browser

The OVPI and NNM Integration Module forwards OVPI-THRESHOLD-CLEAR events to the NNM management station with an incorrect message identifying the events as Breach events. Thus, the OVPI-THRESHOLD-CLEAR events display as Breach events in the NNM alarms browser.

Workaround: Use the NNM Event Configuration utility to modify the event message. From the Event Configuration window, select the OVPI enterprise and double-click OVPI-THRESHOLD-CLEAR. Modify the event message by changing the word Breach to Clear.

Unable to Open NNM Event Reports on Windows

Note: This problem occurs only when NNM is running on a Windows operating system.

When using the NNM and OVPI Integration Module in conjunction with the OpenView Performance Insight NNM Event Report Pack, NNM may not be able to access its version of Perl. As a result, NNM Event reports may not generate properly.

On the NNM management station, modify the Windows PATH environment variable so that the path to NNM's copy of Perl is listed first. When NNM is installed in its default location, the following must be added to the beginning of the Windows PATH environment variable:
C:\Program Files\HP OpenView\bin\Perl\bin

OVPI Launch Pad Menu Does Not Display in Shortcut Menu of Dynamic Views

On some machines, the OVPI Launch Pad shortcut menu command does not appear in Dynamic Views even if you have OVPI installed and configured.

Workaround: Type the following URL in a web browser:
where ovpi_server is the fully-qualified DNS address of the OVPI server, ovpi_port is the port number of the OVPI web site, and node_selected is the name of the NNM device with which to open the OVPI Reports Launchpad.

OVPI Cannot Request Node List from NNM

The nodeList.ovpl script is used to send OVPI a list of the nodes NNM manages so the two can routinely synchronize device information. If OVPI does not correctly produce the node synchonization list after installation of the NNM and OVPI Integration Module, and no errors were reported after installation, it could be that the .ovpl extension was not registered as an executable in the IIS server configuration during the installation of NNM.

To register the .ovpl extension, do the following:

  1. Open the Add/Edit Application Extension Mapping window.
  2. In the Executable field, enter the following, inclusing the quotes:
    “C:\Program Files\HP OpenView\bin\Perl\bin\perl.exe” “%s” “%s”
  3. In the Extensions field, enter the following: .ovpl
  4. In the Verbs pane, make sure All Verbs is checked.
  5. Select options: Script engine and Check that file exists.

Node List Filtering Feature Unavailable When NNM Runs on Windows

QXCR1000195972: When NNM is installed on Windows operating systems, the node list filtering feature is unavailable. Due to user permissions issues on Windows, the scripts that export the list of devices from NNM to OVPI cannot be run by the web server. Instead, the export is scheduled once a day, and all of the nodes are exported.

Solid as NNM's Database on Windows

On Windows only: NNM must use Solid as its data repository on Windows operating systems. The IP Telephony SPI does not support the configuration of Oracle as NNM's data repository on Windows.

Verified Environments

High Availability

The NNM and OVPI Integration Module has been verified to work in high availability environments. To setup the high availability environment, you must install and configure the NNM and OVPI Integration Module on both the active and standby management stations.

Please contact HP technical support for specific configuration needs.

NNM and OVPI on Separate Servers

NNM and OVPI are not supported on the same server.


Please visit the HP OpenView web site at: http://www.managementsoftware.hp.com/

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

You can also go directly to the support web site at:


HP OpenView online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valuable support customer, you can benefit by being able to:

NOTE: Most of the support areas require that you register as an HP Passport user and log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:


To register for an HP Passport ID, go to the following URL:


To view release notes and user manuals for the NNM and OVPI Integration Module:

  1. Click using our products --> product manuals.

    The product manuals search window opens. It is located at:


  2. In the select product list, click Reporting and Network Solutions.
  3. In the select version list, click 7.0.
    To view archived versions of the release notes and user guides, select another version number from the list.
  4. In the OS list, select an OS type.
  5. To start the search, click Open or Download.

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL:


)Copyright 2004 Hewlett-Packard Development Company, L.P.