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

Page: 48 / 310

2. Use the tools and data provided by Task Manager to identify the process
causing high CPU usage. In the Processes tab you can reorder the processes by
CPU usage. An example of a process name is
kntcma.exe
for the Windows OS
agent.
3. Use the
top
command to display processes using high CPU. For
UNIX, you can also use the
ps auxww
command.
4. Verify the following:
v
Is historical data collection enabled?
v Is the database undergoing a backup?
5. Is the situation writing a lot of event logs?
v
Yes: Disable all event log monitoring situations.
6. Select each of the workspaces in turn, to see which one is consuming high
CPU.
7.
Running the following ITMSUPER tools might also provide more information:
v
Stressed Resources tool
v
Connectivity tool
v
Situations tool
8. When the computer (where the monitoring agent is running) has multiple
Network Interface Cards (NICs), the agent might not be bound to the Primary
NIC. The agent might not be able to establish connectivity with the monitoring
server. High CPU usage can result from the agent's frequent attempts to
connect.
a.
To correct this, you might need to set the environment variable
KDEB_INTERFACELIST
=
'!*'
or
KDEB_INTERFACELIST
=
IP_address
, where
IP_address
is the address of the NIC.
b. Make the changes in the associated agent
*ENV
configuration file for
Windows, or the
*.ini
configuration file for UNIX or Linux.
What to do next
For more information on actions that relate to these diagnostics, see the problem
resolution tasks.
Resolving situation problems - diagnostic actions
You can resolve situation problems by running the ITMSUPER tool. Also, you can
examine the situation definition and formula in the agent-specific
.lg0
file.
Procedure
Diagnostic actions
1. Run the Situation Test ITMSUPER tool.
2. Find out which situations have been deployed to the monitoring agent.
3. Open the agent-specific .lg0 file to view a list of situations started for that
agent.
v install_dir \TMAITM6\logs
v install_dir /logs
4. Examine the situation definition and formula.
5.
Does the situation contain any wildcard
*
characters against UTF8 columns?
v
Yes: See “Resolving situation problems - corrective actions” on page 31.
6. Switch between situations to see which one is causing the high CPU.
30
IBM Tivoli Monitoring: Troubleshooting Guide