Managing NerveCenter - Managing Node Data - Troubleshooting: Managing node data -
Maintaining the Node List      The NerveCenter node list contains two nodes with the same address but different names

Troubleshooting: Managing node data

The following list contains some common problems users have when managing node data.

NerveCenter is not filtering a node by a capability

Problem: Filtering by capabilities is available only when a network management platform has assigned a specific capability to a node.

Solution: Have your network management platform assign a capability to the node.

See your network management platform's documentation for details.

Problem: The OVPA command line switch -ignoreCapability has been turned on.

Solution: From the command line, start OVPA without the -ignoreCapability switch.

For more details see the book Integrating NerveCenter with a Network Management Platform.

After setting an IP filter, a node that should be masked out still appears in the node list

Problem: IP filters only exclude additional nodes from being added to a node list. It does not actively delete nodes in the node list.

Solution: Either manually delete the node or force a resynchronization with your network management platform.

See Adding and Deleting Nodes Manually or Synchronization with your network management platform.

Even though I have enabled Process Traps From Unknown Nodes, NerveCenter does not update its node list when it receives a trap from an unknown node

Problem: Selecting the Process Traps From Unknown Nodes box does not affect NerveCenter's node list. It only tells NerveCenter to process traps.

Solution: If you want NerveCenter to update its node list based on traps received from unknown nodes, set Discover Nodes from Traps to Filter or All.

See Adding Nodes Discovered from Traps.

NerveCenter does not recognize my network management platform as a valid source of node data

Problem: Currently NerveCenter is able to retrieve node data from HP OpenView Network Node Manager.

Solution: Use the IPSweep behavior model to obtain node data.

See Populating Using the IPSweep Behavior Model.

NerveCenter is not receiving node data from my network management platform

Problem: They are using different ports.

Solution: Configure the node data source port number to be the same as the platform adapter's port.

See Populating NerveCenter's node list using your network management platform as a node data source.

The IPSweep behavior model will not work

Problem: Windows is configured with Domain Name Server.

Solution: Enable the Enable DNS for Windows Resolution feature.

See Populating Using the IPSweep Behavior Model.

Problem: There are no IP filters. NerveCenter will not discover nodes unless there are IP filters. This precaution is to prevent NerveCenter from trying to discover all the nodes on the Internet.

Solution: Set the appropriate IP filters.

See Filtering nodes using a Node's IP Address.

Problem: The NerveCenter Server is not set to discover nodes from traps.

Solution: Set Discover Nodes from Traps to All or Filter.

See: Adding Nodes Discovered from Traps.