Managing NerveCenter - Managing Node Data - Troubleshooting: Managing node data -
Previous: Adding and Deleting Nodes Manually     Next: Managing SNMP Settings

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 -nocap has been turned on.

Solution: From the command line, start OVPA with the -nocap 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 and IBM NetView for AIX.

Solution: Use the Discovery 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 NT 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" on page 94.

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.

The NerveCenter node list contains two nodes with the same address but different names

Problem: The node name was changed. When a resynchronization occurred between NerveCenter and the network management platform, the platform added the node.

Solution: Change the name of the node in your platform, not in NerveCenter's node list.

Synchronization with your network management platform.

NerveCenter deletes a node I added manually

Problem: At a resynchronization between NerveCenter and a network management platform, NerveCenter deletes any nodes marked autodelete that are not found in the platform's node database.

Solution: When you add the node disable the autodelete feature.

See Adding and Deleting Nodes Manually.

NerveCenter adds a node I deleted manually

Problem: At a resynchronization between NerveCenter and a network management platform or when NerveCenter runs the Discovery behavior model, NerveCenter adds any new nodes that fall within its filters.

Solution: Exclude the node in the IP filters before deleting it.

See "Filtering nodes using a Node's IP Address" on page 94.

I'm seeing several errors recorded in the application event log window stating that ipsweep.exe is not running

Problem:Your system is looking for ipsweep.exe in the wrong directory.

Solution:Update the correct path to ipsweep.exe in the alarm action Command in the Discovery behavior model.

Problem:Ipsweep.exe is already currently running.

Solution: Kill the first process and restart the Discovery behavior model.

See Designing and Managing Behavior Models in the NerveCenter documentation for more details.