Designing and Managing Behavior Models
-
Discovering and Defining Nodes - Discovering Nodes - Using NerveCenter's IPSweep Behavior Model -
For times when you want NerveCenter to discover the devices on a network, NerveCenter includes the IPSweep behavior model. To use this behavior model, you -- or for the first step, an administrator -- must perform the following tasks:
This information can be specified either when NerveCenter is installed or later via the NerveCenter Administrator. For details on installing NerveCenter, see Installing NerveCenter, and for information about using the NerveCenter Administrator, see Integrating NerveCenter with a Network Management Platform.
Once the IPSweep behavior model becomes operational, it will find the devices on the subnets you've specified and, for each node, send a trap to either the NerveCenter server or the network management platform. If the trap is sent to NerveCenter, the server creates a node definition and places it in the NerveCenter database. If the trap is sent to the platform, the platform writes information about the node to its database, and then that information becomes available to NerveCenter.
Both the customization and enabling of the IPSweep alarm is handled from the NerveCenter Client. For instructions on how to modify and enable these alarms, refer to the following sections:
The IPSweep alarm actually executes the program, ipsweep, that discovers devices on your network. If NerveCenter was installed in the default directory, this alarm will work correctly without modification. However, if the product was installed in a non-default directory, you must change the Command action associated with one of the alarm's transitions so that the path to ipsweep is correct. You may also want to change the delay between executions of the ipsweep program. The instructions below explain how to change both the delay and the path to the ipsweep program.
From the client's
Admin
menu, choose Alarm Definition List
.
The Alarm Definition List window is displayed.
Open
button.The definition of the IPSweep alarm is displayed in the Alarm Definition window.
Off
.The alarm may be turned on even if you've never explicitly enabled it. This is possible because the person who configured NerveCenter may have requested that the server enable this alarm on startup.
The Transition Definition dialog is displayed.
The Fire Trigger Action dialog is displayed.
A short delay will generate more network traffic, while a long delay will mean a longer wait for new devices to be discovered.
OK
button in the Fire Trigger Action window.
OK
button in the Transition Definition window.
The Transition Definition window is displayed.
The Command Action dialog is displayed.
Command
text field so that it contains the correct path to the ipsweep program.
OK
button in the Command Action window.
OK
button in the Transition Definition window.
Save
button in the Alarm Definition window.Once you've modified the IPSweep alarm, you must enable the alarm for the IPSweep behavior model to become functional.
For each alarm, perform this step and the following steps. From the client's
Admin
menu, select Alarm Definition List
.
The Alarm Definition List window is displayed.
Open
button.The alarm's definition is displayed in the Alarm Definition window.
On
radio button in the Enabled frame.
Save
button at the bottom of the window.Using a Network Management Platform's Discovery Mechanism | Defining Nodes Manually |
29 July 2003 |