Integrating NerveCenter with a Network
Management Platform
-
Integrating NerveCenter with HP OpenView IT/Operations - Using IT/Operations as a node source - Identifying Parent-Child Relationships -
In order to use NerveCenter's Downstream Alarm Suppression behavior model, it is necessary to establish the parent-child relationship between nodes. You can let OVPA extract relationship information from HP OpenView IT/Operations and either store it in the NerveCenter database or in a text file. You can also create the text file manually.
To identify parent-child relationships using OVPA:
ovstop ovpa
at the command line.
ovpa -pc
OVPA runs and computes parenting information, resychronizing the information periodically. The how often OVPA resychronizes information is configurable through the Node Source tab in the NerveCenter Administrator. The default resync parent rate is 600 seconds.
ovpa -pc
-writeParentsToFile
hostname
hostname is the name of the machine on which the NerveCenter Server runs. OVPA computes the parenting information, writes it to a file named hostname_PC.dat, and then stops.
To change the resync parent rate:
For further instructions, see Managing NerveCenter.
Node Source
tab.NerveCenter displays the Node Source tab.
Resync Parent Rate
field, type the number of seconds you want between each resync attempt.If left blank, the default resync parent rate is 600.
Save
.
To identify parent-child relationships manually:
child parent
where child is the name of the node and parent is the name of each node on which the child is dependent. If you have more than one parent, separate parents by typing a space between each one.
For example, if nodeA is dependent on nodeB.domain.com and nodeC, and nodeB.domain.com is dependent on nodeD, then the contents of the text file would look like this:
nodeA nodeB.domain.com nodeC
nodeB.domain.com nodeD
For more information see the White Paper Open NerveCenter: Downstream Alarm Suppression.
Using IT/Operations as a node source | Specifying the Destination of NerveCenter Inform Packets sent to HP OpenView IT/Operations |
29 July 2003 |