IBM Enterprise Console manual LRF File, Starting and Stopping the Adapter, Error File

Each line of this file has the following form:

"name" "object identifier"

For example

"sysUpTime" "1.3.6.1.2.1.1.3" "ifIndex" "1.3.6.1.2.1.2.2.1.1" "whyReload" "1.3.6.1.4.1.9.2.1.2"

Note: Object identifiers must appear in increasing order.

You can use the names that are mapped to object identifiers in the CDS file.

Error File

The error file enables you to configure debugging and tracing options. This file is described in detail in “Error File” on page 19.

LRF File

The .lrf file registers the application when the NNM application starts up. The .lrf file is created and registered automatically when the adapter is installed. For details on the syntax of the file, see the OpenView NNM documentation.

If you need to make changes to the tecad_hpov.lrf file, follow these steps:

1.Stop the adapter.

2.Change the .lrf file as needed and save it.

3.Register the change with NNM by using $OV_BIN/ovaddobj $OV_LRF/tecad_hpov.lrf.

4.Restart the adapter.

If the tecad_hpov.lrf file has errors, the adapter might not start successfully.

Starting and Stopping the Adapter

If you have configured the host start-up file correctly, the adapter always starts when the OpenView operating system starts up. You can also start an adapter manually. When the adapter starts up, it gets new bindings, reads its adapter files, and restarts the daemon.

Use the following commands to start and stop the adapter. You can access the OpenView NNM environment variables by sourcing the NNM environment using the ov.envvars.sh file in the /bin directory in the OpenView NNM installation directory.

. /opt/OV/bin/ov.evvars.sh	# source the unix/bash environment
/opt/OV/bin/ov.envvars.bat	# source the MS-DOS environment
$OV_BIN/ovstop tecad_hpov	# stop the OpenView adapter
$OV_BIN/ovstart tecad_hpov	# start the OpenView adapter

Chapter 5. OpenView Adapter 73