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 raw probe Watch error messages that the probe generates. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers or causes
Cannot connect to `host`	The probe cannot connect to `host`.	The connection might be blocked by a firewall or the hostname is incorrect.
Connection inactive	The connection between the probe and the fault adapter is inactive.	The read timeout period has expired and heartbeating is not in use to help restore the connection.
`Established connection host`	The probe successfully connected to the given `host`.	The probe has connected to the Tellabs 8000 INM system.
`Finished reading incoming alarms`	The resynchronization process completed successfully.	The probe has connected to the Tellabs 8000 INM system and successfully resynchronized with all active alarms.
`Going Down ...`	The probe is shutting down.	The probe is shutting down after performing the shutdown routine.
`Running ...`	The probe is running normally.	The probe has just been started up.
`Status field value of status not valid for msgtype msgtype`	The status of a received message was not equal to 1 (Success).	The fault adapter may be unavailable.
`Timed out while trying to connect to host`	The probe's response timeout period expired while connecting to the given `host`.	The host has not responded to the probe within the time specified by the ResponseTimeout property.
`Tellabs fault adapter may be down`	The status of a received message was not equal to 1 (Success).	The fault adapter may be unavailable.
`Unable to get events`	A problem occurred while trying to receive events.	If this message was sent at startup, it indicates that there was a problem initializing the connection due to insufficient memory. If this message was sent after some events had been parsed, it indicates that there was a connection failure.
`Unable to remove process ID file pid_file_location.`	The probe was unable to remove the file `pid_file_location`.	The probe does not have permission to remove the file, the file does not exist, the file location does not exist, or the file is not in the specified location.
`Unable to write process ID file, pid_file_location`	The probe was not able to open the file `pid_file_location` for writing.	The probe does not have permission to write to the file, the file does not exist, the file location does not exist, or the file is not in the specified location.