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 error messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7530).
ProbeWatch message |
Description |
Triggers/causes |
---|---|---|
Connection attempted ... (<host>,<port>) | The probe is trying to establish a connection to the host. |
The probe is trying to establish a connection to the host. |
Connection failed ... (<host>,<port>) | The probe has failed to establish a connection to the host. |
General connection failure due either to an incorrect setting of the Host or Port property, or the host refusing a connection request from the probe. |
Connection lost ... (<host>,<port>) | The probe has lost the connection to the host. |
The device has dropped the connection to the probe. |
Connection succeeded ... (<host>,<port>) | The probe has successfully established a connection to the host. |
The probe has successfully established a connection to the host. |
Disconnected from system due to shutdown signal | The probe has disconnected from the host. |
A shutdown signal was sent to the probe. |
Disconnecting from system due to Inactivity alarm ... (<host>,<port>) | The probe has disconnected from the device. |
The device was silent for the period specified by the Inactivity property. If you want the probe to time out less frequently, increase this value. |
Disconnection attempted ... (<host>,<port>) | The probe is attempting to disconnect from the host. |
The probe is shutting down or has lost the connection. |
Disconnection failed ... (<host>,<port>) | The probe has failed to disconnect cleanly from the host. |
The logout procedure failed. |
Disconnection succeeded ... (<host>,<port>) | The probe has disconnected from the host. |
The probe shut down or lost the connection. |
Event from (<host>,<port>) did not match the expected format! | The event received by the probe does not match any of the supported event formats. |
The probe has received an event that does not match any of the supported event formats. |
Failed to get events | A problem occurred while receiving events. |
Either there was a problem initializing the connection due to insufficient memory or (if this message was sent after some events had been parsed) there was a license or a connection failure. |
Failed to get license ... (<host>,<port>) | The probe is unable to obtain a license for the connection to the host. |
Either the license server is down or there are insufficient licenses in the server. |
Going Down ... | The probe is shutting down. |
The probe is shutting down after performing the shutdown routine. |
Have lost all connections - going down | The probe is shutting down because all of its connections have been deactivated. |
The number of times that the probe has attempted reconnection for each of its connections has exceeded that specified by the ReconnectionAttempts property. |
License failure - going down | The license server could not be reached. |
Either the license has expired, the license server has gone down, or the connection to the license server has been lost. |
Login attempted ... (<host>,<port>) | The probe is trying to log in to the host. |
The probe is trying to log in to the host. |
Login failed ... (<host>,<port>) | The probe has failed to log in to the host. The probe has encountered a problem while logging in. |
Check that the ChatinString property is specified correctly. |
Login succeeded ... (<host>,<port>) | The probe has logged in to the host. |
The probe has logged in to the host. |
Logout attempted ... (<host>,<port>) | The probe is trying to log out from the host. |
The probe has received a command to shut down. |
Logout failed ... (<host>,<port>) | The probe has failed to log out from the host. |
The probe has encountered a problem while logging out. Check that the ChatoutString property is specified correctly. |
Logout succeeded ... (<host>,<port>) | The probe has logged out from the host. |
The probe has logged out from the host. |
Running ... | The probe is running normally. |
The probe has just been started. |