Table of Contents
Installing ViewRunner on One Machine
The following are the basic steps for installing ViewRunner for HP OpenView on one local machine.
Step 1 Verify that all system and software requirements have been met.
Step 2 Verify that the Kernel parameters are defined in /etc/system and that the system has been rebooted. (See "Shared Memory and Semaphores" section for a list of these parameters and their settings.)
Step 3 Install the Oracle database software (RDBMS, SQL *Net, TCP/IP Protocol adapter, Server Manager, and SQL *Plus).
Step 4 Install HP OpenView Network Node Manager (NNM).
Step 5 Install the proper patch for HP OpenView.
Step 6 Install the ViewRunner database package (CSCOvrdb).
Step 7 Install the ViewRunner server package (CSCOvrovs).
Step 8 Install the ViewRunner client package (CSCOvrovc).
Use following procedures to install ViewRunner as a new installation. 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 the details on running upgrade.ksh to convert the old OpenView maps.
Step 2 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. (See the "Installation Options" section for the installation options.)
Step 5 Install the ViewRunner server package.
Step 6 Install the ViewRunner client package.
Note Each of the above packages presents a menu of options you can change before installing the package. You can take the defaults on most of the options. See "Installation Options" section for more information.
Step 7 If you have old ViewRunner maps that need to be converted then you need to 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
See "Upgrading ViewRunner Software" for details on running upgrade.ksh.
Step 8 Start the ViewRunner application.
ovw &
Step 9 Login 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.
The following is the directory structure created upon installation of ViewRunner for HP OpenView server applications.
- $VRS_HOME - home directory for the Server installation
- $VRS_HOME/CMF - contains the feature capability matrix (FCM) file
- $VRS_ HOME/NSS - contains configuration save files
- Each Cisco 6100 will have a subdirectory for its save files. The name of the directory is the Cisco 6100's IP address.
- You can control the number of save files stored through 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 - 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. (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 upgrades.
- $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 will have 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.
The following is the directory structure created upon installation of ViewRunner for HP OpenView client applications.
- $VRC_HOME - home directory for the client installation
- $VRC_HOME/bin - contains the ViewRunner client binaries
- $VRC_HOME/conf - contains the configuration files (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 - 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. (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







Posted: Fri Apr 23 13:58:52 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.