IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 47 / 310

Procedure
Diagnostic and corrective actions
1.
Does the system command run correctly from a command line?
v
Yes: Go to the next step.
v
No: Verify that the command you typed in is correct.
2. Is the length of the command within the limit for your operating system?
v
Yes: Go to the next step.
v No: The command cannot be executed on this platform. You might be able to
write a wrapper script to issue the command.
3. Are the required user type and environment variables correct?
v
Yes: Go to the next step.
v
No: Include the
set
command in the shell script or batch script and redirect
the output to a file. Review the file afterwards to show which variables are
being used.
4. Collect the monitoring agent operations log, which shows whether reflex
automation occurred. A monitoring server message log also confirms which
error occurred.
5. Correct the identified problem.
High CPU usage on a distributed system
You can encounter a problem that CPU usage is high on a distributed system.
Symptoms of the problem:
v
Performance degrades or availability is lost because of high processing in an
application or a computer.
v
No data is returned in the portal client and the collector log contains the text
string
Open Probe pipe error
. See “Resolving Oracle DB Agent problems -
corrective actions” on page 32.
v
Situations alert you frequently about a managed system cycling between online
and offline. See “Resolving firewall problems - corrective actions” on page 31.
Diagnosing high CPU usage on a distributed system
You can diagnose that CPU usage is high on a distributed system by determining
whether a monitoring component, application, or process running on the system
might be the cause of the problem. Also, you can use the ITMSUPER tools, such as
the Connectivity tool to provide more information.
About this task
To diagnose that CPU usage is high on a distributed system, perform the following
steps:
Procedure
Preliminary diagnostics
1. Determine whether an IBM Tivoli Monitoring component is the root cause.
Another application or process running on the system might be causing high
CPU usage.
Chapter 3. Common problem solving
29