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

support on a z/OS monitoring server, see "Adding application support to a
monitoring server on z/OS" in Configuring IBM Tivoli Enterprise Monitoring Server
on z/OS.

Resolving monitoring server problems

Monitoring server problems are caused by a monitoring server that is not started
or connectivity that is lost either between servers or between servers and agents.
You can restart the Tivoli Enterprise Monitoring Server, and you can also run the
ITMSUPER Topology tool to get more information.
About this task
To resolve monitoring server problems, you perform diagnostic and corrective
actions. These actions include running tools, such as the Topology or Connectivity
tool and correcting communication failures in logs.
Procedure
Diagnostic and corrective actions
1. If you are an administrator, restart the monitoring server. Otherwise, notify an
2. Running the following ITMSUPER tools might also provide more information:
3. Check the portal server logs for messages indicating communication failures to
4. Check the monitoring server logs for messages indicating communication
5. Correct the communication failures indicated in the logs.

Resolving monitoring agent problems

If the monitoring agent is running but data is not being returned or if you receive
an error message from an agent log, such as Endpoint unresponsive, verify that the
agent is connected and online. You can also verify that application support has
been installed correctly.
About this task
To resolve monitoring agent problems, you perform diagnostic and corrective
actions. These actions include verifying that the agent is running and that
application support has been installed correctly. For information on monitoring
agents on z/OS
Procedure
Diagnostic and corrective actions
1. Verify that the agent is connected. Check the monitoring server log for
2. If the agent is online, check to see whether subnodes are online in the agent
12
IBM Tivoli Monitoring: Troubleshooting Guide
administrator and wait for the monitoring server to be restarted.
v Topology tool
v Connectivity tool
v Tivoli Enterprise Monitoring Server analysis tool
v Tivoli Enterprise Portal Server
the monitoring server.
failures to the remote monitoring servers or to monitoring agents.
®
see each product's Problem Determination Guide.
messages similar to Remote node <SYS:MQIRA> is ON-LINE.
log. For example: KMQMI171I Node JSG1:SYS:MQESA is online.