Installing ViewRunner on One Machine

Local Installation Overview and Guidelines

You might choose to install ViewRunner for HP OpenView on one local machine for the following reasons:

One machine is used as a network server.
Local installation is adequate for your needs.
Hardware/software compatibility varies according to the network.
Security considerations prevent a wider distribution.

Directory Structure for ViewRunner Server Applications

Following is the directory structure that is created upon installation of 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 and subscriber provisioning 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 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 inter-process 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 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 ViewRunner for HP OpenView Applications Locally

Following are the steps for installing ViewRunner for HP OpenView on one local machine:

Step 1 Verify that you are running the correct versions of Oracle, HP OpenView, and the correct patches for HP OpenView.

Step 2 Backup the Oracle database. (This is only required if you want to remove the new release and reinstall the previous release.)

Step 3 Verify that the Kernel parameters are defined in /etc/system and that the system has been rebooted. (See the "Shared Memory and Semaphores" section for a list of these parameters and their settings.)

Step 4 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 5 Install HP OpenView Network Node Manager (NNM) according to the instructions in the HP OpenView manuals. See "Installing ViewRunner on One Machine," for a sample of the HP OpenView NNM installation.

Step 6 Install the proper patch for HP OpenView.(See the "ViewRunner for HP OpenView Patches" section for patch information.)

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

Step 8 Install the ViewRunner server package (CSCOvrovs).

Step 9 Install the ViewRunner client package (CSCOvrovc).

Procedure 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 "Removing and Upgrading ViewRunner for HP OpenView Software." You must be the root user to execute these commands.

Note Refer to "Removing and Upgrading ViewRunner for HP OpenView Software," for additional removal guidelines.

Step 1 Change to the directory where the CD is mounted:

cd /cdrom/cdrom0

Step 2 Issue the pkgadd command to install the packages:

pkgadd -d .

Step 3 Install the ViewRunner database package.

Step 4 Install the ViewRunner server package.

Step 5 Install the ViewRunner client package.

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 details.

Step 6 Start the ViewRunner application.

ovw &

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.

Table of Contents