Designing and Managing Behavior Models
-
Using Other Data Sources - Another NerveCenter -
The section Using Multiple NerveCenter Servers on page 23 introduced the idea of using NerveCenter servers at the various sites within an enterprise to monitor the network conditions at those sites and then to forward important events on to a central NerveCenter server. In this situation, the central server can correlate the events it receives from the remote servers, take appropriate corrective actions, and notify a network management platform of any serious problems it discovers.
Remote servers communicate with the central server using an alarm action called Inform -- the same action used to communicate with a network management platform. (For complete information about the Inform alarm action, see the section Inform on page 273.) When a remote server performs this type of Inform action, it sends to the central server what looks like an SNMP trap. This trap's specific trap number is determined by the person who sets up the alarm that initiates the Inform action. The trap also contains a set of variable bindings that include information about the alarm transition that led to the Inform being sent.
The central server handles the traps sent from remote servers just as it handles other traps: by using a trap mask. The only things special about the trap masks you use to receive traps from other NerveCenter servers are that:
For further information about receiving traps from other NerveCenter servers, see the following sections:
| An Example Using Built-In Triggers | Creating a Trap Mask |
| 29 July 2003 |