|
|
ViewRunner for HP OpenView provides start-up utilities for the server and client applications that must be run by the root user.
 |
Note During installation, the ViewRunner servers and Oracle database can be configured to start-up and shut down automatically. See the "Directory Structure for ViewRunner Server Applications" section for more information. |
To provide easy access to the environment-variable setup utilities, you must copy the utilities to the local bin directory.
Employ the following steps to start ViewRunner server applications:
# . /opt/CSCOvrovs/env/vrs.kshrc
Step 2 Verify that the local bin directory is included in every user's path.
Step 3 Copy the ViewRunner server and client utilities to the local bin directory.
Step 4 Start the ViewRunner server applications. You must start the ViewRunner server applications using nohup if you plan to exit this shell and do not want the ViewRunner server applications to exit as well.
# nohup vrStart &
The servers should start-up. To check the servers that are currently running, use the ViewRunner utility check_servers, which is described in the "Guidelines for the ViewRunner Application Utilities" section.
|
Note Instructions are provided assuming that the user is root and is using ksh. |
To start the ViewRunner client applications, follow these steps:
$ . /opt/bin/vrc.kshrc
$ ovw &
ViewRunner starts the client applications through the GUI menu options.
Step 2 Create a new map or open an existing map that supports ViewMap. See "Defining the Default Map" section for the map creation procedure.
The initial map that is loaded is the HP OpenView default map. This map does not have ViewMap (one of the ViewRunner client applications) enabled.
See the ViewRunner for HP OpenView User Guide for more information on the operation of the ViewRunner client applications.
|
Note These instructions assume that the user is root and is using ksh. |
Execute the following commands to view the NetMon log file when employing a C shell.
source /opt/bin/vrs.cshrc cd $VRS_HOME/log check_servers #start-up show process (pid) id of running NetMon(s) vi vrNetMon.log.<pid> #where <pid> is value returned from previous command
Use the following commands to view the NetMon log file when using a Korn shell.
. /opt/bin/vrs.kshrc cd $VRS_HOME/log check_servers #start-up show process (pid) id of running NetMon(s) vi vrNetMon.log.<pid> #where <pid> is value returned from previous command
Only the root user can execute the first nine of the ViewRunner application utilities. All ViewRunner users can execute the last three utilities. The following twelve utilities are included with ViewRunner applications:
The root user can use the vrStart utility to start the primary ViewRunner server application, vrProcessMon, and any applications on which it depends (HP OpenView and Oracle7). If vrStart detects a failure of vrProcessMon, it restarts vrProcessMon unless ViewRunner is stopped by one of the following processes:
vrStart [-h] [-t <traceLevel>]
The parameter traceLevel is an optional parameter that sets the trace level as follows:
-h | Displays the usage of this command | |
-t <traceLevel> | 1 | - Trace error |
| 2 | - Trace events |
| 3 | - Trace functions |
| 4 | - Trace path flow |
The default trace level is 1, and should be used in most cases. To start ViewRunner at trace level 3, enter the following command:
vrStart -t 3
See the "vrTrace Utility" section for more information on trace levels.
The vrStop utility interacts with vrProcessMon to shut down ViewRunner server applications.
vrStop [-h][-p pipe] [-r <reason>]
-h | Displays the usage for this command | |
-p pipe | The communication pipe for the server applications for which the shutdown message is to be sent. If this parameter is not specified, all server applications are shut down. Otherwise, indicate a specific server application name. | |
-r reason | 1 | - Server shutdown |
| 2 | - Operator shutdown |
| 3 | - OpenView shutdown |
| 4 | - Exception shutdown |
The vrTrace utility interacts with vrProcessMon to set the trace levels of the ViewRunner server applications. The vrTrace utility can be used to change the log file size as well as the log truncation size. The default log size is 81,920 K, and the default log truncation size is 51,200 K.
The root user can change the trace level of a running server from the command line. If a regular user tries to change the trace level, the operation start-up fails silently.
To determine the current trace level, run the utility check_servers, which informs you of the initial trace level. Also, you can search the log files for any changes to the trace level by using the following command:
grep "Tracing level set to" $VRS_HOME/log/*.
vrTrace [-h] [-m truncSize] [-M maxSize] [-t traceLevel] -p {processName | all}
-h | Displays the usage for this command | |
-m truncSize | The size to which the trace file is truncated if it reaches maximum size | |
-M maxSize | The size beyond which the trace file is truncated | |
-t traceLevel | 1 | - Trace error |
| 2 | - Trace events |
| 3 | - Trace functions |
| 4 | - Trace path flow |
-p processName | all | The valid process names are vrProcessMon, vrNetMon, vrAlarmFormatter, and vrDataCollect. | |
You should use the default trace level of 1 in most cases.
Trace messages can have one of four possible severities:
The vrPerformConfigSync utility allows you to manually control synchronization runs. You can employ this utility to perform intelligent configuration synchronizations (the default) or to force full configuration synchronizations.
Multiple Cisco 6100 Series systems can be synchronized in parallel, subject to the limitations set in the MAX_GLOBAL_CONFIGURATION_SYNCS and MAX_CONFIGURATION_SYNCS_PER_NETMON parameters in the ViewRunner configuration file. Only the root user can run The vrPerformConfigSync utility.
|
Note This utility should be run regularly if you use more than one SNMP system to provision Cisco 6100 Series systems. |
The ViewRunner installation process automatically schedules a full configuration synchronization every day at midnight using a cron job.
vrPerformConfigSync -h vrPerformConfigSync -s [-p] -n all | address[address ...] vrPerformConfigSync -c [-f|-i] [-p] -n all | address[address ...]
-h | Displays the usage for this command | |
-c | Perform a configuration synchronization | |
-s1 | Save configuration | |
-i | Perform an intelligent configuration synchronization | |
-f | Force a full configuration synchronization | |
-p | Perform configuration synchronizations in parallel | |
-n | Select all Cisco 6100 Series systems or select individual Cisco 6100 Series systems by IP address for configuration synchronization | |
To perform an intelligent configuration synchronization on two nodes, execute the following command:
vrPerformConfigSync -i -n 172.24.133.20 172.24.133.40
To force a full configuration synchronization on all the nodes, execute the following command:
vrPerformConfigSync -f -n all
The vrPerformAlarmSync utility reconciles alarm assertions and alarm clears between the Cisco 6100 Series system current alarm tables and the ViewRunner alarm database. The alarm assertions and clears discovered by this utility are annotated in the Event Browser with, "Discovered by ViewRunner." Only the root user can run the vrPerformAlarmSync utility.
|
Note You should run this utility regularly if Cisco 6100 Series systems are not provisioned to send traps to the ViewRunner management station. |
vrPerformAlarmSync [-h] [-p] -n all | address[address...]
-h | Displays the usage for this command | |
-p | Perform alarm synchronization in parallel | |
-n | Select all Cisco 6100 Series systems or select individual Cisco 6100 Series systems by IP address for configuration synchronization | |
You can use the start_ora utility to start the vrunner Oracle database. This command should not be executed while any of the ViewRunner server applications are running. You need to run this utility after boot up of the workstation to ensure that the Oracle database is on line. The vrStart utility starts the database if it is not already running. Ordinarily, this utility is not invoked manually. Only the root user can execute the start_ora utility.
The start_listener utility starts the Oracle listener. Typically, start_ora starts this utility. It is not invoked manually. Only the root user can execute the start_listener utility.
The stop_ora utility stops the vrunner Oracle database. Do not execute this command while any of the ViewRunner server applications are running. However, you should execute this command before rebooting the server workstation. Only the root user can execute the stop_ora utility.
|
Note After installing the servers, you must create a link to the stop_ora utility in /etc/rc0.d and /etc/rc1.d. Doing so shuts down the database when the workstation is being shut down or when the run level is changed to single-user mode (for example, ln-s $VRS_HOME/bin/start_ora /etc/rc0.d/K00oracle). |
The check_ora utility checks the status of the vrunner Oracle database. Any user at anytime can run this utility. The check_ora utility has no parameters.
To check the servers that are currently running, use the ViewRunner utility, check_servers. You can find this in $VRS_HOME/bin or the local bin directory. The current version of check_servers is a simple utility that looks in the process table for the various process names associated with the servers. The following servers should be running:
To check the client applications that are currently running, use the ViewRunner utility, check_clients. This utility is located in $VRS_HOME/bin, $VRC_HOME/bin, or the local bin directory. The current version of check_clients is a simple utility that looks in the process table for the various process names associated with the client. The clients that could be running are
|
Note This utility only reports on clients that are running on the local machine. |
To check the OpenView sessions that are currently running, use the ViewRunner utility, check_ovw, which is located in $VRS_HOME/bin, $VRC_HOME/bin, or the local bin directory. The current version of check_ovw is a simple utility that looks in the process table for "ovw" and filters out the other OpenView processes.
|
Note This utility only reports on clients that are running on the local machine. |
To check the client applications that are currently running, you can use the ViewRunner utility, check_clients, which is located in $VRS_HOME/bin, $VRC_HOME/bin, or the local bin directory. The current version of check_clients is a simple utility that looks in the process table for the various process names associated with the client. The clients that could be running are
|
Note This utility only reports on clients that are running on the local machine. |
Posted: Tue Feb 8 14:44:21 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.