HP OpenView Network Node Manager 7.0

Runtime Release Notes

For the Red Hat Linux Advanced Server 2.1 Operating System

Copyright © 1990-2003 Hewlett-Packard Development Company, L.P

To view these Release Notes as one document suitable for printing, click here.
Post-release updates to this document are available here.

Congratulations on your purchase of HP OpenView Network Node Manager 7.0 (NNM) for the Red Hat Linux Advanced Server 2.1 operating system! HP OpenView Network Node Manager is the industry-leading network management solution, and we're proud to have you join the HP OpenView family. We thank you for purchasing HP OpenView Network Node Manager for Red Hat Linux Advanced Server 2.1, and we hope this product exceeds your network management expectations. See the table of contents in the left frame for the topics that are included in these release notes or click here to bring up the frame version of the Release Notes.

Licensing

NNM comes with a 60-day password that is activated during installation. It comes with an unlimited node license for 60 days. Before 60 days elapse, you must request a permanent password.  To request a permanent password, from the command prompt run ovnnmPassword, or pick [OK] when the NNM user interface prompts you to request your password.

It is recommended that you request your permanent password immediately.

NNM Starter Edition

Part Numbers for NNM 7.0

If you want to run HP OpenView Remote Consoles, you do not need an additional  license or password for each remote console as long as the HP OpenView Management Server has a valid password.

If you change the IP address of your management station, you will need to request a new password. Fill in the form:
$OV_CONF/OVLicense/forms/nnm/$LANG/server_move.txt

Note:
The license installed is AE Instant-On, and the product features are restricted to NNM Starter Edition (Classic) only.

Feature comparison of NNM7.0 on Linux with other Platforms

Feature NNM 7.0 on Linux (Starter Edition) NNM 7.0 On HPUX/Solaris/Windows (Starter Edition)
Discovery, polling, events, data collection, and reporting YES YES
Layer 3 discovery YES YES
Layer 2 discovery NO NO
Out-of-the-box event filtering YES YES
Out-of-the-box event correlation BASIC BASIC
Reporting YES YES
Duplicate IP Addresses NO NO
Distribution (act as an MS) NO (CS only) NO (CS only)
New home base GUI YES YES
Dynamic views YES (Basic views) YES (Basic views)
Third-party integration YES YES
Out-of-the-box vendor icons, traps, etc. YES YES
Integration with customer views NO YES
Correlation composer YES (OV_NodeIf circuit only) YES
Path analysis NO NO
Support for high availability NO YES
Upgrade to advanced edition NO YES
Internationalization YES YES
Support for non-english locales YES(Japaneese EUC and simplified Chinese will be supported in NNM7.01) YES(Japaneese(EUC,ShiftJIs, and Simplified Chinese will be supported in NNM7.01)
Documentation Linux-specific changes are not incorporated into all the documents, but they are mentioned in the release notes. All documentation changes are incorporated.
Database support Oracle 8i and 9i Oracle 8i and 9i (Additionally, MSSQL for Windows)

Configuring Discovery with Custom Installation

See Managing Your Network with NNM, Chapter 5 for information about the choices available for customizing and troubleshooting NNM's discovery process. For more information, see the subsequent sections in this document.

If you wish to delay the discovery process until after you decide which configuration choices to implement:

When you are ready to run discovery, open NNM's user interface and select Options:Network Polling Configuration. Then enable the IP Discovery:Discover new IP nodes  field.

Improving Performance

You can improve the performance of your NNM management system in several ways. See the latest versions of the HP OpenView Network Node Manager Performance and Configuration guide which will be available at:
    http://ovweb.external.hp.com/lpe/doc_serv/. From this URL, choose the product "Network Node Manager". Choose a Release. Select either the Performance and Configuration Guide or Managing Your Network.

Online and Printable Documentation

NNM includes a library of detailed reference materials for your use. They are shipped as Adobe's Portable Document Format (.pdf) files, and viewed through your web browser.  Adobe's Acrobat Reader can be installed from http://www.adobe.com/products/acrobat/.  You can use Netscape's Help:About Plug-Ins to see which plug-ins are enabled.  For Japanese browsers, be sure to download the Acroread ASIAN Font Pack. from http://www.adobe.com/products/acrobat/acrrasianfontpack.html.

The following manuals are provided with NNM, and are available from the Help menu of ovw, or in the $OV_WWW/htdocs/LANG/manuals directory. 

Numerous additional HP OpenView online manuals are available at the following web site:  http://ovweb.external.hp.com/lpe/doc_serv/ (for Adobe Acrobat .pdf documents)

Compatibility Between Network Node Manager and 3rd Party Applications

Network Node Manager 7.0 for Redhat Linux Advanced Server 2.1 has not been tested with any third-party applications.

Customers developing applications on top of NNM 7.0 for Linux should use GNU C and C++ compiler version 2.96 for smooth integration.

3rd Party Symbols and Jovw/Dynamic Views

If your 3rd Party application contains custom bitmaps and/or symbol definitions (i.e. CiscoWorks 2000) and you want them to be available in either Jovw or the Dynamic Views, you must take additional steps:

Join the OpenView Forum User's Group

The OpenView Forum is an association of users and developers of OpenView network and system management solutions. OpenView Forum was formed as a non-profit corporation by four of the largest licensees of HP OpenView (Duke Power, GTE Government Systems Corporation, Martin Marietta and US WEST) to represent the interests of OpenView users and developers world-wide.

If you are an OpenView end user or developer, OpenView Forum is your voice to vendors of OpenView products. Become a member and make sure that OpenView vendors listen to your requirements. OpenView Forum is your advocate.

For more information about the OpenView Forum, conference, or for a membership application, visit http://www.ovforum.org/.

OpenView Forum is an independent corporation, not affiliated with Hewlett-Packard Company.

What's New in Network Node Manager 7.0

For more details about the following features, see the NNM online help.

NNM 7.0

NNM on Linux

NNM 7.0 is now available on Red Hat Linux Advanced Server 2.1.

Network Node Manager 7.0
Supported Configurations


This document contains the following topics:

Hardware and Software Minimum Requirements

Platform Hardware and Software Minimum Requirements
Red Hat Linux Advanced Server 2.1
  • Intel P4 or higher processor with internal memory of 512 MB RAM or more
  • Minimum 1 GB disk space
  • 8 GB disk space for smooth operation
  • Network card with TCP/IP configured

You can refer to the Install Guide for information on prerequisites and installation requirements. The installation process does not enforce all the prerequisites. One of the prerequisites which is not enforced is the disk space requirement.

Supported Web Browsers

The following browsers are supported with NNM 7.0. For an updated list of browser support, visit http://ovweb.external.hp.com/nnm/NNM7.0/relNoteUpd/relNoteUpdate.htm.

For additional limitations on browsers running in non-English locales, see Supported Non-English Locale Configurations.

Client Operating System Supported Browsers Where to Download
HP-UX 11.11
HP-UX 11.0
Netscape Navigator 7.0
Mozilla 1.4
note: Mozilla 1.4 incorrectly reports userAgent as Windows instead of HP-UX, so if you have no JPI, you'll get redirected to the wrong site to download the plug-in.  Instead, follow the link below to get the HP-UX plug-in
http://www.hp.com/workstations/risc/standard/software/netscape/netscape.html
http://www.hp.com/products1/unix/java/mozilla/index.html
Solaris 9
Solaris 8
Netscape Navigator 7.0
Mozilla 1.2.1
http://www.sun.com/solaris/netscape/
http://wwws.sun.com/software/solaris/browser/index.html
Windows XP
Windows 2000
Internet Explorer 6.0
Netscape Navigator 7.0
Mozilla 1.4
http://www.microsoft.com/windows/ie/default.htm
http://home.netscape.com/download/
http://www.mozilla.org
Red Hat Linux Advanced Server 2.1 Mozilla 1.4 and Netscape 7.1 http://www.mozilla.org
http://home.netscape.com/download/

The gcc3-3.0.4-1 package must be installed as part of the operating system.

Java Plug-in (JPI) Minimum Requirements

For information about the Java Plug-in, browse to http://java.sun.com/products/plugin/index.html.

Server Operating System Supported Java Plug-in Where to Download
HP-UX 11.11
HP-UX 11.0
JPI 1.4.1.03 http://www.hp.com/go/java
Solaris 9
Solaris 8
The JPI is automatically installed with supported browsers.
Netscape 7.0 automatically installs JPI 1.4.1.
Mozilla automatically installs JPI 1.4.2
http://java.sun.com/j2se/1.4.2/download.html
Windows XP
Windows 2000
JPI 1.4.2_01 http://java.sun.com/j2se/1.4.2/download.html
Red Hat Linux Advanced Server 2.1 JPI 1.4.2_01 http://java.sun.com/j2se/1.4.2/download.html

Dynamic Views require the Java Plug-in (JPI).  When you view one of the Dynamic Views, you will be prompted with a dialog such as

This page contains information of a type (application/x-java-applet;jpi-version=1.4) that can only be viewed with the appropriate Plug-in.
Click OK to download Plugin.

Installing the Java Plug-in

You must have installed gcc3-3.0.4-1 on your machine.
Source: http://plugindoc.mozdev.org/linux.html#Java [Then press HOWTO: Installing Java Plug-in(linux)].

For Mozilla 1.4.1/Netscape 7.1:
  1. To run Java applets, you must install the Java Run Time Environment (JRE) plug-in.
  2. Put a symlink to /usr/java/jre/plugin/i386/ns610-gcc32/libjavaplugin_oji.so in your plugins/ directory.

Note: If you copy the file instead of making the symlink, Java will crash.

If you are not familiar with symbolic linking and permissions, complete one of the following steps:

Note: To check which compiler was used to build Mozilla, see about:buildconfig (Mozilla 1.4a or later).

For the Netscape Installation with Java Plug-ins, follow the same procedure mentioned above but replace the mozilla directory with netscape in all the cases.

Signed Applet:
The Dynamic Views utilize a signed applet, allowing this applet to create local files and launch applications.  When running a Dynamic View you will get a dialog like:
        "Warning - Security"
        "Do you want to trust the signed applet distributed by "Hewlett-Packard"?  Publisher authenticity verified by: "VeriSign, Inc.".
Click "Always" and you will not be prompted with this dialog again.

Non-English Users Note:
When you first download the JPI, at the "Select Java(TM) Plugin Installation..." dialog, be sure to set your Locale to "International".  Otherwise, your Internet Explorer browser will disappear every time you load a Dynamic View.

Supported Web Servers

NNM currently only supports Apache on Linux

Supported External Databases for NNM Data Warehouse

If you are using the embedded database that is installed with Network Node Manager, you have no additional requirements.  If you want to run an enterprise database, the following external databases are supported:
Operating System Supported Databases
Red Hat Linux Advanced Server 2.1 Oracle 9.2.0.3
Oracle 8.1.7

The listener.ora and tnsnames.ora files can be located at $ORACLE_HOME/network/admin.

For Oracle, the following products are required to run together with NNM.

HP only supports 32-bit Oracle on HP-UX and Solaris.

Supported Non-English Locale Configurations

A single installation of Network Node Manager can support multiple locales. NNM 7.0 is internationalized. Follow your system's instructions to set the locale appropriately. Other languages can be set to get locale specific values such as dates, sorting/collation, character handling, and currency. Various parts of Network Node Manager  force LC_NUMERIC to be C to enforce consistent use of ',' instead of '.' for numbers.

Non-English Web UI

Use ovchange_locale_mapping on the NNM server to ensure that the NNM and browser codesets match.

(Unix only) Be sure that the ovspmd process (started upon bootup via /etc/init) has the correct locale set, or the web-based alarm browser will not have localized categories. This happens if ovalarmsrv is running with LANG=C in its environment.  The environment is set at the time ovstart is first run, usually at the operating system startup, and is passed to its child processes, such as ovalarmsrv.  Running 'ovstop ovalarmsrv; ovstart ovalarmsrv' will not change the parent's environment. Often the operating system has the default language of "C" when it first starts, so this environment is passed indirectly to ovalarmsrv. To work around this problem, set the correct language variable (such as 'export LANG=ja_JP.eucjp') into the /sbin/init.d/ov500 file. Or after every re-boot, run ovstop;ovstart with the correct $LANG in the environment.

Setting Locale for the Browser

Mozilla/Netscape

To set locale for Mozilla, complete the following steps:

  1. Open a Browser.
  2. In the Edit Menu, click Preferences.
  3. In the Left Pane(Category) of a Preferences Dialog, collapse the Navigator Tab and inside that, select Languages.
  4. From the listed Languages, select one corresponding to system locale.
  5. You can select a particular codeset to be used also from the same window.

Configuring Internet Explorer Web Browser/Java Plug-in to Display Other Locales

NNM supports web browsers configured for various different languages. The following is an example of how to configure these languages.

A Japanese web browser pointed at a system which supports multi-locales will display Japanese characters, while an English web browser will display English when pointed at the same system.  This requires that the Japanese locale be installed on the server for Unix systems. With Internet Explorer browser you can adjust your locale by selecting Tools:Internet Options and clicking the Languages... button.  To view Japanese, select Add... and make  "Japanese [ja]" the first item in the list.  Note that an input method must also be selected, and it must be configured via the Regional Settings of the Windows Control Panel.

If you get a message like:

Cannot set locale LC_ALL to [system default]. Be sure the locale is set on the machine (check the "Language settings for the system" in Control Panel's Regional Options)

it is likely that you need to set the Control Panel's Regional Options "Your locale (location):" field to Japanese.  Windows 2000: If this field is not available, you need to check it in the "Language settings for the system" section.

Be sure to set the Fonts correctly, so you can display Japanese fonts.  Do this from Internet Explorer by picking "Tools:Internet Options", General tab, pick "Fonts...", and change "Language script:" to "Japanese".  For English systems this should be set to "Latin based".

On Windows, if the English version of the Java Plug-in (JPI) is installed instead of the International version, the Dynamic Views will cause Internet Explorer to immediately disappear without a message.

Supported PC-based X Window Emulators

This is currently not tested.

Supported Desktop Environments

NNM is currently tested against Gnome and KDE desktop environments.

Network Node Manager 7.0
Known Problems and Workarounds

General Information

See the Release Notes addendum for any more recent updates or workarounds.

For information on getting the Java Plug-in or checking for patches, see the Supported Configurations document.

There is also a troubleshooting section below.

Known Problems

Installation

Using an NFS mounted CD drive for installation

When exporting a remote CD drive to be used for installing NNM, you must specifically give 'root' access to the drive. Use a line similar to the following on the machine that has the CD drive installed on it:

Return to Known Problems

System Firewall Configuration

If you have a firewall installed on your system, you must make sure that it allows loopback (127.0.0.1) access.

Return to Known Problems

Printing on Linux

The xpr rpm package should be installed on the system in order to facilitate printing on Linux. The server should be configured for Printing options for Dynamic Views and all the other applications

Requesting Evaluation Licenses for ECS Designer

Use the forms in the $OV_CONF/OVLicense/nnm/forms/C directory to make password requests for the "HP OpenView ECS Designer for the NNM product. The forms in the $OV_CONF/ecs/forms/C directory are for the standalone ECS Designer product only and should not be used.

Return to Known Problems

Rpm Error During Installation

While installing NNM the following error may occur -

rpmdb: region error detected; run recovery.
error: db4 error(-30981) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30981)
The following command has to be run to remove this error.
$ rpm --rebuilddb
The installation has to be repeated from the beginning. The installation so started may give errors because of the previous installation failure. In such a case nnm must be uninstalled and then NNM has to be re-installed.

Return to Known Problems

Dynamic Views

Labels

Changing labels in ovw will not affect the label seen in any Dynamic Views.  This is because the labels come from topology, and ovw stores labels locally.

Return to Known Problems

Right-Click

Right-click menu items may drop off the bottom of the visible pane in the web browser, especially when clicked near the bottom of a page with scroll bars. The workaround is to use scrollbars to move the node to the middle of the visible area and then right-click.

Return to Known Problems

Name Services

Your name services must be consistent between the server and the remote browser.  If the management station name (automatically defined in $OV_DB/openview/ovwdb/ovserver) does not resolve from the browser system correctly as the management station's IP address, the Dynamic View applet will not load.  This misconfiguration will also manifest as no images displayed in the index page (http://<MACHINENAME>:7510/topology/).

Return to Known Problems

Help on Active Tables

Dialogs launched from active tables contain a "Help" button that is not functional. General help on active tables is available here:
http://<machine>:3443/OvCgi/OvWebHelp.exe?Context=cxttsk&Content=cnttsk&Scope=scptsk&Topic=UsingTables
The ":3443" is only required on Unix servers and may be removed for Windows servers.  This information covers most active table features in the context of direct access from a table, rather than through subordinate dialogs.

Return to Known Problems

Authentication and Authorization

If you configure secure access to a particular view, and then incorrectly enter the user name and password, you will not get a second chance.  You must restart your browser to regain access.

Return to Known Problems

Active Table and Rearranging Columns

If you rearrange columns in an Active Table, you will be unable to launch from a selected row to another view.

Return to Known Problems

Node Details

There are two ways to get to Node Details, either double click on the node (or Active Table entry), or to select and pull down either the right click menu or View:Details.

With Overlapping Address Domain nodes, only the double click method works, the other will return a failure.

With nodes which were filtered out during Extended Topology discovery, only the menus will work, double click will return a failure.

Workaround:  If the View:Details menu fails, try double click, if double click fails, use View:Details.

Return to Known Problems

Dynamic Tables Sorting

After clicking on a table header column in a Dynamic Table to sort, you cannot click again to reverse sort.

Workaround:  Right click on the column heading and then pick Ascending or Descending to sort.

Return to Known Problems

Known Problems with Web Browsers

Web Interface

Ensure that you have the latest browser.  You must also have the Java Plug-in installed.  See Supported Configurations for more information on which browsers are supported and how to install the JPI.

Dynamic Views

Return to Known Problems

JPI 1.4.1 and Entity Expansion

JPI 1.4.1_03 (and greater) have a system property to limit the number of entity expansions in an XML document.  Unfortunately, the system property is by default not readable.  Therefore, an attempt to access this property fails, causing any expansion to fail.

The workaround for this problem is to add the following two lines to the section marked "grant" in the file "JRE_PATH/lib/security/java.policy" (where JRE_PATH is the path to the 1.4.1_03 JRE, typically C:\Program Files\Java on Windows and /opt/java on Unix systems).

permission java.util.PropertyPermission "entityExpansionLimit", "read";
permission java.util.PropertyPermission "disallowDoctypeDecl", "read";

All browsers will need to be closed, and the java cache may need to be cleared.

Return to Known Problems

Web Interface - HP OpenView Launcher

Can't get the Java based web Launcher (ovlaunch.exe URL) to come up

Do Not Close Launcher Window

Do NOT close the Launcher window, itself, when launching applications. Some applications use the frames within the Launcher window for executing web scripts. If the Launcher window is closed, it will cause the application that was launched from the window to close. This is particularly true when launching the HP OpenView Network Presenter. The Launcher window may be iconified to remove its presence instead of being closed.

Return to Known Problems

Web Interface - Network Presenter

Network Presenter with JPI 1.4.1 on Windows browsers does not repaint the panner window correctly.

Return to Known Problems

Web Interface - SNMP MIB Browser

On Windows XP, the system must be rebooted after initial installation of NNM for the Web SNMP MIB browser to work. This reboot allows IIS to reconfigure permissions properly. You may see the following text: "The specified CGI application misbehaved by not returning a complete set of HTTP headers..."

Return to Known Problems

Web Interface - Report Configuration/Report Presenter

If you schedule PingResponseTime and PingRetries reports, the reports are created, but will not begin collecting data until you complete one of two additional steps: either run xnmpolling -event, or do the following:

    ovstop netmon
    ovstart netmon
Return to Known Problems

Web Interface - SNMP Data Presenter

If using a proxy server, and the DNS server running on the proxy server cannot resolve an NNM data presenter hostname, the graphic lines for the tree structure cannot be located, and will appear as generic icon symbols. If this happens, disable use of the proxy server, clear the browser caches, and reload the page. If the problem persists, modify the http configuration file on the http server to provide the fully qualified name of the http server:

http server running on UNIX systems:

The configuration file is /opt/OV/httpd/conf/httpd.conf, and the entry to be modified is the ServerName entry. After saving the new configuration, you must restart the http server. This is accomplished with ovstop followed by ovstart.

Return to Known Problems

Web Interface - Correlation Composer GUI

If multiple users start the Composer GUI, or a user starts multiple Composer GUIs from the ECS CMG Composer 'Modify' button, and changes are made to the Correlators, only the last 'Save' will be preserved. The other user changes will be lost.

Return to Known Problems

Web Interface - ovweb

ovweb is a utility program which is used to start a preferred web browser and launch a specified URL. 

Now, with NNM 7.0, you only need to escape these special characters if you're running from the command line and it's required by your shell. You don't need to escape them an additional time for ovweb itself. For example:

ovweb "http://somewhere.com?foo=1&bar=2"

or

ovweb http://somewhere.com?foo=1\&bar=2

Return to Known Problems

Data Warehouse

When using databases other than the embedded database, the user needs to manually instantiate the data warehouse schemas using ovdwconfig.ovpl before using the data warehouse.

Using Oracle:

All export tools are enabled for ODBC.  To use Oracle, sql*net must be installed and configured.  A default datasource has been configured in the /etc/opt/OV/share/conf/analysis/system_odbc.ini file, OVoracle.  To switch over, change the "ServerName" parameter in that file to your server as defined in tnsnames.ora.
Then run:

To configure $ORACLE_HOME for use by the NNM Data Warehouse tools, you can use the "env" parameter on ovdwconfig.ovpl to place the value of ORACLE_HOME in the ovdwenvs.conf file. For example:

Return to Known Problems

Oracle SID may be misconfigured on HP-UX, Solaris, and Linux systems

On HP-UX, Solaris, and Linux systems, the file listener.ora may be misconfigured to have the Oracle SID set to "openview" even if the Oracle SID is not "openview". Rerunning ovdbsetupo3.sh will report this as an error if  $ORACLE_SID is not "openview". To correct this, edit listener.ora to the name to be the value of $ORACLE_SID.

The listener.ora and tnsnames.ora files can be located at:

HPUX 11.X: /etc/listener.ora
SOLARIS 2.X: /var/opt/oracle/listener.ora
LINUX 2.X:$ORACLE_HOME/network/admin

Return to Known Problems

Using ovbackup and the NNM Data Warehouse

If you are using ovbackup.ovpl and are using the NNM Data Warehouse, when the ovbackup.ovpl command is executed, it will also instruct the Embedded Database server to initiate the online backup. In order to allow a roll-forward recovery the default backup schedule must be deactivated. The process for doing this is:

  1. copy the $OV_DB/analysis/default/solid.ini file to $OV_DB/analysis/default/solid.ini.old file.
  2. Edit the $OV_DB/analysis/default/solid.ini file.
  3. Comment out the "At=<time> backup" entry, by inserting a ";" at the beginning of the line. An example would be:
    ;At=01:00 backup
  4. Save the $OV_DB/analysis/default/solid.ini file.

The embedded database will now be backed up only when the ovbackup.ovpl command is run. If use of ovbackup.ovpl is stopped at a future this, the default backup should be reinstated by copying the $OV_DB/analysis/default/solid.ini.old back to $OV_DB/analysis/default/solid.ini.

Return to Known Problems

Remote Consoles

For Japanese Windows 2000/XP Remote Consoles connecting to HP-UX or Solaris or Linux Management Stations, the 3rd party NT NFS product must be able to resolve the Japanese_Japan.932 symbolic links in the registration, symbols, and conf subdirectories. If the ovw menus and symbols on the Remote Console are in English, this means that the symbolic links are not working correctly. For the third party NFS product Disk Access, you need to enable symbolic links from the Disk Access applet in the Control Panel, not from the Administrator Utility.   The default for Disk Access is to not enable symbolic links.

Remote consoles are not tested against Samba servers for Red Hat Linux Advanced Server 2.1.

Return to Known Problems

Internationalization (I18N)

This section documents defects in all parts of the product which only occur in non-English (LANG="C", browser language = "en") environments.

Unsupported: Do not mix languages on client and server for CGI-based views.

You cannot combine an NNM application that supports one language with a server that supports a different language. The following NNM views either will not work, or will display in the server's language:

Return to Known Problems

Supported Locale Names

The following are the locale names supported by NNM for Linux:

Hence, the $LANG variable should be set to these names in order to run NNM in Traditional Chinese or Korean locales. Other possible $LANG settings are not supported for Korean and Traditional Chinese.

Return to Known Problems

Accessing Web UI using Traditional Chinese or Korean browser (Netscape or Mozilla)

If any of the Web UIs is accessed from a Traditional Chinese or Korean browser, then the date/time and the Traditional Chinese or Korean character names may appear as square boxes.

Workaround

To work around this problem, complete the following steps:

  1. Close all instances of the browser.
  2. cd <Java Plugin install directory/lib>

  3. Eg: cd /usr/java/j2re1.4.2_01/lib
  4. Locate the following file:

  5. For Traditional Chinese: font.properties.zh_TW.Redhat8.0
    For Korean: font.properties.ko.Redhat8.0
  6. Create new files by copying the above mentioned files as follows:

  7. For Traditional Chinese: cp font.properties.zh_TW.Redhat8.0 font.properties.zh_TW.Redhat
    For Korean: cp font.properties.ko.Redhat8.0 font.properties.ko.Redhat
  8. Edit the font.properties<.Language>.Redhat file.

  9. The file will have font specification entries of the form:
    "-b&h-luxi serif-bold-i-normal--*-%d-*-*-p-*-iso8859-1"
    Ensure that these fonts are available on your system.
  10. Start the browser.

The above steps will enable the correct language-specific fonts to be displayed in the Web Interfaces. However, the following problem may still remain:
When network presenter is launched and any symbol with Traditional Chinese/Korean name is selected and right clicked, an incorrect symbol name appears in the popup window.

Return to Known Problems

Symbols with Traditional Chinese/Korean Names

The text boxes of the NNM GUIs, which allow users to enter symbol/map names, will show wrong characters when Traditional Chinese/Korean characters are given as input for symbol/map names. However, normal operations can be performed on these symbols.

Return to Known Problems

Running OVW in Traditional Chinese/Korean Locales

When a symbol is selected in ovw, running in T.chinese or Korean locales, and right clicked, the screen may blink. If the right click causes the screen to blink, then a drag operation needs to be performed on any symbol in the submap, to stop the blink. However, this symptom may be seen only once, whenever the X-server is restarted.

Return to Known Problems

Data Warehouse

There are a number of fields in the Data Warehouse that contain localized data. These fields are:

As a result of the localized data in the nnm_event_cat table, the data in the "Alarm Category" column of the Alarms By Category report will be localized. In addition, the data in the "category" column of the "Alarms By Severity" detail report will be localized. As a result of the localized data in the nnm_event_sev table, the data in the "Alarm Severity" column of the Alarms By Severity report will be localized. In addition, the data in the "Severity" column of the "Alarms By Category" detail report will be localized. As a result of the localized data in the nnm_event_detail table, certain text in the message fields of both the Alarms By Severity and the Alarms By Category will be localized.

The "high_time" and "low_time" fields from the nnm_event_thresh table are not used in any of the reports provided with NNM. These fields are localized because they are populated from a localized version of the trapd.conf file by ovdwevent. The version of trapd.conf that is used as a data source is determined by the local set when ovdwevent is run.

Return to Known Problems

Printing with Web-based Alarm Browser

The web-based alarm browser does its printing through ovalarmsrv.  The printer connected to the machine running ovalarmsrv must support multi-byte characters in order to print Japanese output.  There is no way to pass arguments to the printer, so the printer must have something similar to a '-japanese' option enabled by default to the lp command.

Return to Known Problems

Printing Submaps on Unix with ovw

If you need to pass options to your printer so that it will print in landscape and Japanese, you can set the environment variable $OVwLpOpts before running ovw, so that the time string at the bottom of the printed output will print properly.  For example, you can set:

    export OVwLpOpts="-olandscape -ojapanese"
Return to Known Problems

Do Not Intermix Locales with the Topology/Map Databases

When NNM is first installed, the topology/map databases will contain labels in that locale.  Submap names are created in this locale, and should be accessed through that same locale.

You must plan which language will be used for NNM. Once a locale is chosen, it is very hard to change it. This is because NNM does not support mixed locale string in the topology and map databases. Once it is decided which locale is to be used, perform the following steps.

  1. Set $LANG to the desired locale. (e.g. LANG=ja_JP.eucjp; export LANG)
  2. Install NNM with exported LANG environment
  3. Stop OV processes (ovstop)
  4. Re-start OV process with desired LANG environment (ovstart)
  5. Setup Bootup scripts. Edit /sbin/init.d/ov500 as follows (this example uses SJIS on HP-UX):
        'start')
            if .........
            case `uname` in
             ...........
            HP-UX)
                ECHO_CMD=$ECHO_CMD_HP
                OVHOME=/opt/OV
                PATH=/bin:/usr/bin:/etc:$PATH
                export PATH LANG=ja_JP.eucjp # Add following 2 lines
                export LANG                               # if want to set LANG=SJIS
                ;; 
  6. Set the default WEB locale if you want to change locale from default:
    # ovchange_locale_mapping [-sjis | -euc]
    (Default locale)
    HP-UX ja_JP.SJIS
    Solaris ja

Return to Known Problems

The "More Information" Window

The "More Information" window launched from OVW-> Help -> About HP OpenView ->More Info shows date/time as garbage in Traditional Chinese/Korean.

Return to Known Problems

Tools

This section documents all the known problems in the tools that NNM includes.

Snmpget and snmpset Do Not Work the Same Way as in HPUX/Solaris/Windows

NNM ships snmpget, snmpset, snmpwalk, snmptrap commands. But, these commands are also being shipped by the ucd-snmp package in Red Hat Linux Advanced Server 2.1. By default, the ucd-snmp command utils are placed under /usr/bin whereas NNM-supplied commands are installed under /opt/OV/bin. Hence, when the user executes snmpget, first the ucd-snmp supplied snmpget command is executed, which does not behave the same way as the NNM-supplied commands.

To solve this problem, add /opt/OV/bin to path, in such a way that /opt/OV/bin is first in the path before /usr/bin.

Example:
For ksh users:
$ export PATH=/opt/OV/bin:$PATH
For csh users:
$ setenv PATH /opt/OV/bin:$PATH

Return to Known Problems

hpuxagt Not Available on Linux

The emanate SNMP agent shipped along with the NNM does not contain hpuxagt, and this is not ported for Linux.

Return to Known Problems

Fault->Network Connectivity->Locate via:SNMP not Working for Linux Nodes

Fault->Networking Connectivity->Locate via:Snmp needs certain features supported by the hpux agent, which is part of Emanate Suite of snmp agents. But, hpuxagt is not ported on to Linux. This feature will not work against Linux nodes, but this feature should work against non-linux nodes running hpuxagt supplied as part of HP's Emanage Agent suite.

Return to Known Problems

ovperms.ovpl

The ovperms.ovpl script is not available on Linux.

Return to Known Problems

Snmp Agent Start Script is Called ovsnmpd

The script used to start the snmp agents and the sub agent is renamed as ovsnmpd and installed under /usr/sbin.

Return to Known Problems

Snmpdm Log File

On other platforms, Snmpd.log is created in /var/adm whereas on Linux, it is created under /etc/SnmpAgent.d.

Return to Known Problems

Ovstop Does Not Kill All the Instances of OVAS

When ovstop is executed, it may not kill all the instances of ovas. Because of this, when ovstart is executed after ovstop, ovas will not start successfully.

To work around this problem, kill all the instances of ovas before doing ovstart.

Return to Known Problems

Conflicting Man Pages for snmp Commands

NNM ships man pages fpr snmpget, snmpset, snmpwalk, snmptrap commands. But, these commands are also being shipped by the ucd-snmp man package in Red Hat Linux Advanced Server 2.1. By default, the ucd-snmp command man pages are installed under /usr/share/man/man1 whereas NNM-supplied man pages are installed under /opt/OV/man. Hence, when the user executes 'man snmpget', since the ucd-snmp supplied man page path comes before the NNM's installed man path, the user cannot see the man page shipped by NNM.

To work around this problem, add /opt/OV/man to MANPATH in such a way that /opt/OV/bin is first in the search path before /usr/bin.

Example:
For ksh users:
$ export MANPATH=/opt/OV/bin:$MANPATH
For csh users:
$ setenv MANPATH /opt/OV/bin:$MANPATH

Return to Known Problems

Invalid Links in the Views sub-menu of Actions menu in Alarm browser

In the Alarm browser the Views sub-menu in the Actions menu has the following invalid links

HSRP View
IPv6
VLAN

Online Help and Man Pages

This section documents all the known problems in the online help system that NNM includes.

Man Pages for certain deamons and commands are not found

Man pages for daemons and certain commands are placed under /opt/OV/man/man1m for NNM and /opt/OV/man/man1m.Z for ecs tools. To view the man page for these commands the man section should be specified in the command line (e.g. man 1m netmon, man 1m.Z ecsmgr).

Alternatively, 1m and 1m.Z may be added to the MANSECT variable in the /etc/man.config file (e.g. MANSECT 1:8:2:3:4:5:6:7:9:tcl:n:l:p:o:1m:1m.Z). This enables man to search the additional directories man1m and man1m.Z without command line parameters.

Return to Known Problems

Size of the Online Help Window

The size of the online help windows of NNM when using GNOME as the desktop is inconsistent. When the right scroll bar is not visible, the arrow keys or the PgUp/PgDwn keys should be used for scrolling.

Return to Known Problems

Content of Online Help

The "Using Help" option in ovw Help menu brings up a window titled "HP OpenView Windows Help". This window contains information about Using the online help itself. The displayed content may contain information specific to CDE (Common Desktop Environment). All the information specific to CDE will hold good only if CDE is being used as the Desktop Environment. It will not hold good for GNOME and KDE.

Return to Known Problems

Warning message on Console

While launching any of the online help windows, the console may show an error as follows:

"Warning: Representation size 2 must match superclass's to override columns"

This warning may be ignored.

Return to Known Problems

Troubleshooting

TIP: Look in the following directories for error log files and trace output. Look for the keyword "ERROR":

Windows 2000/XP:
\<installdir>\log\*.* and \<installdir>\tmp\*.*
UNIX and Linux:
$OV_SHARE_LOG, $OV_PRIV_LOG, and $OV_TMP

Troubleshooting Installation

See Managing Your Network with NNM for information about starting with a well-configured network for best results. If during installation NNM complains that your networking appears to be misconfigured, try the following. From a command prompt of the management system type:

    /sbin/ifconfig
This will display your Linux TCP/IP config, including your hostname. Then type:
    nslookup <YOUR_IP_ADDRESS>
where <YOUR_IP_ADDRESS> is the address reported by ipconfig. If the hostnames reported by ipconfig and nslookup don't match, then NNM won't work. If either command fails to give you a hostname, then DNS is likely misconfigured or not available. Verify that the result of this nslookup matches the result of 'ovw -server'.

Troubleshooting Discovery

NNM will automatically start up and begin discovering and displaying your network within five minutes of installation. However, if your discovery is not working (such as an empty internet icon on the top level map) or you would like to validate your installation, see Chapter 5 in Managing Your Network with NNM for information about troubleshooting the Discovery process. The following may help you isolate any problems:

If NNM fails to discover all the nodes you expect to find in your local network, individually ping first your local node and then the missing nodes to verify connectivity (using the Fault:Ping" menu item). Validate that your node "knows" about these by selecting your management station icon and selecting the Configuration:Network Configuration->ARP Cache menu item. You should then see these new nodes in the ARP cache. Select your management station and select the Fault:Network Connectivity->Poll Node menu item to have the netmon process query your node again. The new nodes should then be added to the map.

Manually Seeding Discovery

If NNM fails to discover any nodes, you can manually seed discovery through the user interface or command line. See Chapter 5 of Managing Your Network with NNM and the netmon reference page in NNM's online help (or the Linux manpage) for details.

This is done by adding a node at the internet level which supports SNMP.  Even if this node is not really a gateway, NNM will properly discover the device, create the necessary networks, and place it in the appropriate network.  Verify the node supports SNMP by running:

    rnetstat -I <nodename>
To manually add this node through NNM's user interface:
  1. Open NNM's user interface.
  2. Go to the top level submap and select the internet icon.  Double click on it to get to the internet submap
  3. Pick Edit:Add Object  Select 'connectors' and 'gateway'
  4. Give the name of the gateway.  Double click on 'ipmap'
  5. Enter in the correct submap (important!) and the node name.  Hit [Verify] and [OK]

To manually add this node through a command line (you must know the correct subnet mask) run:

    echo <IPADDR> <NODENAME> | loadhosts -V -v -m <SUBNETMASK>

where <IPADDR> is the IP address of the node to add, <NODENAME> is the name of the node, and <SUBNETMASK> is the subnet mask for the network.  An example is:

    echo 192.18.1.1 myrouter | loadhosts -V -v -m 255.255.255.0

You can also manually seed discovery by using a seedfile.

After seeding discovery, you should see the map start displaying nodes based upon the information received from the node which supports SNMP, or see a list of nodes when running the ovtopodump command.

Troubleshooting Data Warehouse

Make sure the database is executing by running "ovstatus ovdbcheck".

You can verify that data exists in your data warehouse by using the ovdwquery command, such as:

You can use the ovdbdebug command to test whether your database is functional.

See Reporting and Data Analysis with NNM for more information.

Return to Troubleshooting

Updates to the Existing Documentation

The NNM 7.0 manuals are not updated with changes specific to Red Hat Linux Advanced Server 2.1. All procedural information will continue to be valid for NNM on Red Hat Linux Advanced Server 2.1 too, unless otherwise mentioned here in this section. However, an Installation Guide (part number: T2490-90003) is available, which describes the installation procedure for NNM 7.0 on Red Hat Linux Advanced Server 2.1

IMPORTANT: Read this section in conjunction with the manual set of NNM 7.0.

Product Manuals

The following sub-sections describe the changes pertaining to the NNM 7.0 product manuals on Red Hat Linux Advanced Server 2.1.

Return to Product Manuals

Man Pages

The NNM 7.0 man pages are not updated with changes specific to Red Hat Linux Advanced Server 2.1. All procedural information will continue to be valid for NNM on Red Hat Linux Advanced Server 2.1 too, unless otherwise mentioned in the following sub-sections:

OV Web Help

The following links in the Web Help are not relevant to this version of NNM. The users are requested to ignore these links and the information the links point to. The features described by these links are not supported.