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.

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.

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.

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

• UNIX: $OV_CONF/OVPI_INTEGRATION
• Windows: %OV_CONF%\OVPI_INTEGRATION

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.

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.

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

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:
http://<ovpi_server>:<ovpi_port>/reports/launchpad?p_Device=<node_selected>
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.

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, including 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.
   

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.

QXCR1000243798: If OVPI and NNM are installed in non-English systems (Chinese, Korean and or Japanese), the Thresholds alarm category does not get added to the NNM alarm browser.

Workaround: Perform the following steps to fix the defect related to the threshold alarm category:

1. On the NNM system, go to the following directory:
   Windows: %OV_MAIN_PATH\OVPI_NNM_Integ
   Unix: $OV_MAIN_PATH/OVPI_NNM_Integ
2. Run one of the following commands:
   Windows: xnmevents –merge ovpiException_win.conf
   Unix: xnmevents –merge ovpiException_ux.conf
3. Run the following command:
   xnmevents –event

QXCR1000233804: If OVPI and NNM are installed in non-English systems (Chinese, Korean and or Japanese), NNM cannot pass event data to the NNM Event Report Pack.

Workaround: Perform the following steps to workaround the defect:

1. Download the following patch from the OVPI Report Pack patch site (http://support.openview.hp.com/patches/patch_index.jsp?fromOV=true):
   OV_Integration_L10N_patch.zip

2. Unzip the patch to one of the following directories:
   Windows: %OV_MAIN_PATH\OVPI_NNM_Integ
   Unix: $OV_MAIN_PATH/OVPI_NNM_Integ

3. Navigate to the appropriate directory:
   Windows: %OV_MAIN_PATH\OVPI_NNM_Integ
   Unix: $OV_MAIN_PATH/OVPI_NNM_Integ
4. Locate the following perl script:
   ovpi_agg_evtdump.ovpl
5. Copy ovpi_agg_evtdump.ovpl to the following directory:
   Windows: %OV_BIN%
   Unix: $OV_BIN/{OV_INSTALL}\bin\

On Windows only: NNM must use Solid as its data repository on Windows operating systems. The NNM and OVPI Integration Module does not support the configuration of Oracle as NNM's data repository on Windows.