Table of Contents

Distributed Installation Overview
Guidelines for a Distributed Installation

Directory Structure for ViewRunner Server Applications
Directory Structure for ViewRunner Client Applications

Installing on Distributed Machines

Procedure for Installing on the ViewRunner Database Machine
Procedure for Installing on the ViewRunner Server Machine
Procedure for Installing on the ViewRunner Client Machine
Procedure for a New Installation on Distributed Machines

Installing ViewRunner on Distributed Machines

Distributed Installation Overview

Installing ViewRunner for HP OpenView in a distributed environment involves three separate installs on three separate machines. A distributed installation allows you limited system capacities, security considerations, and internetwork flexibility.

Guidelines for a Distributed Installation

Note the following guidelines before attempting to install ViewRunner for HP OpenView on distributed machines.

Directory Structure for ViewRunner Server Applications

Following is the directory structure that is 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 that are 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 might also be located in a local bin directory, such as /opt/bin, if the installer chose this option.

• $VRS_HOME/hpov contains files that are used to configure HP OpenView during installation. (This is not used after installation.)

• $VRS_HOME/install contains a file with information that is 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 might 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 that is created each time it starts.

  • The name of the file is <process_name>.log.<pid>.

• $VRS_HOME/pipes contains the named pipes that are used for interprocess communications between servers.

Directory Structure for ViewRunner Client Applications

Following is the directory structure that is 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 might also be located in a local bin directory, such as /opt/bin, if the installer chose this option.

• $VRC_HOME/etc contains bitmaps that are used in the ViewRunner client applications and a sample XDefaults file for the client applications.

• $VRC_HOME/hpov contains files that are used to configure HP OpenView during installation. (This is not used after installation.)

• $VRC_HOME/install contains a file with information that is 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 might need to be installed during the installation process.

Installing on Distributed Machines

A distributed installation of ViewRunner for HP OpenView requires three different machines. These are

• Database

• Server

• Client

Procedure for Installing on the ViewRunner Database Machine

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

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 "Installing the Oracle Database," for a sample of the Oracle installation.

Step 3 Install the ViewRunner database package (CSCOvrdb) according to the instructions in this guide. See "Installing the Oracle Database," for a sample transcript of the installation.

Procedure for Installing on the ViewRunner Server Machine

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

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 "Installing the Oracle Database," 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 Network Node Manager 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 that you used in the ViewRunner database package.

Procedure for Installing on the ViewRunner Client Machine

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

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 "Installing the Oracle Database," for a sample of the Oracle installation.

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

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 that you used in the ViewRunner database package.

Procedure for a New Installation on Distributed Machines

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 "Configuring ViewRunner Applications." You must be the root user to execute these commands.

cd /cdrom/cdrom0
 

Step 2 Issue the pkgadd command to install the packages.

pkgadd -d .
 

Step 3 Install the ViewRunner database package on the database machine.

Step 4 Install the ViewRunner server software on the server machine.

Step 5 Install the ViewRunner client software on the client machine.

Note Each of the preceding packages presents a menu of options that you can change before installing the package. You can take the defaults on most of the options. See the "Installation Options" section for more information.

Step 6 Start the ViewRunner application.

ovw &
 

See "Configuring ViewRunner Applications," for details on running upgrade.ksh.

Step 7 Log in to ViewRunner using vradmin as the user ID and cisco123 as the password.

Note You can change the default user ID and password after logging in.

Posted: Tue Feb 8 14:40:36 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.