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
• Man Pages
• OV Web Help

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.

• Welcome to NNM

• Page Number: 1

  What It Was
  "Windows Operating Systems, HP-UX, and Solaris"
  
  Read As
  "Windows Operating Systems, HP-UX, Solaris, and Linux"
  



• Page Number: 17

  What It Was
  "On HP-UX systems"
  
  Read As
  "On HP-UX and Linux systems"
  



• Managing Your Network

• Page Number: 31

  What It Was
  "HP-UX and Solaris"
  
  Read As
  "HP-UX, Solaris, and Linux"
  



• Page Number: 72

  What It Was
  "On HP-UX systems"
  
  Read As
  "On HP-UX and Linux systems"
  



• Page Number: 100

  What It Was
  "HP-UX 10.X, 11.X and Solaris 2.X systems."
  
  Read As
  "HP-UX 10.X, 11.X, Solaris 2.X, and Linux 2.X systems.
  

  Page Number: 101

  What It Was
  "HP-UX 10.X, HP-UX 11.X, Solaris 2.X"
  
  Read As
  "HP-UX 10.X, HP-UX 11.X, Solaris 2.X, and Linux 2.X systems."
  



• Page Number: 102

  Add
  "Linux 2.X: /usr/openwin/lib/app-defaults"
  



• Integration Concepts

• Page Number: 1

  What It Was
  "Windows NT, Windows 2000, HP-UX, and Solaris"
  
  Read As
  "Windows NT, Windows 2000, HP-UX, Solaris, and Linux"
  



• Page Number: 28

  What It Was
  "HP-UX/Solaris"
  
  Read As
  "HP-UX/Solaris/Linux"
  



• Page Number: 28 and 47

  What It Was
  "HP-UX and Solaris"
  
  Read As
  "HP-UX, Solaris, and Linux"
  



• Page Number: 35

  What It Was
  "HP-UX or Solaris"
  
  Read As
  "HP-UX or Solaris or Linux"
  



• Creating and Using Reg Files

• Page Number: 1

  What It Was
  "HP-UX, Solaris, and Windows operating systems"
  
  Read As
  "HP-UX, Solaris, Linux and Windows operating systems"
  



• Page Number: 21, 52, 54, and 85

  What It Was
  "HP-UX and Solaris"
  
  Read As
  "HP-UX, Solaris, and Linux"
  



• Reporting and Datawarehousing

• Page Number: 1

  What It Was
  "HP-UX, Solaris, and Windows operating systems"
  
  Read As
  "HP-UX, Solaris,Windows, and Linux operating systems"
  



• Page Number: 53

  What It Was
  "To verify the amount of space available, type bdf -l on HP-UX or df -kl on Solaris systems."
  
  Read As
  "To verify the amount of space available, type bdf -l on HP-UX or df -kl on Solaris/Linux systems."
  



• Page Number: 55-56

  What It Was
  "Configures Net8. If the listener.ora and tnsnames.ora files do not exist, the files are created in the directory:
  HP-UX: /etc
  Solaris: /var/opt-oracle
  
  Read As
  "Configures Net8. If the listener.ora and tnsnames.ora files do not exist, the files are created in the directory:
  HP-UX: /etc
  Solaris: /var/opt-oracle
  Linux: $ORACLE_HOME/network/admin
  



• Page Number: 211

  What It Was
  "On UNIX, the following paths should be included to allow the ODBC drivers to be loaded when the ODBC applications are started:
  HP-UX: SHLIB_PATH=/opt/OV/iodbc/lib
  Solaris: LD_LIBRARY_PATH=/opt/OV/iodbc/lib"
  
  Read As
  "On UNIX, the following paths should be included to allow the ODBC drivers to be loaded when the ODBC applications are started:
  HP-UX: SHLIB_PATH=/opt/OV/iodbc/lib
  Solaris and Linux: LD_LIBRARY_PATH=/opt/OV/iodbc/lib"
  
  

• Page Number: 212

  What It Was
  "Check that the following ODBC data sources were created during the installation of NNM:
  
  Add
  For Linux:
  For the embedded database:
  tcpip 2690
  
  For Oracle 8.1.7 and 9.2.0, the data source should be Ovoracle.
  
  

• Page Number: 260

  What It Was
  "Export the OV directories so the database server can mount them."
  
  Add
  If NNM is on Linux:
  Modify the /etc/exports file as follows:
  
  /opt/OV DatabaseServerName(rw,no_root_squash)
  /etc/opt/OV DatabaseServerName(rw,no_root_squash)
  /var/opt/OV DatabaseServerName(rw,no_root_squash)
  
  On the command line, run exprotfs -av
  
  

• Page Number: 262

  What It Was
  "Copy the file with the bits (not the link) from this directory to the NNM library directory renaming the file as needed to either libclntsh.sl or libclntsh.so for the HP-UX and Solaris platforms, respectively:
  
  Read As
  
Copy the file with the bits (not the link) from this directory to the NNM library directory renaming the file as needed to either libclntsh.sl or libclntsh.so for the HP-UX, Solaris, and Linux platforms, respectively:



• Page Number: 265

  What It Was
  "All of the following commands must be executed on the NNM server regardless of the specific operating system:"
  
  Add
  If the NNM server is a Linux machine:
  /opt/OV/bin/ovdwcfggetset -file $DW_ENVIRS -s "=" \
  -set
  "LD_LIBRARY_PATH=$ORACLE_HOME/lib:/opt/OV/iodbc/lib" \
  >> /var/opt/OV/share/log/externalDbConf.log
  
  /opt/OV/bin/ovdwcfggetset -file $DW_CONF -s ": @" -set "dbname: OVoracle" \
  /var/opt/OV/share/log/externalDbConf.log
  
  

• Page Number: 271

  What It Was
  "On Solaris systems, consult your system documentation for information on accessing manpages online or printing them."
  On Windows systems, to view and print reference pages from the menu bar, select Help:NNM->Reference Pages.
  
  Add
  On Linux systems, consult your system documentation for information on accessing manpages online or printing them."
  
  

• HP OpenView Network Node Manager - A Guide to Scalability and Distribution

• Page Number: 113

  What It Was
  "Ensure that NFS is running on the server.
  
  Add
  On Linux:
  a. Run command:
  /etc/rc.d/init.d/nfs status
  
  b. If nfs is not running, start nfs using:
  /etc/rc.d/init.d/nfs start
  



• Page Number: 114

  What It Was
  "Configure the exportation of the HP OpenView file system to the client as follows:"
  
  Add
  For a Linux server, edit the /etc/exports file. You will either modify two existing lines or add new ones, depending on the contents of this file.
  
  Add the following lines:
  
  /etc/opt/OV/share <ip address of console> (rw, no_root_squash)
  /var/opt/OV/share <ip address of console> (rw, no_root_squash)
  
  Save and close the /etc/exports file.
  



• Page Number: 114

  What It Was
  "Run the following two commands to unexport and re-export the directories from the server:"
  
  Add
  On Linux:
  exportfs -ra
  



• Page Number: 117

  What It Was
  "Ensure that the console is running as an NFS client."
  
  Add
  On Linux:
  a. Run command:
  /etc/rc.d/init.d/nfs status
  
  b. If the processes are not running, run the following command:
  /etc/rc.d/init.d/nfs start
  



• Page Number: 118

  What It Was
  "Choose a mount point for the servers HP OpenView file systems. To make sure this file system is mounted at boot time, you must modify the appropriate file shown below. You must be root to modify these files. Replace server_name with the name of the server whose databases you want to use on this client."
  
  Add
  On Linux:
  a. Run these commands:
  mkdir -p /opt/OV/nfs/server/var/opt/OV/share
  mkdir -p /opt/OV/nfs/server/etc/opt/OV/share
  
  b. Run these commands:
  mount server:/etc/opt/OV/share /opt/OV/nfs/server/var/opt/OV/share
  mount server:/var/opt/OV/share /opt/OV/nfs/server/etc/opt/OV/share
  

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:

• ovcolqsql, ovcoltosql, ovdwevent, ovdweventflt, and ovdwquery

What It Was
"ODBC Datasource Configuration. ODBC datasources will either be preconfigured at NNM installation time, or may be created when installing the RDBMS. In UNIX environments, ODBC datasources are defined in the /opt/OV/odbc/system_odbc.ini file."

Read As
ODBC Datasource Configuration. ODBC datasources will either be preconfigured at NNM installation time, or may be created when installing the RDBMS. In UNIX environments, ODBC datasources are defined in the /etc/opt/OV/share/conf/analysis/system_odbc.ini file."



• ovtopmd

What It Was
FILES
The environment variables below represent universal path names that are established according to your shell and platform requirements.
See the ov.envvars(1) manpage for information on universal pathnames for your platform and shell.
IP topology database files: $OV_BIN/ovtopmd $OV_LRF/ovtopmd.lrflrf $OV_CONF/$LANG/filters

Read As
FILES
The environment variables below represent universal pathnames that are established according to your shell and platform requirements.
See the ov.envvars(1) manpage forinformation on universal pathnames for your platform and shell.
IP topology database files:$OV_BIN/ovtopmd$OV_LRF/ovtopmd.lrf$OV_CONF/$LANG/filters



• ovrepld

What It Was
-l filename
Sets the name of the log file to filename. The filename must include the full path of the file. The default log file is /var/opt/OV/log/ovrepld.log on HP-UX 10.x, HP-UX 11.x, and Solaris 2.x.

Read As
-l filename
Sets the name of the log file to filename. The filename must include the full path of the file. The default log file is /var/opt/OV/log/overpld.log on HP-UX 10.x, HP-UX 11.x, Solaris 2.x and Red Hat Linux Advanced Server 2.1



• ipmap

What It Was
Tracing
ipmap has three levels of tracing. You can trace traps from netmon, NNM events and other miscellaneous internal items. You turn on tracing using these nettl commands as root. Other platforms have different directory paths (see FILES):

nettl -e ovw -traceon mask -f /var/adm/nettlnettl
-e ovEXTERNAL -traceon mask -f /var/adm/nettl
where mask is the bit mask for the type of tracing that is desired.

Read As
Tracing
ipmap has three levels of tracing. You can trace traps from netmon, NNM events and other miscellaneous internal items. You turn on tracing using these nettl commands as root.
The following example is for HP-UX 10.x or 11.x or Linux platforms. Other platforms have different directory paths (see FILES):

nettl -e ovw -traceon mask -f /var/adm/nettlnettl
-e ovEXTERNAL -traceon mask -f /var/adm/nettl
where mask is the bit mask for the type of tracing that is desired.



• ovdwconfig.ovpl

What It Was
In UNIX environments, the ODBC datasource is configured in the /opt/OV/odbc/system_odbc.ini file;

Read As
In UNIX and Linux environments, the ODBC datasource is configured in the /etc/opt/OV/share/conf/analysis/system_odbc.ini file;



• ovrequestd

What It Was
HP-UX and Solaris:
/var/opt/OV/analysis/ovrequestd

HP-UX and Solaris:
/var/opt/OV/log

Read As
HP-UX, Solaris and Linux:
/var/opt/OV/analysis/ovrequestd

HP-UX, Solaris and Linux:
/var/opt/OV/log

What It Was
-l logdir
Note that if the default is used, ovrequestd must be run as user root or bin.

Read As
-l logdir
If the default is used, ovrequestd must be run as user root or bin for HP-UX and Solaris. Ovrequestd can be run as daemon for Linux.

What It Was
The user u and group ID that runs ovrequestd will be inherited also, with one exception: if ovrequestd is started as user root, it will change to be uid/gid of bin/bin for security purposes. However, ovrequestd shouldn't be run in the default server directory as any other user than root or bin.

Read As
The user u and group ID that runs ovrequestd will be inherited also, with one exception: if ovrequestd is started as user root, it will change to be uid/gid of bin/bin for security purposes. However, ovrequestd shouldn't be run in the default server directory as any other user than root or bin for HP-UX and Solaris. But for Linux, it can be run as a daemon.



• request_list

What It Was
HP-UX and Solaris:
/var/opt/OV/analysis/ovrequestd

HP-UX and Solaris:
/var/opt/OV/analysis/ovrequestd

Read As
HP-UX, Solaris and Linux:
/var/opt/OV/analysis/ovrequestd

HP-UX, Solaris and Linux:
/var/opt/OV/analysis/ovrequestd



• NNMReportPresenter

Read As
The Web browser's language preference (or the locale preference in the HP OpenView Launcher login screen) is used to select the preferred $LANG from the Report Presenter file system path.

For example, if the Web browser locale of Japanese [ja] the $LANG select would be ja_JP.SJIS on HP-UX, Japanese on Solaris, or Japan_Japanese.932 on the NT/2000 platform. If the index.html file cannot be found under the preferred $LANG directory the C directory's index.html file is used instead.



• OVsnmpIntro

What It Was
Communication with SNMP agents is supported over UDP/IP. The HP-UX and Solaris versions of the SNMP library only support SNMP communication over UDP/IP.

The SNMP communications API provides both blocking and non-blocking modes of communication. Further, extensions are provided to support native integration with Microsoft Windows32 (on Windows NT/2000) and X11 (on HP-UX and Solaris) asynchronous event-loop programming models.

Read As
Communication with SNMP agents is supported over UDP/IP. The HP-UX, Solaris, and Linux versions of the SNMP library only support SNMP communication over UDP/IP.

The SNMP communications API provides both blocking and non-blocking modes of communication. Further, extensions are provided to support native integration with Microsoft Windows32 (on Windows NT/2000) and X11 (on HP-UX, Solaris, and Linux) asynchronous event-loop programming models.

What It Was
FILES
The environment variables below represent universal path names that are established according to your shell and platform requirements. See the ov.envvars(1) manpage for information on universal pathnames for your platform and shell.

HP-UX and Solaris 2.x
/$OV_PROG_SAMPLES/ovsnmp_app/*

/$OV_HEADER/OV/OVsnmp*.h

/$OV_LIB/*.[sl|a]

Read As
FILES

The environment variables below represent universal path names that are established according to your shell and platform requirements. See the ov.envvars(1) manpage for information on universal pathnames for your platform and shell.

HP-UX, Solaris and Linux 2.x
/$OV_PROG_SAMPLES/ovsnmp_app/*

/$OV_HEADER/OV/OVsnmp*.h

/$OV_LIB/*.[sl|a]



• OVwRegIntro

Read As
Label

Label for the button. This is a required field. If the label starts with (@), it is interpreted as the name of an image file.
HP-UX, Solaris, and Linux Only: If the label contains two image file names separated by a (:), the first image is displayed when the button is active and the second image is displayed when the button is unavailable.

Return to Man Pages

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.

• Tasks
• Dynamic Views Tasks
• Configuring Extended Topology
• Using Active Tables in Dynamic Views
• Using Visual Cues in IPv6 Views
• Understanding IPv6 Status
• Understanding the Status of HSRP Groups
• Troubleshooting Views when Running NNM Extended Topology
• Problem Diagnosis Tasks
• Syslog Integration Tasks
• Customer Views Tasks
• Concepts
• Dynamic Views Concepts
• Extended Topology Discovery Status
• Problem Diagnosis View
• VLAN View
• Overlapping Address Domain View
• OSPF View
• IPv6 Network View
• IPv6 Node Detail
• IPv6 Interface Detail
• IPv6 Prefix Groups
• HSRP View
• Problem Diagnosis Concepts
• Syslog Integration Concepts
• Customer Views for NNM Concepts

Return to OV Web Help