|
Component
|
Description
|
|---|
NerveCenter Server |
The NerveCenter Server carries out all of the major tasks that NerveCenter performs. It manages communication among all components, processes event data from managed nodes, performs automated actions, saves all behavior model data to the database, and loads the compiled MIB file. The server can run as a daemon on UNIX systems and as a service on Windows systems. |
Database |
A database or flat file is the repository for information about NerveCenter's behavior models and the nodes NerveCenter monitors. Database utilities allow you to convert, update, import, or export the NerveCenter database. Most operations can be performed without shutting down the NerveCenter Server. |
MIB definitions |
NerveCenter ships with support for standard RFC MIB definitions and specific vendor devices. Users can add and remove MIBs using a supplied MIB compiler. |
NerveCenter Administrator |
After installing NerveCenter, you can use the NerveCenter Administrator to configure the settings for the connected Server. These values are stored with the NerveCenter configuration settings. |
NerveCenter Client |
The NerveCenter Client lets you monitor the network as well as create and modify the behavior models managed by the NerveCenter Server. Once connected to a Server, you can access the MIBs, nodes, behavior models, alarm filters, and other NerveCenter objects associated with that Server. |
Command line interface (CLI) |
You can use the CLI to operate NerveCenter from a DOS command prompt or a UNIX shell. From the command line, you can list, delete, and control NerveCenter objects, such as nodes, alarms, polls, and masks. You can issue the commands manually or from a script. |
Configuration Settings |
Server settings are stored in the nervecenter.xml configuration file (UNIX) and the Registry (Windows). |
