TSMWatch 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 TSMWatch error messages that the TSM generates. For information about generic TSMWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
Error |
Description |
Action |
|---|---|---|
Connection attempted |
The TSM is trying to establish a connection to the host. | The TSM is trying to establish a connection to the host. |
Connection failed |
The TSM 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 TSM. |
Connection Going Down … |
The TSM is disconnecting from the host. | Either there are insufficient licenses in the license server, the TSM has received a bounce command from the command port, or the TSM is having problems reading from the socket. |
Connection lost |
The TSM has lost the connection to the host. | The device has dropped the connection to the TSM. |
Connection succeeded |
The TSM has successfully established a connection to the host. | The TSM has successfully established a connection to the host. |
Disconnection Attempted … |
The TSM is attempting to disconnect from the host. | The TSM is shutting down or has lost the connection. |
Disconnection Failed … |
The TSM has failed to disconnect cleanly from the host. | There has been a corruption of the memory location storing the connection details. |
Disconnection succeeded … |
The TSM has disconnected from the host. | The TSM shut down or lost the connection. |
Failed to get a license for host: port |
The TSM 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 TSM is shutting down. | The TSM is shutting down after performing the shutdown routine. |
Heartbeat response received |
A heartbeat response has been received within the period specified by the HeartbeatTimeout property. | A response matching the HeartbeatResponse property in the props or hosts file has been received. |
Heartbeat response timed out |
A response to the heartbeat string has not been received for the period specified by the HeartbeatTimeout property. | The TSM has not received the expected response or an event and is disconnecting from and reconnecting to the host. |
Heartbeat sent |
A heartbeat string has been sent from the TSM to the host. | The TSM has not received an event from the device for the period specified by the HeartbeatInterval property. |
Login attempted |
The TSM is trying to log in to the host. | The TSM is trying to log in to the host. |
Login failed |
The TSM has failed to log in to the host. | The TSM has encountered a problem while logging in. Check that the ChatinString property is specified correctly. |
Login succeeded |
The TSM has logged in to the host. | The TSM has logged in to the host. |
Logout attempted |
The TSM is trying to log out from the host. | The TSM has received a command to shut down or has received the bounce command from the command port. |
Logout failed |
The TSM has failed to log out from the host. | The TSM has encountered a problem while logging out. Check that the ChatoutString property is specified correctly. |
Logout succeeded |
The TSM has logged out from the host. | The TSM has logged out from the host. |
Running … |
The TSM is running normally. | The TSM has just been started. |
Unable 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. |