IBM Tivoli Monitoring 6.1.0问题排查指南

需积分: 9 81 浏览量更新于2024-07-23 收藏 3.9MB PDF 举报

"ITM故障排查" 本文档是IBM Tivoli Monitoring的问题确定指南，版本6.1.0，更新于2007年5月，编号GC32-9458-00。该指南适用于IBM Tivoli Monitoring产品（产品编号5724-C04）的6.1.0版本及其后续的所有发布和修改，直到新的版本中有其他指示。在使用此信息和支持的产品之前，请阅读附录F“通知”中的内容，这是位于第315页的重要信息。本版指南旨在帮助用户解决IBM Tivoli Monitoring在操作过程中遇到的问题，提高系统的稳定性和可用性。 IBM Tivoli Monitoring是一款全面的企业级监控解决方案，用于实时监控和诊断IT基础架构中的问题，包括服务器、网络设备、应用和服务。它提供了深入的性能分析、自动故障识别和报告功能，帮助管理员预防和快速解决可能出现的技术问题。本指南的目标读者是那些负责IBM Tivoli Monitoring系统运维的专业人员，包括系统管理员、IT运营团队成员以及对故障排查有需求的技术支持人员。通过阅读本指南，他们可以学习如何有效地定位和解决监控系统中出现的各种问题。除了本指南，IBM还提供了一系列相关的出版物，包括用户手册、参考指南和技术文档，这些都可以在线访问。读者可以通过在线资源获取最新的术语解释和出版物，也可以选择订购纸质版的文档。关于访问性，IBM关注所有用户的需求，包括残障人士。指南可能包含无障碍功能，如高对比度模式或屏幕阅读器兼容性，以确保所有用户都能无障碍地获取信息。 IBM Tivoli Monitoring问题确定指南是一份重要的技术资料，对于管理和维护Tivoli Monitoring系统的人来说，它是故障排查和系统优化不可或缺的工具。通过深入理解和应用指南中的知识，IT专业人员可以更高效地管理其IT环境，确保服务的连续性和稳定性。

v Application information:

– Version number and patch level

– Sample application data file (if monitoring a file)

v Operating system version number and patch level

v Messages and other information displayed on the screen

v Version number of the following members of the monitoring environment:

– IBM Tivoli Monitoring. Also provide the patch level, if available.

– Monitoring Agent version number

– Tivoli Enterprise Portal. Select About Tivoli Enterprise Portal ... from the

Help menu.

Note:

The version number of the Tivoli Enterprise Portal and the Tivoli

Enterprise Portal server must always be synchronized.

v Screen captures of incorrect output, if any.

v If the systems stops on Windows, collect the drwtsn32.log and user.dmp files if

available. The drwtsn32.log and user.dmp files are located in

\Documents and Settings\All Users\Documents\DrWatson

1. Enter the following command at the command prompt to enable Dr. Watson

as default debugger:

drwtsn32 –i

2. Enter the following command at the command prompt to open the Dr.

Watson configuration dialog:

drwtsn32

3. Set the Crash dump Type to FULL.

4. Remove the check from the Dump Symbol Table box.

5. Place a check in the Dump all Thread Contexts box.

6. Place a check in the Create Crash Dump File box.

If the system stops on UNIX-based systems, collect the core dump file from

install_home/bin directory, where install_home is the directory path where you

installed the monitoring agent.

Problem classification

The first task in problem determination is to determine the origin of the problem,

or which component or function is experiencing a problem. To assist you in

determining the origin of the problem, collect documentation at the time of the

error. You might experience problems with IBM Tivoli Monitoring in the following

areas:

v Installation

v Upgrading

v Configuration

v Connectivity

v Tivoli Enterprise Portal

v Tivoli Enterprise Portal Server

v Tivoli Enterprise Monitoring Server

v Tivoli Enterprise Monitoring Agent deployment

v Databases

v Tivoli Data Warehouse

2 IBM Tivoli Monitoring: Problem Determination Guide

v Universal Agent

v IBM Tivoli Enterprise Console

Finding release notes

You can find release note information online by viewing IBM Technotes. Technotes

replace the Release Notes manual for this product. Technotes are short documents

that cover a single topic. You can search the Technotes collection for common

problems and solutions, as well as known limitations and workarounds. Technotes

are continuously updated to provide current product information.

The following two procedures describe how to view Technotes and subscribe to

have future Technotes e-mailed to you. Alternatively, you can watch demos of

these procedures at the following Web site:

http://www-306.ibm.com/software/support/sitetours.html

Viewing Technotes

Perform the following actions to access Technotes for this product:

1. Launch the IBM Software Support Web site: http://www.ibm.com/software/

support

2. In the Products A - Z field, select the product name to open the

product-specific support site.

For this product, select I > IBM Tivoli Monitoring..

3. In the Self help field, click Technotes.

4. Scroll through the Technotes, or you can optionally type a search term to refine

the displayed data.

For tips on refining your search, click Search tips.

Creating an e-mail subscription to Technotes

You can subscribe to e-mail notification about product tips and newly published

fixes through My support, a personalized portal that enables you to:

v Specify the products for which you want to receive notifications

v Choose from flashes, downloads, and Technotes

v Receive an e-mail update in your inbox

Perform

the following actions to subscribe to My support e-mails:

1. Launch an IBM support Web site such as the following site:

http://www.ibm.com/support/us/

2. Click My support in the upper-right corner of the page.

3. If you have not yet registered, click register in the upper-right corner of the

support page to create your user ID and password.

4. Sign in to My support.

5. On the My support page, click Edit profile.

6. Select a product family and continue setting your preferences to specify the

information you want in your e-mails.

7. Click Submit.

Chapter 1. Introduction to problem determination 3

Chapter 2. Diagnostic tools

IBM Tivoli Monitoring provides several tools for diagnosing problems. The

primary diagnostic tool of IBM Tivoli Monitoring is logging. Logging refers to the

text messages and trace data generated by the software. Messages and trace data

are sent to an output destination, such as a console screen or a file.

Trace logging

Trace logs capture information about the operating environment when component

software fails to operate as intended. The principal log type is the reliability,

availability, and serviceability (RAS) trace log. RAS logs are in the English

language only. The RAS trace log mechanism is available on the Tivoli Enterprise

Monitoring Server, the Tivoli Enterprise Portal Server, and the monitoring agent.

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

IBM Software Support uses the information captured by trace logs to trace a

problem to its source or to determine why an error occurred. The default

configuration for tracing, such as whether tracing is enabled or disabled and trace

level, depends on the source of the tracing. You can choose how many files to keep

when the log rolls. If you cannot find the log files you need, restart the system and

try again. This section includes instructions for configuring trace logging.

Table 1 lists the location of the log files directories.

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

Component Windows UNIX-based systems

Tivoli Enterprise

Portal Server

install_dir\logs 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. See Appendix A, “IBM

Tivoli Monitoring product codes,” on page 111 for

a list of product codes.

timestamp

A decimal representation of the time at which the

process was started.

Tivoli Enterprise

Portal browser

client

C:\Documents and Settings\

Administrator\

Application Data\

Java\Deployment\

log\plugin142.trace

None.

剩余337页未读，继续阅读

LunaSeaKYO

粉丝: 0
资源: 5

IBM Tivoli Monitoring 6.1.0问题排查指南

Longley-Rice（ITM）模型软件_ITM_Longley-Rice

STM32 ITM 动态调试

itm不规则地面模型

ITM 和STM trace的區別

ITM filter

[{'max_xsrz_itm': 418}],取出里面的数值的django语句

for(let item of timeArray){ for(let itm of item.busyTime){ const start = toMinutes(itm.busyStart); const end = toMinutes(itm.busyEnd); if (givenEnd <= start || givenStart >= end) { // no overlap continue; } else { // overlap return true; } } }改写代码，return true改成结束最外层循环

最新资源