Managing NerveCenter - Managing Node Data - Processing Traps from Unknown Nodes -
Filtering Using a Node's System Object Identifier      Populating the Node List Initially

Processing Traps from Unknown Nodes

NerveCenter offers a lot of flexibility in filtering the managed nodes it monitors. See Filtering Nodes. By setting these filters, you are telling NerveCenter to ignore any traps sent by nodes not stored in the node list. This keeps the node list to a size that is manageable and acceptable under your license agreement.

However, there may be times you will want a NerveCenter Server to process a trap from a node not found in its node list, but in the node list of another NerveCenter Server.

For example, in the following diagram, a NerveCenter Server responsible for monitoring a LAN (Server A) needs to pass a trap along to a WAN-level NerveCenter Server (Server B).

An Example of a Trap Being Processed from an Unknown Node

In this case, Node 1 is in the node list of Server A. Node 1 sends a trap to Server A, which in turn is passed along to Server B. Because Node 1 is being managed by Server A, it will not appear in Server B's node list. Server B needs to process the trap from Node 1. Server B could be set up to add unknown nodes to its node list whenever it receives a trap, but then both Server A and Server B will be monitoring Node 1. How can Server B process the trap from Node 1 without first adding the node to its node list?

NerveCenter's Process traps from unknown nodes feature allows a NerveCenter Server receiving a trap from an unknown node to process that trap if the trap is associated with an Enterprise scope alarm.

---

   The Process traps from unknown nodes feature will only process traps associated with Enterprise scope alarms.

---

At the same time, the Process traps from unknown nodes feature will keep the NerveCenter Server from adding the node to its node list. This ensures that the NerveCenter Server does not exceed the node limit allowed by its license. It also avoids a situation in which two NerveCenter Servers are responsible for the same node.

---

   If you want to learn how a NerveCenter Server can add an unknown node to its node list when it receives a trap from that node, see the section Adding Nodes Discovered from Traps.

---

 
  To process traps from unknown nodes:

1. Open NerveCenter Administrator and connect to the appropriate NerveCenter Server.

   See Connecting Administrator to a NerveCenter Server on page 38.

2. Select the Server tab.

   NerveCenter displays the Server tab.

   

3. Select the Process Traps From Unknown Nodes box.

   If this box is not selected, then NerveCenter will ignore any trap it receives from a node not included in its node list.

4. Select Save.

The NerveCenter Server will now process traps associated with Enterprise scope alarms even when those traps are received from nodes not appearing in the server's node list.