NNM 7.5 Release Notes Update

Last Updated: 10 August, 2005


This document contains updates to the HP OpenView Network Node Manager 7.5 Release Notes.  Updated information since the product was released is contained in this page.   This page is kept in reverse chronological order, so newer problems are listed toward the top.

Some other useful links which might help you include:


08/10/2005: Documentation Error in Release notes in the Internationalization (I18N and L10N) Section of the Known Problems and Workarounds Chapter.
03/29/2005: Attention HP-UX 11.0 and HP-UX 11.11 Customers: Read this before NNM7.X software installation
03/29/2005: Documentation Error: NNM7.5 Release notes
07/28/2004: NNM 7.x does not support OVO licenses and licenses of earlier versions of NNM
07/28/2004: Report Presenter shows garbled characters in Microsoft Internet Explorer with Japanese(ja) language option enabled
07/28/2004: IPv6 nodes show critical status on Windows XP systems
07/28/2004: Nodes show critical status on Windows XP systems with Service Pack 2 installed
07/28/2004: Attention HP-UX 11.0 and HP-UX 11.11 Customers: Read this before NNM7.5 software installation NNM supports 64-bit Oracle databases


Documentation Error in Release notes in the Internationalization (I18N and L10N) Section of the Known Problems and Workarounds Chapter.

Currently the documentation reads as "You cannot combine an ..." and lists a set of NNM views that either will not work, or will display in the server's language. The list of views did not include "Dynamic Views". Please include "Dynamic Views" also to the above list. This means, Dynamic Views will not work or will display in the server's language.

Attention HP-UX 11.0 and HP-UX 11.11 Customers: Read this before NNM7.X software installation

The NNM 7.X CD-ROMs use a new format that is somewhat different from older formats.

As a result, HP UX 11.0 and HP UX 11.11 systems require a system patch in order to read the CD-ROM properly. The CD-ROMs may appear to mount correctly on an unpatched HP UX 11.0 or HP UX 11.11 system. However, software installation will fail, because the system can not find certain files on the CD ROM.

Note that the issue is in reading the CD-ROM, not in the NNM installation process. Therefore the solution is to patch the system where the CD-ROM will be mounted, which is not necessarily where NNM is to be installed.

Visit http://www4.itrc.hp.com/service/index.html and follow the "patch database" link to download the appropriate patch for your system:

HP-UX 11.0: PHKL_28060 - s700_800 11.00 Y2k; Rock Ridge extension for ISO-9660
HP-UX 11.11: PHKL_28025 - s700_800 11.11 Rock Ridge extension for ISO-9660

Apply the patch on the system where the CD-ROM will be mounted as follows:
1. Unpack the patch using this command: sh
2. Apply the patch using this command: swinstall -s .depot

NOTE: This patch requires a system reboot.

Then proceed with software installation as usual, according to the Release Notes and Quick Start Installation Guide.


Documenation Error: NNM7.5 Release notes

OpenView Operations subsection under the "Compatibility Network Node Manager and 3rd Party Applications" section of the NNM7.5 Release notes, reads as "OpenView Operations (OVO) for Unix 7.1 is being tested with NNM 7.5, and we will announce compatibility when testing is complete". Please read this statement as "OpenView Operations (OVO) for Unix 8.1 is being tested with NNM 7.5, and we will announce compatibility when testing is complete".


  • NNM 7.x does not support OVO licenses and licenses of earlier versions of NNM

    NNM7.0 introduced a new product structure. Thereby, NNM 7.x supports only new NNM licenses. Refer the release notes for more information on the product structure changes.

    For OVO installations that upgrade to NNM 7.x, OVO does not stop working and does not loose any functionality on migration, since OVO with NNM 7.x recognizes the NNM AE instant-on unlimited license which is an enterprise license. Please refer to the release notes for the versions of OVO supported with NNM7.x.

    For earlier release NNM installations that upgrade to NNM7.x, NNM does not stop working and does not loose any functionality on migration, since the upgrade process installs an NNM AE unlimited instant-on license which is an enterprise license. Please refer to the migration guide for the supported migration paths to NNM7.x from earlier versions.

    Customers of earlier versions of OVO or NNM should contact the support centre to request an appropriate NNM 7.x permanent license, before the installed NNM AE instant-on unlimited license expires.


  • Report Presenter shows garbled characters in Microsoft Internet Explorer with Japanese(ja) language option enabled

    When the Report Presenter is invoked from Microsoft Internet Explorer with Japanese(ja) language option enabled, garbled characters are displayed if the NNM server is on Solaris platform.

    The problem occurs due to a mismatched codeset selection by the server side programs, on Solaris platforms, that exchange data with the browser side applications.

    To correct this problem, change the codeset used by server side web applications by executing the following command:

       $OV_BIN/ovchange_locale_mapping -sjis

    See ovchange_locale_mapping(1) man page for more information.


  • IPv6 nodes show critical status on Windows XP systems

    On Windows XP, two versions of IPv6 networking were released. The first was a Developer Beta version, and the second was an official release version known as the Advanced Networking Pack for Windows XP. Given the official release version, the condition exists that there is now a firewall. By default, the firewall disables all inbound IPv6 packets, and as such, all IPv6 pings fail.

    This can be disabled by invoking "Start->Control Panel->Administrative Tools->Services->IPv6 Internet Connection Firewall", setting the starting of the service to "Manual" and stopping the service. The other option is to determine what systems are responding to IPv6 ping requests and have the firewall configured to allow these devices to send packets back to the management station.

    In either case, both problems result in the IPv6 view showing nodes that are normal being marked critical (displayed as the node symbols being red).

    For details on configuring the IPv6 firewall, see the documentation for the Advanced Networking Pack or visit http://www.microsoft.com/.


  • Nodes show critical status on Windows XP systems with Service Pack 2 installed

    Windows XP Service Pack 2 introduced a number of security changes. One of these was to merge the firewall for IPv4 and IPv6 into one firewall. Additionally, this firewall is enabled by default. This firewall can be disabled by invoking "Start->Control Panel->Administrative Tools->Services->Internet Connection Firewall", setting the starting of the service to "Manual" and stopping the service. The other option is to determine what systems are responding to ping requests and have the firewall configured to allow these devices to send packets back to the management station.

    For details on configuring the firewall, visit http://www.microsoft.com/.


  • NNM supports 64-bit Oracle databases

    A comment in the Support Matrix references that Oracle is only supported in 32-bit versions on HP-UX and Solaris. This statement was removed in the NNM 7.5 Release Notes, but it needs to be made clear that NNM does support 64-bit Oracle.

    It is not the case that the Oracle database server is 64-bit. Some versions of 64-bit Oracle did not deliver 32-bit Oracle database drivers. Given that NNM is 32-bit, NNM would not have a valid database driver to operate.

    NNM now relies upon a database driver provided by the ODBC vendor called OVoraWire. With this driver, NNM is assured that a 32-bit driver exists.