Integrating NerveCenter with a Network Management Platform - Integrating NerveCenter with Tivoli TME - How to Specify the Destination of Inform Packets Sent to Tivoli TME -
Starting and Stopping Platform Integration with Tivoli TME      How to Configure Tivoli to Integrate with the NerveCenter Universal Platform Adapter

How to Specify the Destination of Inform Packets Sent to Tivoli TME

One of the most powerful characteristics of NerveCenter's platform integration is how it informs Tivoli TME. Since NerveCenter's inform packets use the Transmission Control Protocol (TCP), the alert sent to Tivoli is more reliable then a standard SNMP trap. As you create or modify a behavior model to notify Tivoli, you determine the specific inform number it will receive. However, before you can use this behavior model, NerveCenter must know which machine or machines will receive the inform.

The following procedure will step you through the process of declaring one or more recipients of NerveCenter informs.

 
  To specify the destination of NerveCenter informs sent to Tivoli:

1. Open NerveCenter Administrator and connect to the appropriate NerveCenter Server. If you need help opening NerveCenter Administrator or connecting to a NerveCenter Server, see Managing NerveCenter.
2. Select the Inform Configuration tab.

   The Inform Configuration tab appears.

   

3. In the Inform Host Type field, select the radio button beside Tivoli.

   Selecting this option enables the NerveCenter Server to recognize the inform recipient as a platform needing the NerveCenter Universal Platform Adapter.

4. In the Machine Name field, type the name of the machine hosting Tivoli.
5. In the Port field, type the port number your NerveCenter Server will use when communicating with the NerveCenter Universal Platform Adapter.

   By default, NerveCenter uses the port number 32509.

6. In the Notify On field, select EVENT_ONLY.

   NerveCenter send events to Tivoli when the Inform Platform action is invoked.

7. In the Minimum Severity field, type the number representing the minimum severity an alarm must reach before triggering a message to this platform.

   This option enables you to be selective about which events are sent to particular platforms. For example, a local platform could get all events, while a lead or central platform could get only critical events. When NerveCenter sends Informs to your platform, NerveCenter first checks the minimum severity value entered here to ensure that the trap value for the Inform matches or exceeds that severity.

   ---

      There is one case when NerveCenter disregards the minimum severity value specified in Administrator: After NerveCenter sends an Inform, if the condition returns to a normal state-that is, a state below the minimum severity threshold you configure-it's important that NerveCenter notify the platform of this change. Therefore, if a node transitions the alarm from a severity above the minimum value to a severity below the minimum value, and the transition includes an Inform action, NerveCenter will send a Normal Inform to the platform. This allows the platform to reset the mapped severity color associated with the node.

   ---

   ---

      The values associated with each severity in NerveCenter can be viewed and altered in the NerveCenter Client in the Severity List found under the Admin menu.

   ---

8. In the Properties field, type zero or more properties.

   NerveCenter will only send an Inform packet to this platform if the managed node's property group contains at least one of the properties listed in this field. If no events are listed, NerveCenter sends events for all managed nodes.

   This option enables you to be selective in which events are sent to particular platforms. For example, one platform could receive informs only prompted by routers.

9. Select Add.

   The platform's host machine is added to the Inform Recipient list.

10. Repeat steps 3 through 9 for each different machine hosting a network management platform that will receive a NerveCenter inform packet.
11. Select Save.

When an alarm performs an Inform Platform action, the relevant platforms included in this list will receive the inform data.