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 ProbeWatch messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC23-6373).
ProbeWatch message |
Description |
Triggers/Causes |
|---|---|---|
Alcatel OSOS probe running on host host |
The probe is running normally. |
The probe has just been started on the named host. |
Trying to connect to host host on port port Trying to connect to |
The probe is attempting to connect to the host. |
The probe tried to login to the OS-OS system. |
Cannot connect to host host on port port; Retrying Cannot connect to |
The probe failed to connect to the host. |
The probe could not connect to the OS-OS system. |
Probe successfully connected to host host on port port Successfuly connected to |
The probe connected to the host. |
The probe connected to the OS-OS system using the given properties. |
Failed to login to remote host; Closing connection |
The probe failed to log in to the system. |
Either the value specified for the ConnectionTimeout property is too small, or the values specified for the Host and Port properties are incorrect. |
Login successful |
The probe received a connection confirmation message. |
The probe has connected to the OS-OS system. |
Login rejected by remote host; probe shutdown |
The probe received a connection rejected message. |
Either the value specified for the LoginTimeout property is too small, or the destination server is not working. |
Failed to get heartbeat confirmation; Closing connection Failed to get heartbeat confirmation; Retrying |
The probe failed to receive the first heartbeat message from the system. |
Either the value specified for the HeartbeatInterval is inadequate, or the destination server is not working. |
Heartbeat successful; Requesting unsolicited alarms (if OSOSHeartbeatInterval > 0) Heartbeat skipped; Requesting unsolicited alarms (if OSOSHeartbeatInterval = 0) Heartbeat received |
The probe has received the first heartbeat message from the system. |
The OS-OS system sent a response to the heartbeat message from the probe. |
Resynchronization failed; Closing connection Resynchronisation request failed |
The probe failed to receive resynchronization data. |
The value specified by the RequestTimeout property is inadequate. |
Resynchronization successful resynchronisation complete |
The probe received resynchronization data. |
The probe has resynchronized alarms from the OS-OS system. |
Requesting current alarm list Requesting resynchronisation |
The probe is requesting periodic resynchronization. |
The probe has reached the next resynchronization time specified by the HeartbeatInterval property. |
Failed to get current alarms request confirmation; Closing connection |
The probe failed to receive an alarm request confirmation. |
The resynchronization attempt by the probe has failed. |
Current alarms request confirmation received; Starting resynchronization Resynchronisation started |
The probe received an alarm request confirmation. |
The resynchronization attempt by the probe was successful. |
Invalid data received |
The probe received invalid data. |
The connection to the OS-OS system is not working. |
Disconnection request received; probe shutdown |
The probe shuts down following a disconnection request. |
Either the connection attempt by the probe has failed, or the destination system is not available. |