IBM Tivoli Monitoring问题确定指南（6.2版）：从数据收集到问题分类

需积分: 9 132 浏览量更新于2024-07-27 收藏 2.08MB PDF 举报

"《IBM Tivoli ITM问题确定指南》（Version 6.2，GC32-9458-01）是一份详尽的文档，专为ITM（Tivoli® IBM Tivoli Monitoring）用户设计，旨在帮助用户诊断和解决在版本6.2（产品编号5724-C04）及后续版本中可能遇到的问题。该指南适用于政府用户，受限于GSA ADP Schedule合同中的规定。第一章“问题确定介绍”涵盖了问题诊断的基本原则和步骤。它强调了问题来源的重要性，包括系统日志、事件记录和用户反馈等，这些都是收集问题数据的关键。收集数据时，可能涉及监控工具的使用，如日志追踪，以获取关于性能瓶颈、异常行为或故障的详细信息。接下来的部分，问题分类被详细阐述，这是确定问题类型和优先级的基础。根据问题的性质和影响范围，可能分为软件错误、硬件故障、配置问题或用户操作不当等类别。指南还指导读者如何查找相关的发布说明，以便了解已知问题和解决方案，以及查看技术提示（Technotes）来获取专业建议和最佳实践。创建Technotes的电子邮件订阅功能也被提及，这样用户可以及时获取最新的技术支持文档和技术更新，进一步提升问题解决效率。第二章“工具”深入介绍了Tivoli Monitoring提供的各种诊断工具，如故障排查工具、性能分析器和报告生成器。这部分内容对于熟悉和优化使用这些工具进行问题定位至关重要，确保能够快速定位问题根源，减少解决问题的时间。《IBM Tivoli ITM问题确定指南》提供了一套完整的流程和资源，旨在帮助IT专业人员有效地识别、分析和解决各种问题，确保系统的稳定运行和高效运维。无论是初次使用者还是经验丰富的运维人员，都能从中获益匪浅。"

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)

Component Windows UNIX-based systems

Tivoli Enterprise

Portal desktop

client

install_dir\CNP\kcjerror.log

install_dir\CNP\kcjras1.log

When launched via Java

™

Web

Start:

%USERPROFILE%\Application Data\

IBM\Java\Deployment\log\

javawsnnnnn.trace

where ’nnnnn’ is a unique,

randomly generated numeric suffix

to support generational logs (i.e.,

the last generated log will not be

overlayed by the most current

execution of Tivoli Enterprise

Portal using Java Web Start. This is

in contrast to the Tivoli Enterprise

Portal Browser client, which has a

fixed name and is overlayed with

each execution cycle.

install_dir/logs/

hostname_PC_timestamp.log

where:

install_dir

Specifies the directory where Tivoli Enterprise

Portal Server was installed.

hostname

Specifies the name of the system hosting the

product.

PC Specifies the product code. cq for the Tivoli

Enterprise Portal Server.

timestamp

A decimal representation of the time at which the

process was started.

When

launched via Java Web Start:

${user.home}/.java/deployment/log/javawsnnnnn.trace

where ’nnnnn’ is a unique, randomly generated numeric

suffix to support generational logs (i.e., the last generated

log will not be overlayed by the most current execution of

Tivoli Enterprise Portal using Java Web Start. This is in

contrast to the Tivoli Enterprise Portal Browser client,

which has a fixed name and is overlayed with each

execution cycle.

Tivoli Enterprise

Monitoring

Server

install_dir\logs\hostname_PC_

HEXtimestamp-nn.log

where:

install_dir

Specifies the directory

where Tivoli Enterprise

Monitoring Server was

installed.

PC Specifies the product code.

ms for Tivoli Enterprise

Monitoring Server

HEXtimestamp

A hexadecimal

representation of the time

at which the process was

started.

nn Represents the circular

sequence in which logs are

rotated. Ranges from 1-5,

by default, though the first

is always retained, since it

includes configuration

parameters.

install_dir/logs/hostname_PC_timestamp.log

where:

install_dir

Specifies the directory where Tivoli Enterprise

Portal Server was installed.

hostname

Specifies the name of the system hosting the

product.

PC Specifies the product code. cq for the Tivoli

Enterprise Portal Server.

timestamp

A decimal representation of the time at which the

process was started.

6 IBM Tivoli Monitoring: Problem Determination Guide

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)

Component Windows UNIX-based systems

Monitoring

agents

install_dir\tmaitm6\logs\

hostname_PC_HEXtimestamp-nn.log

where:

install_dir

Specifies the directory

where monitoring agent

was installed.

PC Specifies the product

codes, for example, um for

Universal Agent or nt for

Windows.

HEXtimestamp

A hexadecimal

representation of the time

at which the process was

started.

nn Represents the circular

sequence in which logs are

rotated. Ranges from 1-5,

by default, though the first

is always retained, since it

includes configuration

parameters.

install_dir/logs/hostname_PC_timestamp.log

where:

install_dir

Specifies the directory where Tivoli Enterprise

Portal Server was installed.

hostname

Specifies the name of the system hosting the

product.

PC Specifies the product code. cq for the Tivoli

Enterprise Portal Server.

timestamp

A decimal representation of the time at which the

process was started.

IBM Tivoli

Warehouse Proxy

agent

install_dir\logs\hostname_PC_

timestamp.log

where

PC Specifies the product code.

hd is the product code for

the IBM Tivoli Warehouse

Proxy agent

Not supported.

IBM Tivoli

Summarization

and Pruning

agent

The Summarization and Pruning Agent uses C-based RAS1 tracing, Java-based RAS1 tracing and

Java-based internal tracing. By default, Summarization and Pruning Agent trace data is written

to a file in the logs subdirectory.

install_dir\logs\hostname_PC_

HEXtimestamp-nn.log

install_dir\logs\hos tname_PC_

ras1java_HEXtimestamp-nn.log

install_dir\logs\hostname_PC_

java_HEXtimestamp-nn.log

install_dir/logs/hostname_PC_

HEXtimestamp-nn.log

install_dir/logs/hostname_PC_ras1java_

HEXtimestamp-nn.log

install_dir/logs/hostname_PC_java_

HEXtimestamp-nn.log

where:

install_dir

Specifies the directory where monitoring agent was installed.

PC Specifies the product codes, for example, sy for IBM Tivoli Summarization and Pruning

agent.

HEXtimestamp

A hexadecimal representation of the time at which the process was started.

nn Represents the circular sequence in which logs are rotated. Ranges from 1-5, by default,

though the first is always retained, since it includes configuration parameters.

Chapter 2. Tools 7

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)

Component Windows UNIX-based systems

IBM Tivoli

Enterprise

Console Event

Forwarder

install_dir\logs\hostname_PC_

HEXtimestamp-nn.log

where:

install_dir

Specifies the directory

where Tivoli Enterprise

Monitoring Server was

installed.

PC Specifies the product code.

ms for Tivoli Enterprise

Monitoring Server

HEXtimestamp

A hexadecimal

representation of the time

at which the process was

started.

nn Represents the circular

sequence in which logs are

rotated. Ranges from 1-5,

by default, though the first

is always retained, since it

includes configuration

parameters.

install_dir/logs/hostname_PC_timestamp.log

install_dir/logs/hostname_PC_HEXtimestamp-nn.log

where:

install_dir

Specifies the directory where Tivoli Enterprise

Portal Server was installed.

hostname

Specifies the name of the system hosting the

product.

PC Specifies the product code. cq for the Tivoli

Enterprise Portal Server.

timestamp

A decimal representation of the time at which the

process was started.

IBM Tivoli

Enterprise

Console Situation

Update

Forwarder

c:\tmp\itmsynch\logs\

synch_trace.log

c:\tmp\itmsynch\logs\

synch_msg.log

/tmp/itmsynch/logs/synch_

trace.log

tmp/itmsynch/logs/synch_

msg.log

Note: IBM Tivoli Enterprise Console Situation Update Forwarder logs are created on the IBM

Tivoli Enterprise Console server.

The log files are managed as follows:

v On Windows, the log file name includes a time stamp in hexadecimal format. By

default, the logs are stored in the installation path for IBM Tivoli Monitoring.

The following is an example of a log file name that includes the time stamp in

hexadecimal format:

ibm-kpmn803v01_cq_472649ef-01.log

v On UNIX-based systems, the log file name includes a time stamp. The

UNIX-based systems RAS1 log files are stored in the /logs directory. The

following is an example of a log files name that includes the time stamp:

f50pa2b_ux_1112097194.log

Note: When you communicate with IBM Software Support, you must capture and

send the RAS1 log that matches any problem occurrence that you report.

Installation log files

The following table lists and describes the log files created during installations.

8 IBM Tivoli Monitoring: Problem Determination Guide

Table 2. Installation log files

Windows UNIX-based systems

v ITM_HOME\InstallITM\Abort<Product_name><date_timestamp>.log

This log is created if an abort occurs for either a first time install or

a modification of previous installation of IBM Tivoli Monitoring.

v ITM_HOME\InstallITM\<Product_name>_<timestamp>.log

This log is created during a normal clean installation.

v ITM_HOME\InstallITM\MOD_<Product_name>timestamp.log

This log is created if you modify an existing product specified with

the PC, or when adding or deleting components.

where:

Product_name

Specifies the product name. IBM Tivoli Monitoring 20050923

1815.log is the log file name for the IBM Tivoli Monitoring

installation CD.

timestamp

A decimal representation of the time at which the process was

started.

$CANDLEHOME/logs/candle_

installation.log

You can find a log for uninstallation on Windows in the root directory where the

product was installed:

Uninstall<PC><date_timestamp>.log

UNIX installer and configuration logs

For tracing and logging java code (that is run on UNIX

systems), this mechanism

enables problem debugging. Two sets of information are created – logs and traces.

Logs (*.log) are globalized and traces (*.trc) are in English. They contain entry and

exit parameters of method and stack traces for exceptions. The amount of

information traced depends on the level of tracing set.

Level name What is logged or traced

LOG_ERR Only exceptions and errors are logged and

traced

LOG_INFO Also log messages are logged and traced -

DEFAULT

DEBUG_MIN Also most important method entries, exits

and trace messages are traced

DEBUG_MID Most of the method entries, exits and trace

messages are traced

DEBUG_MAX All of the method entries, exits and trace

messages are traced

The level can be set in configuration files or by exporting an environment variable

called TRACE_LEVEL with one of the values mentioned above. Configuration of

RAS settings is stored in the following files:

v CH/config/ITMInstallRAS.properties (for installation)

v CH/config/ITMConfigRAS.properties (for configuration)

Chapter 2. Tools 9

Callpoints are the only component that is handled differently, their logs and traces

always go to the directory CH/InstallITM/plugin/executionEvents. The default

location for installation is CH/logs/itm_install.log(.trc) and for configuration it is

CH/logs/itm_config.log(.trc).

To gather all the needed logs and environment information in case of an error, use

the pdcollect tool described in “pdcollect tool” on page 25.

Component Location File name

Install logs/traces CH/logs candle_installation.log

itm_install.log (.trc)

Config logs/traces CH/logs itm_config.log (.trc)

Logs for component startup CH/logs pc.env (lists env variables

passed to the agent)

hostname_pc_ID.log

Callpoint logs/traces CH/InstallITM/plugin/

executionEvents

/logs/timestamp/

install(config)/

plugin_type/pc

callpoint.trc (.log)

*.stderr

*.stdout

Upgrading from Tivoli Distributed Monitoring log file

All upgrade actions performed by the IBM Tivoli Monitoring Upgrade Toolkit are

recorded in a central log with an associated user ID and a time stamp. Upgrade

actions taken outside of the Upgrade Toolkit are not recorded in the log. The

detailed results from running the Upgrade Toolkit are recorded in a log file.

Table 3. Upgrading from Tivoli Distributed Monitoring log file

Windows UNIX-based systems

$DBDIR/AMX/logs/log_tool_

timestamp.log

$DBDIR/AMX/logs/log_tool_

timestamp.log

where:

$DBDIR

The Tivoli Management Environment

Framework environment variable

that specifies the directory where the Object Repository (odb.bdb) is

located.

tool Specifies the IBM Tivoli Monitoring Upgrade Toolkit tool: witmscantmr,

witmassess, or witmupgrade.

timestamp

Specifies a time stamp that includes data and time of execution.

For

example: log_witmscantmr_20050721_15_30_15.log

The log file name displays when the Upgrade Toolkit tool completes the upgrade

operation. Each time a Upgrade Toolkit tool runs, its generates a new log file that

is never reused by any tool. The contents of the log file conform to the Tivoli

Message Standard XML logging format. The following example is an excerpt from

an Upgrade Toolkit tool log file:

<Server Format="IP">YFELDMA1.austin.ibm.com</Server>

10 IBM Tivoli Monitoring: Problem Determination Guide

剩余183页未读，继续阅读

ymm2008520

粉丝: 0
资源: 1

IBM Tivoli Monitoring问题确定指南（6.2版）：从数据收集到问题分类

生成WSN拓扑的GT-ITM压缩包

Cortex-M3 ITM调试：无串口占用的高效跟踪方法

IBM ITM安装配置全指南

ITM install guide

ITM

ITM445

ITM TOTAL LIBERADO.zip_BINARY OPTIONS_ITM TOTAL_Indicator ITM To

gt-itm.tar.gz_gt-itm_itm_things

ITM352_S21_repo:ITM 352

itm_exporter:Prometheus 的 ITM 导出器

最新资源