cc/td/doc/product/dsl_prod/vrmgtsw/vr4ov/rel240
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Miscellaneous Setup

Miscellaneous Setup

6.1 Default Map Definition

The default map that HP OpenView automatically creates does not support ViewRunner. It is preferable to create a new map with ViewMap enabled and make it your default map. To define a "default" that supports ViewRunner, you need to do the following:

Step 1 Log on as with your normal user ID.

Step 2 Source the vrc.cshrc file using the following commands:

Step 3 cd /opt/CSCOvrovc/env

        source vrc.cshrc
cd ~

Step 4 Start HP OpenView.

        ovw &

Step 5 Log in to ViewRunner as vradmin, with the initial password cisco123.

Step 6 Select Maps->New... from the main menu.

Step 7 Enter Temp (or some other name of your choice) for the name of the map, then click OK.

Step 8 Select Maps->Open/List... from the main menu.

Step 9 Select the default map, then click Delete.

Step 10 Select Maps->New... from the main menu.

Step 11 For Compound Status, select Propagate Most Critical.

Step 12 Under Configurable Applications, select ViewMap and choose Configure For This Map.

Step 13 In the ViewMap Configuration dialog box, select True, and then click Verify, followed by OK.

Step 14 Click OK to close the Add Map dialog box and use the new default map.

Step 15 Select Maps->Open/List from the main menu.

Step 16 Select the Temp (new) map and click Delete.

Step 17 Select the default map and set it as the default for the user.

Step 18 Close the window.

Administrators should have read-write maps if they need to make changes to the Locations layouts. Other users should have read-only maps.

6.2 Enable External ViewRunner Clients

To enable external ViewRunner clients, HP OpenView needs to be installed as a distributed console only. HP OpenView Distributed Console software does not require a license to run.

The following system actions must take place:

To install an HP OpenView Distributed Console client, follow the procedures in Chapter 4 of the HP OpenView manual, A Guide to Scalability and Distribution.

6.3 Trivial File Transfer Protocol and Bootstrap Protocol Server Setup

The ViewRunner for HP OpenView server may also provide Trivial File Transfer Protocol (TFTP) and Bootstrap Protocol (BOOTP) services to Cisco 6100 Series systems as they boot. In order to do this, the workstation needs to be configured to support TFTP and BOOTP. In order to set up TFTP, the following actions must be completed:

Step 1 Verify that there is an entry for TFTP in /etc/intd.conf. It should be of the form:

    tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s/tftpboot

Step 2 As the root user, execute the following commands:

    mkdir /tftpboot
cd /tftpboot
ln -s . tftpboot

Step 3 Copy the Cisco 6100 Series images to the /tftpboot directory.

Complete the following steps to set up BOOTP:

Step 1 Verify that there is an entry for bootp in /etc/inetd.conf. It should be of the form:

    bootps dgram udp wait root /usr/sbin/bootpd bootpd

Step 2 Download the Hewlett-Packard JetDirect software from the World Wide Web at

    http://www.hp.com/cposupport/eschome.html

Install the packages, which (among other things) creates a copy of bootpd in /usr/sbin.

Step 3 Create a BOOTP table (/etc/bootptab) that contains the following information:

6.4 Cron Job Setup

It is possible to set up cron jobs to do periodic configuration synchronizations. The cron job allows you to do the synchronizations during nonpeak hours and to further minimize the potential impact on users.

The following example performs an intelligent configuration synchronization every night at 1:00 a.m. on a Cisco 6100 Series system named lr01:

0 1 * * * VRS_HOME=/opt/CSCOvrovs; export VRS_HOME; vrPerformConfigSync -c -n lr01

To synchronize all Cisco 6100 Series systems, substitute the key word all for lr01 in the
preceding line.

You can also run a cron job at nonpeak hours to purge log files. The following example purges the log files every Sunday at midnight.

0 0 * * 0 VRS_HOME=/opt/CSCOvrovs; export VRS_HOME; /opt/CSCOvrovs/bin/cleanlog.ksh

6.5 Installation Options

The following sections describe the installation options for the packages.

6.5.1 Database Package Option Description

During the installation of the ViewRunner database package, CSCOvrdb, you are presented with a menu of options for the install. You can select the number or letter to the left of each parameter to change that parameter. Most sites, however, can take the defaults. To increase performance, you are given the opportunity to spread the Oracle database across multiple disk drives and the ability to specify the size of each tablespace. The ViewRunner Server and Client packages recognize the parameters entered in the ViewRunner database package to provide for Oracle connectivity. If you are installing in a distributed environment, you must enter the same Oracle parameters in every package. Following is an example of the parameters you may change to customize the installation:

*****************************************************************
**************** DATABASE INSTALL PARAMETERS ********************
*****************************************************************
 
       ViewRunner DB Release: 2.4.0.10.1 Install Type: N
0)   Oracle Script directory: /opt/CSCOvrdb
1)    Oracle UNIX Owner/User: oracle
2)              Oracle Group: dba
3)               ORACLE_HOME: /u01/app/oracle/product/7.3.4
4)                ORACLE_SID: vrunner
5)             Listener Port: 1521
6)      TNS Name or DB Alias: vrunner
7)         Create RC Scripts: Y
8)           Database Exists: N
9)      Default DB Directory: /u01/oradata/vrunner
A)        System TS Dir/Size: /u01/oradata/vrunner 32M
B)        Config TS Dir/Size: /u01/oradata/vrunner 32M
C)         Alarm TS Dir/Size: /u01/oradata/vrunner 64M
D)      RollBack TS Dir/Size: /u01/oradata/vrunner 128M
E)          Temp TS Dir/Size: /u01/oradata/vrunner 32M
F)         Index TS Dir/Size: /u01/oradata/vrunner 32M
G)         Redo Log Dir/Size: /u01/oradata/vrunner 10M x2 logs
H)        Diskspace required: 330 MB
I)     Schema owner/password: vrunnerrw vrunnerrw
J)      Client user/password: vrunnerro vrunnerro
 
Z)    Install VR Database with the displayed parameters?
 
 
Enter the letter or number q=quit [default=Z]: g

Following are the descriptions of the database install parameters from the previous example:

This is the directory where the database package is installed. The scripts to start and stop Oracle are installed in this directory. The environment variable $VRD_HOME references this directory. Therefore, $VRD_HOME/bin should be in your path to start Oracle.
This is the UNIX ID that owns the Oracle software. The default name is "oracle." It is the ID that you used to install Oracle on your UNIX server.
This is the UNIX group that is used when you install the Oracle software on the server. The default is dba.
This is the environment variable defining the directory you used when installing Oracle. It is typically defined as the following:
/mount_point/app/oracle/product/oracle_version
The mount_point is the directory of the disk drive where you did the install of Oracle and oracle_version is the version of Oracle that you installed.
This is the Oracle System Identifier (SID) for the database instance. Basically, you think of the SID as the name of the Oracle database. You can name it whatever you want for a new installation. If the SID (database) exists, ViewRunner attempts to install the ViewRunner tables and tablespaces to the existing Oracle database.
The Oracle Server requires a TCP/IP port which allows remote clients to connect to the database server using SQL*Net. The default value of 1521 is typically used by most Oracle installations.
In a Distributed Database environment, the transparent network substrate (TNS) name, or Database Alias Name, is used by SQL*Net on the client to locate the instance of the host, port, and database to communicate with on the server. This name is located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter the same name in the ViewRunner Client and Server install or you are not able to connect to the database. You can name this whatever you want that is descriptive. A good name might be a combination of the host where the Oracle database is located and the SID. The default for ViewRunner
is vrunner.
An entry can be created in the /etc/rc2.d directory so that the ViewRunner Database server is started when the system is rebooted.
If the value is set to Y, scripts that start-up and shut down Oracle and ViewRunner are created and installed. The HP OpenView and ViewRunner start-up and shutdown scripts are located in the /etc/init.d/vr4hpov directory. The Oracle start-up and shutdown script is located in the /etc/init.d/vrdb directory. Symbolic links are then created in /etc/rc2.d/ to start up the servers and in the /etc/rc0.d/ directory to shutdown the servers.
This is set to Y if the Oracle SID is found. You can't modify this parameter. If the database exists, ViewRunner attempts to add the ViewRunner tables to the existing database.
This is the default directory to which you install all of the Oracle data files. If you distribute the database among other disks, the only thing remaining in this directory would be the control files.
This is the normal Oracle System Tablespace. It contains the Oracle catalog, system tables, and initial rollback segments. For most customers, 32 to 50 MB should be sufficient.
The size of the database is dependent on the number of Cisco 6100 Series systems that are managed and the length of time that the data is stored. The configuration database contains the configuration details for each Cisco 6100 Series system. The amount of configuration data for a fully configured Cisco 6100 Series system is approximately 0.5 M.
The alarm database contains information collected by View Alarm Formatter. Assuming a trap rate of one trap per minute per Cisco 6100 Series system, you need to allocate 75 KB per Cisco 6100 Series system per day of storage, or approximately 2 M per Cisco 6100 Series system per month of storage.
The rollback segments are used to temporarily store "undo" information. It is used to generate a read-consistent database, which is used during database recovery, and to roll back uncommitted transactions for users. The minimum size for the ViewRunner database is 128 MB.
The temporary tablespace is used for database sorting and for saving temporary results from
table joins.
The index tablespace is used to store all of the keys for the ViewRunner tables.
The database redo logs contain information required for database recovery. It is advisable to store the redo logs on a disk that is separate from the database data files because of the heavy write activity. You should create two redo log files of this size where the database alternates between the two. As one redo log becomes full, it switches to the other redo log. Oracle refers to this as two redo log groups with one member per group.
With Oracle, you can also Multiplex (or Mirror) your redo logs to separate physical disks; changes made to one member of the group are made to all members. If you wish to multiplex your redo logs you can specify the directory location of the second member of each group.
This is informational and cannot be directly changed. It adds up all of the space that the database takes up for the installation. The install package adds up the space needed for each mount point and warns you about any tablespace taking up more space than is available for the mount point.
The Oracle Schema user ID is the Oracle user ID that is the owner of all of the ViewRunner tables. This ID has read/write access to all tables and is used by the ViewRunner Server to update the database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install, or you cannot connect to the database.
The Oracle Client user ID is the Oracle user ID that the ViewRunner Client uses to read the database. This ID has read-only access in the ViewRunner database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install or you cannot connect to the database.
Accept all the parameters presented and install the database.

6.5.2 ViewRunner Server Installation Package Option Description

During the installation of the ViewRunner Server package, CSCOvrovs, you are presented with a menu of options for the install. You can select the number or letter to the left of the parameter to change that parameter. Most sites, however, can take the defaults. The Oracle parameters are taken from the ViewRunner Database package. If you are installing in a distributed environment you must enter the same Oracle parameters in every package. Following is an example of the parameters you may change to customize the installation:

*****************************************************************
**************** ViewRunner INSTALL PARAMETERS ******************
*****************************************************************
 
       ViewRunner DB Release: 2.4.0.10.1
1) Host Name Oracle Database: mamiles-u10
2)         Local Oracle Home: /u01/app/oracle/product/7.3.4
3)                ORACLE_SID: vrunner
4)             Listener Port: 1521
5)      TNS Name or DB Alias: vrunner
6)           Remote Database: N
        Database Install Dir: /opt/CSCOvrdb
7)     Schema owner/password: vrunnerrw vrunnerrw
8)      Client user/password: vrunnerro vrunnerro
 
      Base Install Directory: /opt/CSCOvrovs
9)    Create Local Directory: Y
9)           Local Directory: /opt/bin
A)           TFTP IP Address: 171.69.166.41
A)                 TFTP Path: /tftpboot/
B)      Process Monitor port: 3001
B)      Alarm Collector port: 3002
C)         Create RC Scripts: Y
 
 
Z)    Install ViewRunner with the displayed parameters?

Following are the descriptions of the database install parameters from the previous example:

This is the host where the ViewRunner Oracle database is running. If you install the ViewRunner Server on the same machine as the Oracle server, the database is automatically populated. The server is used to configure SQL*Net to connect to the database.
This is the environment variable defining the directory you used when installing Oracle. It is typically defined as the following:
/mount_point/app/oracle/product/oracle_version
The mount_point is the directory of the disk drive where you did the install of Oracle and oracle_version is the version of Oracle that you installed.
The Oracle Client (SQL*Net) is required to be installed on the local machine even if the database is remote.
This is the Oracle System Identifier (SID) for the database instance. Basically, you can think of this as the name of the Oracle database. You can name it whatever you want for a new install. If the SID (database) exists, ViewRunner attempts to install the ViewRunner tables and tablespaces to the existing Oracle database. This must be the same as what was entered on the ViewRunner Database install.
The Oracle Server requires a TCP/IP port which allows remote clients to connect to the database server using SQL*Net. The default value of 1521 is typically used by most Oracle installations. It must be the same as what was entered on the ViewRunner Database install.
In a Distributed Database environment, the transparent network substrate (TNS) name, or Database Alias Name, is used by SQL*Net on the client to locate the instance of the host, port, and database to communicate with on the server. This name is located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter the same name in the ViewRunner Client and Server install or you cannot connect to the database. You can name this whatever you want that is descriptive. A good name might be a combination of the host where the Oracle database is located and the SID. The default for ViewRunner is vrunner. This must be the same as what was entered on the ViewRunner Database install.
This is set automatically if you specify a different host name for where the Oracle database is installed. The Database Install Directory is also automatically populated if the ViewRunner database package is installed on the same machine as the ViewRunner Server. The database installation directory is added to the path in the environment variables of the ViewRunner Server.
The Oracle Schema user ID is the Oracle user ID that is the owner of all of the ViewRunner tables. This ID has read/write access to all tables and is used by the ViewRunner Server to update the database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install or you cannot connect to the database.
The Oracle Client user ID is the Oracle user ID that the ViewRunner Client uses to read the database. This ID has read-only access in the ViewRunner database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install or you cannot connect to the database.
If you want to copy the environment-variable scripts to a local bin directory you can specify "Y" and the directory name for where the scripts are to be copied.
This is the name of the TFTP server machine where the Cisco 6100 Series system software images are installed. The install program attempts to find the IP Address by looking up the name in the local host file. Please verify that the IP Address is correct. There should be only one address. You must also specify the TFTP path, including a trailing slash. For instructions on setting up TFTP, see the "Trivial File Transfer Protocol and Bootstrap Protocol Server Setup" section.
ViewRunner uses two services to service remote clients. Enter the TCP ports to be used for these services. There should be no other process using these ports.
An entry can be created in the /etc/rc2.d directory so that ViewRunner servers are started every time the system is rebooted.
If the value is set to Y, scripts that start-up and shut down Oracle and ViewRunner are created and installed. The HP OpenView and ViewRunner start-up and shutdown scripts are located in the /etc/init.d/vr4hpov directory. The Oracle start-up and shutdown script is located in the /etc/init.d/vrdb directory. Symbolic links are then created in /etc/rc2.d/ to start up the system and in the /etc/rc0.d/ directory to shutdown the system.

Accept all the parameters presented and install the ViewRunner Server.

6.5.3 ViewRunner Client Install Package Option Description

During the installation of the ViewRunner Client package, CSCOvrovc, you are presented with a menu of options for the install. You can select the number or letter to the left of each parameter to change that parameter. Most sites, however, can take the defaults. The Oracle parameters are taken from the ViewRunner Database package. If you are installing in a distributed environment you must enter the same Oracle parameters in every package.

The following script is an example of the parameters you may change to customize the installation:

*****************************************************************
**************** ViewRunner INSTALL PARAMETERS ******************
*****************************************************************
 
       ViewRunner DB Release: 2.4.0.10.1
1) Host Name Oracle Database: mamiles-u10
2)         Local Oracle Home: /u01/app/oracle/product/7.3.4
3)                ORACLE_SID: vrunner
4)             Listener Port: 1521
5)      TNS Name or DB Alias: vrunner
6)           Remote Database: N Install Dir: /opt/CSCOvrdb
7)     Schema owner/password: vrunnerrw vrunnerrw
8)      Client user/password: vrunnerro vrunnerro
 
       VR Client Install Dir: /opt/CSCOvrovc
9)          Create Local Dir: Y
9)                 Local Dir: /opt/bin
A)     VR Server Install Dir: /opt/CSCOvrovs
A)       VR Server Host Name: mamiles-u10
B)      Process Monitor port: 3001
B)      Alarm Collector port: 3002
 
 
Z)    Install ViewRunner with the displayed parameters?
 
 
Enter the letter or number q=quit[default=Z]:

Following are the descriptions of the database install parameters from the previous example:

This is the host where the ViewRunner Oracle database is running. If you install the ViewRunner Server on the same machine as the Oracle server, the database is automatically populated. The server is used to configure SQL*Net to connect to the database.
This is the environment variable defining the directory that you used when installing Oracle. It is typically defined as the following:
/mount_point/app/oracle/product/oracle_version
The mount_point is the directory of the disk drive where you did the install of Oracle and oracle_version is the version of Oracle that you installed.
The Oracle Client (SQL*Net) is required to be installed on the local machine even if the database is remote.
This is the Oracle System Identifier (SID) for the database instance. Basically, you can think of this as the name of the Oracle database. You can name it whatever you want for a new install. If the SID (database) exists, ViewRunner attempts to install the ViewRunner tables and tablespaces to the existing Oracle database. This must be the same as what was entered on the ViewRunner Database install.
The Oracle Server requires a TCP/IP port which allows remote clients to connect to the database server using SQL*Net. The default value of 1521 is typically used by most Oracle installations. It must be the same as what was entered on the ViewRunner Database install.
In a Distributed Database environment, the transparent network substrate (TNS) name, or Database Alias Name, is used by SQL*Net on the client to locate the instance of the host, port, and database to communicate with on the server. This name is located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter the same name in the ViewRunner Client and Server install or you cannot connect to the database. You can name this whatever you want that is descriptive. A good name might be a combination of the host where the Oracle database is located and the SID. The default for ViewRunner is vrunner. This must be the same as what was entered on the ViewRunner Database install.
This is automatically set if you specify a different host name for where the Oracle database is installed. The Database Install Directory is also automatically populated if the ViewRunner database package is installed on the same machine as the ViewRunner Server. The database installation directory is added to the path in the environment variables of the ViewRunner Server.
The Oracle Schema user ID is the Oracle user ID that is the owner of all the ViewRunner tables. This ID has read/write access to all tables and is used by the ViewRunner Server to update the database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install or you cannot connect to the database.
The Oracle Client user ID is the Oracle user ID that the ViewRunner Client uses to read the database. This ID has read-only access in the ViewRunner database. These IDs are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same IDs in the ViewRunner Client and Server install or you cannot connect to the database.
This is the Directory where the ViewRunner package was installed along with the host name of the server where it was installed. In a remote environment, it is necessary to mount the server install directory on the client machine.
ViewRunner uses two services to service remote clients. Enter the TCP ports to be used for these services. There should be no other process using these ports.
Accept all the parameters presented and install the ViewRunner Client.

hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Oct 8 13:49:52 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.