Installing Network Management Software Applications

To extract the StreamView LS-Topology Map software from tape:

# ovinstall -r -p LS-TOPOMAP -- -d <tape-drive>

Figure 3-2 shows a typical screen display that results from execution of the preceding ovinstall command to extract the StreamView LS-Topology Map software from tape.

Figure 3-2 : Screen Display During StreamView LS-Topology Map Extraction

To extract the CiscoView-2020 monitor software from tape:

# ovinstall -r -p CISCOVIEW-2020-- -d <tape-drive>

Figure 3-3 shows a typical screen display that results from executing the above ovinstall command to extract the CiscoView-2020 monitor software from tape.

Figure 3-3 : Screen Display During CiscoView-2020 Monitor Extraction

Step 6 Update the HP OpenView Fields database with StreamView or CiscoView fields by issuing the following command:

# ovw -fields

See the section "Sample Output from HP OpenView Fields Command" in the "StreamView Output Samples" appendix for sample output generated by this command.

Step 7 Ensure that the network management software application has been installed properly by issuing the following command:

# ovw -verify

The verify program takes less than a minute to run and prints the names of verified objects. If the verification process fails, a message on the screen so indicates. In this case, call your service representative for assistance.

See the "Sample Output from HP OpenView Verify Command" section in the "StreamView Output Samples" appendix for sample output generated by the ovw -verify command.

Step 8 Issue the following command to check the status of the HP OpenView daemons:

# ovstatus

If the ovstatus command returns the following message:

"ovstatus: ovspnd is not running; use ovstart to start ovspnd"

issue the ovstart command from "user ID root," as shown below:

# ovstart

Step 9 To update variables associated with the SNMP community, execute the xnmsnmpconf command at the shell prompt.

This command displays the SNMP configuration screen. When displayed, double-click on the "Default" parameters field (which contains default values in text fields). Modify the following field values to read as shown:

Port (remote) 161

Timeout 6.0

Retry 2

The default polling interval is 5 minutes, which determines how long it will be before the display indicates changes in the network. Setting the polling interval to a value less than 5 minutes causes additional SNMP traffic to be generated and is, therefore, not advised.

By default, LS2020 nodes require the use of the "write" community for SNMP set operations, as indicated below:

set community: write

However, you may choose to use another name for the community that has read/write privileges, or you may choose to allow SNMP set operations from any community.

To allow such operations, however, you must configure the HP OpenView environment appropriately using the xnmsnmpconf command.

Alternatively, you can change the files at the LS2020 nodes to conform to the behavior of HP OpenView.

See the LightStream 2020 Network Operations Guide for additional information about setting up SNMP communities in an LS2020 network.

Step 10 Verify that the /etc/services file contains the following lines:

snmp 161/udp
snmp-trap 162/udp

If these lines are not present in the /etc/services file, create them. To do so, as "user ID root," open the /etc/services file with the vi editor:

# vi /etc/services

Insert the snmp 161/udp and snmp-trap 162/udp lines in the appropriate location in the /etc/services file and close the file.

The installation of the network management is now complete. The next section describes how to create a user environment for running network management software applications under HP OpenView.

Setting Up a User Environment Under HP OpenView

This section describes how to set up the StreamView and CiscoView applications to run under HP OpenView on the NMS. Each NMS user intending to run StreamView or CiscoView under HP OpenView must perform the procedures in this section.

These procedures assume that you have already installed the network management software applications on your NMS, as described in the preceding section, "Installing Network Management Software to Run Under HP OpenView.

This section provides instructions for setting up the user environment for the Bourne shell (sh and bash) and the C shell (csh). For clarity, the setup procedures for the Bourne shell and the C shell are discussed under separate headings below.

Other shells may differ in details; in the case of another shell, consult the applicable documentation for that shell.

In preparation for setting up the user environment under HP OpenView, determine the type of shell each user is using.

In an NFS environment that uses the Network Information Services (NIS) facility, enter the following command:

# ypmatch <username> passwd

In an environment that does not use the NIS facility, enter the following command:

# egrep <username> /etc/passwd

The shell can be identified from the last field of the password entry, as shown in the following example:

jjones:o@elQMkzZv7o F:10563:312:Jon Jones:/home/jjones:/bin/bash

Setting Environment Variables for Bourne Shell and Derivatives

To set up the network management software to operate under HP OpenView and the Bourne shell, perform the following procedures:

Step 1 From your home directory, edit the .profile file or the .bash_profile file that is read by the Bourne shell on login.

Add the following lines to the end of the file:

PATH=$PATH:/usr/OV/bin/ls_bin
export LSC_DATABASE=/usr/OV/databases/ls/configure.netdb
export LSC_CFGLOGPATH=/usr/OV/log
export LSC_CFGTCPPORT=6789
export XKEYSYMDB=<pathname>/XKeysymDB
export NMSROOT=/usr/OV/bin/ls_bin