Table of Contents
Miscellaneous Setup
The default map that HP OpenView automatically creates does not support ViewRunner. It is preferable to create a new map with ViewMap enabled and then make it your default map. To define a "default" that will support ViewRunner, you will need to do the following:
Step 1 Logon as with your normal userid.
Step 2 Source the vrc.cshrc file
cd /opt/CSCOvrovc/env
source vrc.cshrc
cd ~
Step 3 Start HP OpenView
ovw &
Step 4 Log in to ViewRunner as vradmin, with the initial password cisco123.
Step 5 Select Maps->New... from the main menu.
Step 6 Enter Temp (or some other name of your choice) for the name of the map, then press OK.
Step 7 Select Maps->Open/List... from the main menu.
Step 8 Select the default map, then press Delete.
Step 9 Select Maps->New... from the main menu.
Step 10 For Compound Status, select Propagate Most Critical.
Step 11 Under Configurable Applications, select View Map and press Configure For This Map....
Step 12 In the View map Configuration dialog, select True and press Verify, followed by OK.
Step 13 Press OK to close the Add Map dialog and use the new "default" map.
Step 14 Select Maps->Open/List... from the main menu.
Step 15 Select the Temp (new) map and press Delete.
Step 16 Select the "default" map and set it as the default for the user.
Step 17 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.
To enable external ViewRunner clients, HP OpenView need only be installed as a distributed console. HP OpenView Distributed Console software does not require a license to run.
The following system actions must take place:
- The ViewRunner server must export its home directory $VRS_HOME, and the ViewRunner client must mount this directory using NFS.
- The ViewRunner client workstation must be authorized to connect to OpenView windows (ovw).
- The ViewRunner client workstation must be authorized to connect to the OpenView windows database (ovwdb).
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.
The ViewRunner for HP OpenView server may also provide TFTP (Trivial File Transfer Protocol) and BOOTP (Bootstrap Protocol) services to Cisco 6100s as they boot. In order to do this, the workstation will need 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 images to the /tftpboot directory.
In order to set up BOOTP, the following actions must be completed:
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/networking/software/sol_pkgadd.d0109.html. Install the packages, which will (among other things) create a copy of bootpd in /usr/sbin.
Step 3 Create a BOOTP table (/etc/bootptab) that contains the following information:
- The hardware address of the Cisco 6100
- The IP address to assign to the Cisco 6100
- The subnet mask to use for the Cisco 6100
- The IP address of the gateway
- The name of the image to download onto the Cisco 6100
- Example:
lr01:\
:ht=ether:ha=00E0D0001941:\
:ip=192.168.7.41:\
:sm=255.255.255.0:\
:gw=192.168.7.1:
:hd=/tftpboot:\
:bf=scRel1.9.ima:\
:vm=rfc1048:
It is possible to set up cron jobs with which to do periodic configuration synchronizations. The cron job will allow you to do the synchronizations during non-peak hours and further minimize the potential impact on users.
The following example will perform an intelligent configuration synchronization on a Cisco 6100 named lr01 every night at 1:00 am:
0 1 * * * VRS_HOME=/opt/CSCOvrovs; export VRS_HOME; vrPerformConfigSync -c -n lr01
To synchronize all Cisco 6100s, substitute the key word all for lr01 in the above line.
You can also run a cron job at off-peak hours to purge log files. The following example will purge the log files every Sunday at midnight.
0 0 * * 0 VRS_HOME=/opt/CSCOvrovs; export VRS_HOME; /opt/CSCOvrovs/bin/cleanlog.ksh
The following sections present a detailed description of the installation options for the packages.
During the install of the ViewRunner database package CSCOvrdb you will be presented with a menu of options for the install. You can select the option at the left and 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 will 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.
*****************************************************************
**************** DATABASE INSTALL PARAMETERS ********************
*****************************************************************
ViewRunner DB Release: 2.3.5.8.1.1.7 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
- This is the directory where the database package is installed. The scripts to start and stop Oracle will be installed in this directory. The environment variable $VRD_HOME will reference this directory. $VRD_HOME/bin should be in your path to start Oracle.
- This is the UNIX id that will own the Oracle software. The default name is "oracle". It is the id you used to install Oracle on your UNIX server.
- This is the UNIX group used when 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 the oracle_version is the version of Oracle you installed.
- This is the Oracle System Identifier (SID) for the database instance. Basically you think of this as the name of the Oracle database. You can name it what you want for a new install. It the SID (database) exists then ViewRunner will attempt to install the ViewRunner tables and tablespaces to the existing Oracle database.
- The Oracle Server requires a TCP/IP port to allow remote clients to connect 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 host, port, and database instance 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 will not be able to connect to the database. You can name this what you want that is descriptive. Maybe a good name would be a combination of the host where the Oracle database is located along with the SID. The default for ViewRunner is vrunner.
- An entry can be created in the /etc/rc2.d directory so that ViewRunner Database server is started when system is rebooted.
- This will be set to Y if the Oracle SID is found. You can't modify this parameter. If the database exists, ViewRunner will attempt to add the ViewRunner tables to the existing database.
- This is the default directory to install all the Oracle data files. If you end up distributing the database among other disks then the only thing remaining in this directory would be the control files.
This is the normal Oracle System Tablespace. It contains the Oracle catalog and system tables and initial rollback segments. 32 to 50 Megabytes should be sufficient for most customers.
- The size of the database is dependent on the number of 6100s that will be managed and the length of time that data will be stored. The configuration database contains the configuration details for each 6100. The amount of configuration data for a fully configured 6100 is approximately 0.5M.
- The alarm database contains information collected by View Alarm Formatter. Assuming a trap rate of one trap per minute per 6100, you will need to allocate 75K bytes per 6100 per day of storage, or approximately 2M per 6100 per month of storage.
- The rollback segments are used to temporarily store "undo" information. It is used to generate a read-consistent database, used during database recovery, and to rollback uncommitted transactions for users. The minimum size for the ViewRunner database is 128 Megabytes.
- The Temporary tablespace is used for database sorting and savings temporary results from table joins.
- The index tablespace is used to store all 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 different disk separate from the database data files because of the heavy write activity. We will be creating 2 redo log files of this size where the database will alternate between the two. As one redo log becomes full, it will switch to the other redo log. Oracle refers to this as 2 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 can't be directly changed. It will add up all the space the database will be taking up for the install. The install package will add up the space needed for each mount point and will warn you about any tablespace taking up more space than available for the mount point.
- The Oracle Schema user id is the Oracle user id that owner of all the ViewRunner tables. This id has read/write to all tables and is used by the ViewRunner Server to update the database. These id's 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 will not be able to connect to the database.
- The Oracle Client userid is the Oracle userid that the ViewRunner Client uses to read the database. This id has read-only access in the ViewRunner database. These id's are located in the vrconstants.conf file in $VRS_HOME/conf and $VRC_HOME/conf. You must make sure that you enter these same id's in the ViewRunner Client and Server install or you will not be able to connect to the database.
- Install VR Database with the displayed parameters
- Accept all the parameters presented and install the database.
During the install of the ViewRunner Server package CSCOvrovs you will be presented with a menu of options for the install. You can select the option at the left and 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.
*****************************************************************
**************** ViewRunner INSTALL PARAMETERS ******************
*****************************************************************
ViewRunner DB Release: 2.3.5.8.1.1.7
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?
- Host name of Oracle Database
- This is the host where the ViewRunner Oracle database is running. If you install ViewRunner Server on the same machine at the Oracle server this will automatically populated. This 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 the oracle_version is the version of Oracle 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 think of this as the name of the Oracle database. You can name it what you want for a new install. It the SID (database) exists then ViewRunner will attempt to install the ViewRunner tables and tablespaces to the existing Oracle database. This must be the same as entered on the ViewRunner Database install.
- The Oracle Server requires a TCP/IP port to allow remote clients to connect the Database server using SQL*Net. The default value of 1521 is typically used by most Oracle installations. It must be the same as 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 host, port, and database instance 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 will not be able to connect to the database. You can name this what you want that is descriptive. Maybe a good name would be a combination of the host where the Oracle database is located along with the SID. The default for ViewRunner is "vrunner". This must be the same as entered on the ViewRunner Database Install.
- This automatic set if you specify a different host name of where the Oracle database is installed. The Database Install Directory is also 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 owner of all the ViewRunner tables. This id has read/write to all tables and is used by the ViewRunner Server to update the database. These id's 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 will not be able to connect to the database.
- The Oracle Client userid is the Oracle userid that the ViewRunner Client uses to read the database. This id has read-only access in the ViewRunner database. These id's 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 will not be able to 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 of where the scripts will be copied.
- The name of the TFTP server machine where the 6100 system software images are installed. The install program will attempt 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 only be one address. You must also specify the TFTP Path, including a trailing slash. For instructions on setting up TFTP see Miscellaneous Setup options.
- Process Monitor / Alarm Collector port
- 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 when system is rebooted.
- Install ViewRunner with the displayed parameters
Accept all the parameters presented and install the ViewRunner Server.
During the install of the ViewRunner Client package CSCOvrovc you will be presented with a menu of options for the install. You can select the option at the left and 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.
*****************************************************************
**************** ViewRunner INSTALL PARAMETERS ******************
*****************************************************************
ViewRunner DB Release: 2.3.5.8.1.1.7
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]:
- Host name of Oracle Database
- This is the host where the ViewRunner Oracle database is running. If you install ViewRunner Server on the same machine at the Oracle server this will automatically populated. This 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 the oracle_version is the version of Oracle 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 think of this as the name of the Oracle database. You can name it what you want for a new install. It the SID (database) exists then ViewRunner will attempt to install the ViewRunner tables and tablespaces to the existing Oracle database. This must be the same as entered on the ViewRunner Database install.
- The Oracle Server requires a TCP/IP port to allow remote clients to connect the Database server using SQL*Net. The default value of 1521 is typically used by most Oracle installations. It must be the same as 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 host, port, and database instance 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 will not be able to connect to the database. You can name this what you want that is descriptive. Maybe a good name would be a combination of the host where the Oracle database is located along with the SID. The default for ViewRunner is vrunner. This must be the same as entered on the ViewRunner Database Install.
- This automatic set if you specify a different host name of where the Oracle database is installed. The Database Install Directory is also 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 owner of all the ViewRunner tables. This id has read/write to all tables and is used by the ViewRunner Server to update the database. These id's 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 will not be able to connect to the database.
- The Oracle Client userid is the Oracle userid that the ViewRunner Client uses to read the database. This id has read-only access in the ViewRunner database. These id's 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 will not be able to 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 of where the scripts will be copied.
- VR Server Install Directory / VR Server Host name
- 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.
- Process Monitor / Alarm Collector port
- 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.
- Install ViewRunner with the displayed parameters
- Accept all the parameters presented and install the ViewRunner Client.
Posted: Fri Oct 8 12:37:17 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
