ProbeWatch messages

During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.

The following table describes the ProbeWatch messages that the probe generates. For information about generic Netcool/OMNIbus ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
Table 1. ProbeWatch Messages

ProbeWatch message

Description

Triggers or causes

Communication failure - lost connection to NoticiationIRP

CORBA.TRANSIENT Exception: Lost connection to NotificationIRP

CORBA.OBJECT_NOT_EXIST Exception: Lost connection to NotificationIRP

Failed to connect to NotificationIRP: Shutting down

Failed to Connect: Either, the server is not running, the IOR is out of date, or probe cannot reach remote Server

The communication with the notification IRP server has failed.

The probe lost its connection to the notification IRP server.

END SYNCHRONIZATION

The synchronization of alarms has stopped.

The probe has resynched all the available alarms in the server.

Failed to find IOR file alarmirp_ior_file

The specified alarm IRP file does not exist.

The IRP manager has been set up incorrectly.

Failed to find IOR file notificationirp_ior_file

The specified notification IRP file does not exist.

The IRP manager has been set up incorrectly.

START SYNCHRONIZATION

The synchronization of alarms has started.

The probe started to resynchronize alarms collected in the system during the timeout period.

Will listen for commands on port numberlistening_port

The probe will listen for commands on the specified port number.

The probe has successfully created the CLI server on the specified command port specified in the properties file.