Managing NerveCenter
-
Troubleshooting NerveCenter - Common problems -
The following list includes some of the more common problems users face when administering NerveCenter.
UNIX will not start the NerveCenter Server on page 33.
An alarm causes the NerveCenter Server to crash every time I start it on page 34.
The NerveCenter Server does not start on Windows on page 34.
I need to get a better idea of what the NerveCenter Server is doing on Windows. Can I temporarily run it as a process? on page 34
UNIX will not start the NerveCenter Administrator on page 44.
While trying to connect to a NerveCenter Server I get the message: The server did not respond on page 44.
I misspelled a server name while trying to connect and now the misspelled name appears in the NerveCenter Administrator Server Name list on page 44.
When I try to connect to a NerveCenter Server it tells me: Number of allowed client connection exceeded on page 60.
I need to make the same changes to several NerveCenter Servers on page 60.
Importing imputil.ini caused unwanted changes to a NerveCenter Server on page 60.
NerveCenter is not filtering a node by a capability on page 95.
After setting an IP filter, a node that should be masked out still appears in the node list on page 95.
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 on page 95.
NerveCenter does not recognize my network management platform as a valid source of node data on page 96.
NerveCenter is not receiving node data from my network management platform on page 96.
The IPSweep behavior model will not work on page 96.
The NerveCenter node list contains two nodes with the same address but different names on page 97.
NerveCenter deletes a node I added manually on page 97.
NerveCenter adds a node I deleted manually on page 97.
I'm seeing several errors recorded in the application event log window stating that ipsweep.exe is not running on page 97.
NerveCenter is not sending SMTP mail notifications on page 151.
Microsoft mail notifications are not being sent as NerveCenter on page 151.
NerveCenter is not dialing pages correctly on page 151.
The logs created by my behavior models are using too much disk space on page 151.
The server shut down gracefully, but event log said that the database was not found. Where did the updates to the database go? on page 174
Running SerializeDB from the command line keeps failing on page 174.
SerializeDB won't work from the application or the command line on page 174.
The data in the database is not what was imported from the serialized file on page 174.
A MIB won't compile on page 184.
| Troubleshooting NerveCenter | Using Trace Counters to Troubleshoot NerveCenter |
| 29 July 2003 |