NerveCenterTM: Integration with
Micromuse Netcool/OMNIbus
-
Contents - NerveCenter Configuration Settings -
This section explains which NerveCenter components are configured to integrate with Netcool/OMNIbus and what should be configured for each component.
NerveCenter's configuration involves specifying the communication ports that allow the NerveCenter Server and adapter to transfer data to Netcool/OMNIbus. Secondly, NerveCenter must be set up to detect noteworthy conditions and send inform actions to Netcool/OMNIbus. Complete procedures for entering these settings are included in the online guides that are shipped with NerveCenter. The guides also describe the rights and privileges required for configuring the NerveCenter applications.
After installation, you enter settings in the NerveCenter Administrator to specify which hosts are to receive NerveCenter informs. When setting up a Netcool/OMNIbus recipient host, you must provide the host name and the port number to use for sending informs to the Universal Platform Adapter. The default port is 32509.
NerveCenter Inform Configuration shows the dialog box used for setting up informs.
NerveCenter Inform Configuration
The host and port number entered here must match the host and port number configured for the adapter (see Universal Platform Adapter Settings). If you later change the host or port number associated with the platform adapter, you must change the information entered here in the Administrator.
While setting up the inform configuration, you can specify a minimum severity level for informs or limit the informs to those with particular property groups. Refer to the Integrating NerveCenter with a Network Management Platform guide for more information about inform settings.
During installation, the platform adapter is configured with default settings that specify the adapter's host machine and the ports used to communicate with the NerveCenter Server and the NerveCenter probe. Depending on your configuration, you may need to change the default settings.
The command to change the platform adapter settings resembles the following:
paserver -o -p listeningport -n ON -nhost hostname -nport
sendingport
The command contains the switches shown in Switches for Reconfiguring the NerveCenter Platform Adapter:
Switches for Reconfiguring the NerveCenter Platform Adapter
| Switch | Description |
|---|---|
Windows only, records values into the registry. Any options (other than -scm) become a part of the standard configuration. To use this switch, you should first stop the Universal Platform Adapter. You must then restart the Universal Platform Adapter. | |
Defines the platform adapter's listening port. The adapter uses this port to communicate with the NerveCenter Server. This number must match the port number specified in NerveCenter Administrator for sending informs. The default is 32509. | |
Enables or disables NerveCenter integration with Micromuse Netcool/OMNIbus. | |
Defines the machine on which the NerveCenter probe is located. The default is the local host where the adapter is installed. If the adapter and probe are on different machines, this value must be changed. | |
Defines the port the NerveCenter platform adaptor uses to communicate with the probe. The default is 32510. See Nervecenter.props file for more information about probe settings. This number must match the number used by the probe to communicate with NerveCenter, as specified in the probe's property file. Some early versions of the probe used port 10001; these should be replaced with the current version. |
You can also enter settings when you start the platform adapter. For complete procedures and settings, refer to the online book Integrating NerveCenter with a Network Management Platform that is shipped with NerveCenter.
Ports for Communication Between NerveCenter and Netcool/OMNIbus summarizes the port settings for NerveCenter-Netcool communication.
Ports for Communication Between NerveCenter and Netcool/OMNIbus
After installation, you can customize or create new behavior models in the NerveCenter Client. The alarms used in behavior models define the types of actions performed when specific network conditions are detected. For each alarm you want to forward to Netcool/OMNIbus, you must define an inform action in the corresponding alarm.
IfLoad Alarm and Transition Definition Dialog Box shows a sample alarm along with the dialog box used to define transitions and configure actions for the transitions. Also shown is the pop-up menu containing the available actions.
IfLoad Alarm and Transition Definition Dialog Box
Inform Action Dialog Box shows the dialog box used to define inform actions for Netcool/OMNIbus.
When creating an inform action, you have the option of providing a specific inform number. This number becomes the $MesgID value sent with each inform and helps Netcool/OMNIbus identify the type of event. If you don't provide a specific number, the message ID defaults to the value 1000 for any transition whose destination state has a severity less than 9 (Warning). For severity levels of 9 or greater, the $MesgID defaults to the value 1000 plus the destination state's severity level.
You can define one or more informs for as many alarms as you want. Once you have defined the inform action and enabled an alarm, the inform is sent each time the associated transition occurs. For more information about designing behavior models using the Client, refer to the Designing and Managing Behavior Models guide.
| How the Integration Components Interact | Netcool/OMNIbus Configuration Settings |
| 29 July 2003 |