Integrating NerveCenter with a Network
Management Platform
-
Integrating NerveCenter with HP OpenView Network Node Manager - OpenView Integration Reference -
The following section includes information you may need to reference occasionally when integrating NerveCenter and HP OpenView Network Node Manager.
You can control certain aspects of the NerveCenter OpenView Platform Adapter (OVPA) from the command line. The proper syntax is:
Ovpa [ -logLevel Error | Warning | Debug | Trace ]
[ -traceOutputFile FileName ] [ -traceOutputStdout ]
[ -traceResync ] [ -traceInform ] [ -traceLoadDb ]
[ -traceParentComp ] [ -traceMapUpdates ] [ -traceConnects ]
[ -traceAll ] [ -pc ] [ -writeParentsToFile NcHostName ]
[ -heartbeat seconds ] [ -ignoreUnmanagedIntf ]
[ -initNcStatusInOV ] [ -ignoreCapability ]
[ -noResolveCommunityOnResync ] [ -defGlobalCommunity filename ]
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 How to Configure OpenView to Integrate with NerveCenter. All of these command line switches are optional.
-logLevel Error | Warning | Debug | Trace
Set logging level, default value is Warning.
-traceOutputFile FileName
Set the output of logging messages to be a file with FileName.
-traceOutputStdout
Set the output of logging messages to be standard output. This option can be used with -traceOutputFile filename so that logging messages can be written both to the screen and the output file.
-traceResync
Enable logging messages for resync (node source) and resync parents. Logging messages contain node information including parent information OVPA is sending to Nerve Center.
To use this option, the log level must also be set to either debug or trace.
-traceInform
Enable logging messages for status informing from NerveCenter to OpenView. It shows status change messages from NerveCenter, whether the status change information is sent to OpenVien or is logged into OpenView database.
To use this option, the log level must also be set to either debug or trace.
-traceLoadDb
Enable logging messages for loading nodes and interfaces from the OpenView database at initialization stage. It shows each node and each interfaces are loaded.
To use this option, the log level must also be set to either debug or trace.
-traceParentComp
Enable logging messages for the details of how the parents are computed for each Nerve Center host.
To use this option, the log level must also be set to either debug or trace.
-traceMapUpdates
Enable logging messages for the processing of OpenView events regarding changes. This option displays the significant data that arrived with an OpenView event, how ovpa is processing that event, and whether network topology needs to be updated or not.
To use this option, the log level must be set to either debug or trace.
-traceConnects
Enable logging messages for connections from the NerveCenter server, and from OpenView. It also shows why the port is disconnected.
To use this option, the log level must also be set to either debug or trace.
-traceAll
Enable logging messages for resync, inform, loadDb, parentComp, mapUpdates, and connects.
To use this option, the log level must also be set to either debug or trace.
-pc
Enable parent computing. Without this option, no parent information is computed for any NerveCenter host, including the requests of resync parents from NerveCenter server, and the command line option -writeParentsToFile
-writeParentsToFile NcHostName
When -pc is turned on, OVPA computes parent-child relationships, writes to the file NcHostName_PC.dat, and exits.
-heartbeat seconds
The ovpa process and the NerveCenter server process exchange heartbeats. You can configure how often the heartbeat is sent from OVPA using the -heartbeat switch. If OVPA doesn't receive a heartbeat from NerveCenter in the specified time then it will close the connection to that server's port. Default heartbeat rate is 300 seconds.
-ignoreUnmanagedIntf
If this switch is used OVPA does not send NerveCenter server any unmanaged interfaces within a node. You may want to restrict the interfaces that NerveCenter server must poll to only interfaces that OpenView is currently managing. If you have many subobject scope alarms and nodes, this switch to improves polling performance.
-initNcStatusInOV
Synchronizes the status of a NerveCenter icon and its managed nodes.
-ignoreCapability
Determines whether OVPA keeps track of OpenView's capability information, such as IsRouter.For more information, see Filtering nodes from HP OpenView Network Node Manager.
-ignoreCapability prevent ovpa from keeping track of capability data. This increases ovpa's speed and decreases its memory usage.
This switch can be turn on when a user wants to force the node to be added to NC server, regardless of capabilities.
-noResolveCommunityOnResync
When this option is turned on, OVPA does not obtain the community strings during a resync or resync parents. You can use this argument when you are sure that the community has not changed since the initial OpenView database import to improve resync performance.
-defGlobalCommunity filename
Instead of retrieving community strings through OpenView, you can retrieve them from a file. This option is used to give the filename where user defines default community strings.
-info
-help
If you want these settings to take effect every time ovpa is started, edit the file ovpa.lrf to include these switches. On Windows, 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 you would modify ovpa.lrf to read:
ovpa:/opt/OSInc/nc/OV/bin/ovpa:
OVs_YES_START:ovwdb:-pc:OVs_WELL_BEHAVED:5:
Depending on how its behavior models are designed, a NerveCenter detecting particular network conditions can send Inform packets to HP OpenView Network Node Manager. Although these Inform packets use TCP/IP, they are similar in content to an SNMP trap, containing trap numbers (generic and specific), an enterprise OID, and a variable-binding list. The lengthy varbinds contains information about the alarm that performed the Inform action, such as the name of alarm, the object the alarm was monitoring, and the names of the origin and destination alarm states.
The OpenView receiving the trap can make use of the information in the variable bindings much the same way it would use variable bindings found in an SNMP trap.
Inform Trap Variable Bindings explains the contents of this variable-binding list.
| How to Reconfigure OpenView before Removing the NerveCenter OpenView Platform Adapter | Integrating NerveCenter with HP OpenView IT/Operations |
| 29 July 2003 |