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.
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.
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
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) |
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.
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.
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)
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.
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:
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.
For more details about the following features, see the NNM online help.
This document contains the following topics:
Platform | Hardware and Software Minimum Requirements |
---|---|
Red Hat Linux Advanced Server 2.1 |
|
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.
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.
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)].
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: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.
NNM currently only supports Apache on Linux
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.
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.
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.
To set locale for Mozilla, complete the following steps:
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.
This is currently not tested.
NNM is currently tested against Gnome and KDE desktop environments.
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.
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:
If you have a firewall installed on your system, you must make sure that it allows loopback (127.0.0.1) access.
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
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.
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.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.
$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/).
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.
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.
If you rearrange columns in an Active Table, you will be unable to launch from a selected row to another view.
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.
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.
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.
- You must first have the Java Plug-in installed. See Supported Configurations for instructions on installing the JPI.
- 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.
- Some of the views can take up to 90 seconds to display (longer for larger networks) - please be patient.
- 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.
- 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/).
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.
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.
Network Presenter with JPI 1.4.1 on Windows browsers does not repaint the panner window correctly.
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..."
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 netmonReturn to Known Problems
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.
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.
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
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.
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:
"ovdwconfig.ovpl -rdb OVoracle -type oracle -u <DBuser> -password <pass>", where <DBuser> is your oracle user and <pass> is that user's password. Oracle user OSauthentication is no longer supported.
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:
/opt/OV/bin/ovdwconfig.ovpl -env "ORACLE_HOME=/opt/oracle/product/7.3.3" \ -type oracle -rdb OVoracle
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
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:
- copy the $OV_DB/analysis/default/solid.ini file to $OV_DB/analysis/default/solid.ini.old file.
- Edit the $OV_DB/analysis/default/solid.ini file.
- Comment out the "At=<time> backup" entry, by inserting a ";" at the beginning of the line. An example would be:
;At=01:00 backup- 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.
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.
This section documents defects in all parts of the product which only occur in non-English (LANG="C", browser language = "en") environments.
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:
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.
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.
To work around this problem, complete the following steps:
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.
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.
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.
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.
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.
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
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.
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: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.
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:In the Alarm browser the Views sub-menu in the Actions menu has the following invalid links
HSRP ViewMan 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.
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.
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.
While launching any of the online help windows, the console may show an error as follows:
This warning may be ignored.
"Warning: Representation size 2 must match superclass's to override columns"
TIP: Look in the following directories for error log files and trace output. Look for the keyword "ERROR":
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/ifconfigThis 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'.
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:
ovstatus -c(or run from Start:Programs->HP OpenView->Network Node Manager->NNM Services - Start)
snmpwalk <nodename> systemIf it is having trouble starting (and the services indicate it will not start), try stopping the SNMP EMANATE Master Agent service, then run the following from a console window
snmpdm -d -apall
snmpwalk <nodename> ipAddrTableYou should get a screen full of data
ovtopodump -lYou should see the "NUMBER OF MANAGED NODES:" field greater than 2. To see which nodes have been discovered, run:
ovtopodump
snmpwalk <nodename> .1.3.6.1.4.1.11.2.17.4.1
snmpwalk <nodename> .1.3.6.1.4.1.11.2.17.4.4
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.
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:
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.
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:
- To test for topology data in your data warehouse:
echo select ip_hostname from nnm_nodes; |ovdwquery
- To test for event data in your data warehouse:
echo select message from nnm_event_detail; |ovdwquery
- To test for trend (snmpCollect) data in your data warehouse:
echo select descript_id from snmp_trend_dataset; |ovdwqueryYou can use the ovdbdebug command to test whether your database is functional.
See Reporting and Data Analysis with NNM for more information.
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.
The following sub-sections describe the changes pertaining to the NNM 7.0 product manuals on Red Hat Linux Advanced Server 2.1.
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:
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.