Managing NerveCenter
-
Controlling NerveCenter from the Command Line - NerveCenter UNIX Shell/DOS Prompt Commands - ovpa -
ovpa [-heart seconds] [-is] [-info] [-v{1|2|3|4|5}]
[-nocap|cache] [-no_ror] [-mi] [-pc|-pc
nchost|pc_noupdate]
Runs the NerveCenter OpenView Platform Adapter (OVPA).
OpenView (OV) must be running before you can run OVPA. To issue an ovpa command (with or without switches) by itself and without also using ovstart, you must first remove the OVPA local registration file (ovpa.lrf) from the list of services that are started by OV. For more information, refer to Integrating NerveCenter with a Network Management Platform.
OVPA sends a heartbeat to the NerveCenter Server at the frequency of the number of seconds entered. If a NerveCenter Server has not responded to OVPA after three heartbeat messages, the platform adapter will set the status of the NerveCenter platform icon to UnKnown and insert an event into the platform event stream. Heartbeat messaging resumes.
The default heartbeat is 300 seconds.-is
Synchronizes the status of a NerveCenter icon and its managed nodes.
Reports the version of the NerveCenter OVPA and exits.
Displays as much information as possible.
Displays timing and node count for resync operations exclusively. This switch displays the time in seconds when the resync starts and ends, the elapsed time for the resync and the total number of nodes that were involved in the resynchronization.
Checks for non-printable characters in the node names sent to NerveCenter Server for deletion. Only provides a display if non-printable characters are found. Characters with ASCII codes <32 and >126 are considered non-printable.
Displays information about inform and node status messages.
Displays information about nodes and their parents.
Determines whether ovpa keeps track of your platform's capability information, such as IsRouter.
-nocap prevents ovpa from keeping track of this data. This increases ovpa's speed and decreases its memory usage.
-cache caches the capability information and updates this data once a day.
If you do not use either switch, OVPA retrieves capability information on demand.
Turns off community resolution during resync to improve performance between OVPA and OV. no_ror does not affect community strings being reset in NerveCenter. The default is to have ovpa get the current community string for each node during every resync.
Loads only IP addresses from managed interfaces when constructing nodes to send to NerveCenter. (See additional information later in NOTES section.)
Handles parenting information:
-pc computes parenting information, sending it to NerveCenter on the next resync or map changes.
-pc nchost computes parenting information, writing it to nchost_PC.dat. OVPA then stops.
-pc_noupdate computes parenting information only during a resync. It does not compute parenting information about an individual node that is added or changed. To have full parenting information updated, you must force a resync using the NerveCenter Client.
The default is that no parenting information is included.
-pc switch, place the -pc switch after all other switches. If not, OVPA may interpret whatever follows as a filename.
If you want these settings to take effect every time OVPA is started, edit the file ovpa.lrf to include these switches. On Windows NT, the file is located in the OpenView/lrf directory. On UNIX, the file is located in the opt/OSInc/nc/OV/lrf directory. For example, to have OVPA compute parenting information only during a resync you would modify ovpa.lrf to read:
ovpa:/opt/OSInc/nc/OV/bin/ovpa:
OVs_YES_START:ovwdb:-pc_noupdate:OVs_WELL_BEHAVED:5:
The following behavior occurs when using the -mi switch: when nodes are unmanaged in OpenView, NerveCenter removes these nodes. When interfaces on multi-interfaced nodes are unmanaged in OpenView, NerveCenter removes only these unmanaged interfaces. NerveCenter retains any managed interfaces and their node. (If all interfaces for a node are unmanaged, then the node is removed from the NerveCenter node list.)
The following behavior occurs when the -mi switch is not used: when nodes are unmanaged in OpenView, these nodes are also unmanaged in NerveCenter. When interfaces on multi-interfaced nodes are unmanaged in OpenView, NerveCenter does nothing to these interfaces and their node; that is, NerveCenter takes no action regarding a node if an interface is unmanaged in OpenView. The Interface's IP is not removed from the node's IP list and NerveCenter continues to attempt to poll this interface.
| Previous: ncstop | Next: paserver |
| Please send comments or corrections to Information Development | This file was last updated on 14 November © 2002 |