Resolving Monitoring Agent Problems; Resolving Monitoring Server Problems - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

What to do next
For more information on actions that relate to these diagnostics, see the problem
resolution tasks.

Resolving monitoring agent problems

Monitoring agent problems, such as a monitoring agent that has not started can be
resolved by refreshing the Navigator status in the Managed System Status
workspace.
About this task
To resolve monitoring agent problems, you perform diagnostic and corrective
actions. These actions include checking the status of the monitoring agent and the
monitoring server.
Procedure
Diagnostic and corrective actions
1. Open the Managed System Status workspace and click View > Refresh.
2. Make sure the monitoring agent is connected to the correct monitoring server.
3. Check the status of the monitoring server that the monitoring agent is

Resolving monitoring server problems

Tivoli Enterprise Monitoring Server problems, such as loss of connectivity between
a monitoring agent and a remote monitoring server can be resolved by checking,
for example, that the remote monitoring server is connected to the hub monitoring
server.
Some causes of monitoring server problems:
v A remote monitoring server has shut down
v Loss of connectivity between the monitoring agent and the remote monitoring
v You receive the following message in the monitoring server log:
About this task
To resolve monitoring server problems, you perform diagnostic and corrective
actions. These actions include running tools, such as the ITMSUPER tools and
correcting connectivity failures.
Procedure
Diagnostic and corrective actions
1. Check the Managed System Status workspacein the portal client.
14
IBM Tivoli Monitoring: Troubleshooting Guide
connected to. For more information, see the monitoring server problem
resolution task.
server to which it reports, or between that monitoring server and the hub
monitoring server
KDS9151E: The heartbeat from remote TEMS variable
was not received at its scheduled time
and the remote TEMS has been marked offline.