Managing NerveCenter
-
Understanding NerveCenter - How NerveCenter Manages Nodes -
To perform its job of event automation, NerveCenter relies on the definition of behavior models. These models are constructed from NerveCenter objects (which we'll discuss in detail later) and define:
The following sections elaborate on the tasks that NerveCenter performs in order to automate event handling:
NerveCenter can get the list of devices to monitor from a network management platform, discover them on the network, or import this information from another NerveCenter database.
NerveCenter assigns to each managed node a set of properties, and these properties determine which behavior models apply to a node. Properties typically describe the type of the device -- for example, a router -- or are named after objects in the management information base (MIB) used to manage the node.
Once NerveCenter assigns a set of properties to a node, NerveCenter automatically applies to that node all of the models that refer to those properties. If NerveCenter detects that a node has been deleted or that its properties have changed, the product immediately retires or updates the set of models that are actively managing that node. This dynamic process enables NerveCenter to adapt at once to changes in network configuration reported by the management platform or by NerveCenter's own discovery mechanism.
It is also possible to assign properties to nodes manually to further refine the set of models that NerveCenter uses to manage a node. For example, you may want to distinguish a backbone router from a campus router to regulate how much and how often status information is collected.
| What is NerveCenter? | Detecting Conditions |
| 29 July 2003 |