Installing ViewRunner on Distributed Machines

5.1 Overview of the Distributed Installation

5.1.1 ViewRunner Database Machine

5.1.2 ViewRunner Server Machine

5.1.3 ViewRunner Client Machine

5.2 Procedures for a New Installation

5.3 Directory Structure for ViewRunner Server Applications

5.4 Directory Structure for ViewRunner Client Applications

Installing ViewRunner on Distributed Machines

5.1 Overview of the Distributed Installation

Installation of ViewRunner for HP OpenView in a distributed environment involves three separate installs on three separate machines.

5.1.1 ViewRunner Database Machine

Following are the basic steps for installing the ViewRunner database on the first machine:

Step 1 Verify that the Kernel parameters are defined in /etc/system and that the system has been rebooted.

Step 2 Install the Oracle database software (RDBMS, SQL *Net, TCP/IP Protocol adapter, Server Manager, and SQL *Plus) according to the instructions in the Oracle manuals. See "Sample of Oracle Database Installation," for a sample of the Oracle installation.

Step 3 Install the ViewRunner database package (CSCOvrdb) according to the instructions in this guide. See "Sample Transcript of ViewRunner Package Installation," for a sample transcript of the installation.

5.1.2 ViewRunner Server Machine

Following are the basic steps for installing the ViewRunner application server on the second machine:

Step 1 Verify that the operating system considerations have been followed.

Step 2 Install the Oracle client software (SQL *Net, TCP/IP Protocol adapter, and the optional SQL *Plus) according to the instructions in the Oracle manuals. See "Sample of Oracle Database Installation," for a sample of the Oracle installation.

Step 3 Install HP OpenView Network Node Manager (NNM) according to the instructions in the HP OpenView manuals. See "Sample of HP OpenView NNM Installation," for a sample of the HP OpenView NNM installation.

Step 4 Install the proper patch for HP OpenView.

Step 5 Install the ViewRunner server package (CSCOvrovs).

Note Make sure that you enter the same database parameters as those used in the ViewRunner database package.

5.1.3 ViewRunner Client Machine

Following are the basic steps for installing the ViewRunner client on the last machine:

Step 1 Verify that the operating system considerations have been followed.

Step 4 Install the proper patch for HP OpenView.

Step 5 Install the ViewRunner client package (CSCOvrovc).

Note Make sure that you enter the same database parameters as those used in the ViewRunner database package.

5.2 Procedures for a New Installation

Use the following procedures to install ViewRunner for the first time. If you are upgrading from a previous release of ViewRunner for HP OpenView, please refer to "Upgrading ViewRunner Software." You must be the root user to execute these commands.

Step 1 Make sure that all previous releases of ViewRunner for HP OpenView have been removed from your system by executing the following command:

pkgrm VRCLIENT VRSERVER

If you have ever installed a release of ViewRunner before this release, you must delete the old HP OpenView maps or go through the upgrade procedure for each map. If you don't want to save your old maps, you can delete the OpenView topology database before installing ViewRunner. See "Upgrading ViewRunner Software," for details on how to delete the OpenView topology database or for details on running upgrade.ksh to convert the old OpenView maps.

Step 2 Use the following command to change to the directory where the CD is mounted:

cd /cdrom/cdrom0

Step 3 Issue the pkgadd command to install the packages.

pkgadd -d .

Step 4 Install the ViewRunner database package on the first machine.

Step 5 Install the ViewRunner server on the second machine.

Step 6 Install the ViewRunner client on the third machine.

Note

"Installation Options" section

Step 7 If you have old ViewRunner maps that need to be converted, you need to do the following after all the packages are installed:

(a) Source the environment variables for the client and make sure your display is set to allow you to run an X terminal.

(b) Upgrade any of the HP OpenView maps that were created with an earlier version of ViewRunner.

$VRC_HOME/mcbin/upgrade.ksh

Step 8 Start the ViewRunner application.

ovw &

See "Upgrading ViewRunner Software," for details on running upgrade.ksh.

Step 9 Log in to ViewRunner using vradmin as the user id and cisco123 as the password.

Note

5.3 Directory Structure for ViewRunner Server Applications

Following is the directory structure created upon installation of the ViewRunner for HP OpenView server applications:

$VRS_HOME is the home directory for the Server installation.
$VRS_HOME/CMF contains the feature compatibility matrix (FCM) file.
$VRS_ HOME/NSS contains configuration save files.
- Each Cisco 6100 Series system has a subdirectory for its save files. The name of the directory is the same as the Cisco 6100 Series system IP address.
- You can control the number of save files stored by setting a parameter in the vrconstants.conf file. The default is 5.
$VRS_HOME/RDF contains the release definition file (RDF), which defines mappings between hardware versions and images for a particular system software release.
$VRS_HOME/bin contains the ViewRunner server binaries and the ViewRunner utility binaries and scripts.
$VRS_HOME/conf contains the configuration files.
- vrconstants.conf contains the ViewRunner server configuration parameters.
- eventcodes.conf contains mappings between event codes and alarm descriptions.
- vrlrcodes.conf contains mappings between CLEI codes and access identifiers (AIDs).
$VRS_HOME/env contains environment-variable scripts. These may also be located in a local bin directory, such as /opt/bin, if the installer chose this option.
$VRS_HOME/hpov contains files used to configure HP OpenView during installation. (This is not used after installation.)
$VRS_HOME/install contains a file with information related to the installation, such as environment variables and selected options. This is used for package removal and upgrade processes as well.
$VRS_HOME/lib contains operating system libraries that may need to be installed during the installation process.
$VRS_HOME/log contains log files for all ViewRunner server processes.
- Each process has a log file created each time it starts.
- The name of the file is <process_name>.log.<pid>.
$VRS_HOME/pipes contains the named pipes used for interprocess communications
between servers.

5.4 Directory Structure for ViewRunner Client Applications

Following is the directory structure created upon installation of the ViewRunner for HP OpenView client applications:

$VRC_HOME is the home directory for the client installation.
$VRC_HOME/bin contains the ViewRunner client binaries.
$VRC_HOME/conf contains the configuration files (which should be identical to the configuration in the server $VRS_HOME/conf files).
- vrconstants.conf contains the ViewRunner client configuration parameters.
- eventcodes.conf contains mappings between event codes and alarm descriptions.
- vrlrcodes.conf contains mappings between CLEI codes and access identifiers (AIDs).
$VRC_HOME/env contains environment-variable scripts. These may also be located in a local bin directory, such as /opt/bin, if the installer chose this option.
$VRC_HOME/etc contains bitmaps used in the ViewRunner client applications and a sample XDefaults file for the client applications.
$VRC_HOME/hpov contains files used to configure HP OpenView during installation. (This is not used after installation.)
$VRC_HOME/install contains a file with information related to the installation, such as environment variables and selected options. This is used for package removal and upgrade processes as well.
$VRC_HOME/lib contains operating system libraries that may need to be installed during the installation process.

Table of Contents

Installing ViewRunner on Distributed Machines