Integrating NerveCenter with a Network Management Platform - Integrating NerveCenter with HP OpenView Network Node Manager - Using OpenView as a node source - Synchronization with HP OpenView Network Node Manager -
Previous: Populating NerveCenter's node list using OpenView as a node data source     Next: Filtering nodes from HP OpenView Network Node Manager

Synchronization with HP OpenView Network Node Manager

Over time, a network's topology will change. Eventually OpenView will add newly discovered devices to its database. It will also delete nodes and change node information. If NerveCenter depends on OpenView for the data in its node list, it will need to adapt to reflect these changes.

NerveCenter will automatically update its node list to keep in sync with OpenView's node data. This occurs in the following situations:

Most often, the node list will only be updated a node at a time. Occasionally, NerveCenter will need to perform a complete resynchronization with the platform. A resynchronization gathers from the platform the most current node data for all nodes. This occurs in the following situations:

The Machine Name field on the Node Source tab of the NerveCenter Administrator specifies the name of the host running the platform resynchronizing with NerveCenter. (See for more details on how to declare a node data source.) The Node Source and IP Filters tabs also specify the parameters NerveCenter uses to filter node data. (See .)

Anyone administering NerveCenter should be aware of two important scenarios involving changes to OpenView's database:


Previous: Populating NerveCenter's node list using OpenView as a node data source Next: Filtering nodes from HP OpenView Network Node Manager
Please send comments or corrections to Information Development
This file was last updated on 10 October 2000