Collecting Data: Read First for the ITM Warehouse Proxy Agent (WPA) V6

Resolving The Problem

Collecting data early, even before opening the PMR, helps IBM® Support quickly determine if:
Symptoms match known problems (rediscovery).
There is a non-defect problem that can be identified and resolved.
There is a defect that identifies a workaround to reduce severity.
Locating root cause can speed development of a code fix.

Collecting Data: Readme first table of contents:

	Gathering general information
	Gathering component specific information
	ITM Collector Tool
	Manually gathering data
	Additional information to collect for the Windows Agent
	Submitting information to IBM Support

Gathering general information

You can use the IBM Support Assistant (ISA) to capture general WPA information. Alternatively you can manually collect general information from the environment. Entering general information into an electronically-opened PMR (through SR) prevents having to manually provide that info to Level 1 support on the phone.

The WPA is enabled with default RAS1 (Reliability, Accessibility and Serviceability) settings. If you do not know what the problem is, then collecting the general WPA logs and configuration files is should help to further isolate the problem. For these instances see the section on manually collecting information and send the data with the default trace settings.

Gathering component specific information

Several components can be involved in a problem with the WPA. This section will detail the common component areas and some trace settings that can be helpful in isolating issues related to them. These trace settings are suggested but will not isolate every problem scenario. Logs with default trace settings can still be provided to IBM Support, and the logs can be reviewed to help suggest additional trace settings.

ITM Tivoli Warehouse Proxy Agent V6 and Related Components

WPA-SIDE (a.k.a. "SERVER-SIDE") KHDX TRACING Update the WPA configuration file to set RAS1 tracing: Windows - <install path>\tmaitm6\KHDENV UNIX/Linux - <install path>/config/hd.ini Default tracing level: KBB_RAS1=ERROR The suggested trace level for diagnosing WPA export-specific problems: KBB_RAS1=ERROR (UNIT:khdx ER,ST) For intense tracing use (UNIT:khd ALL) To see what socket is registered with the hub TEMS for a WPA: On the WPA: (UNIT:khdxrpcr ST) To see which WPA an RTEMS selects for its agents: (UNIT:kpxrwhpx ST) On the hub TEMS, use the kdclbad command utility to print out the Global Location Broker to see all WPA socket registrations (type lower case "L" in the interactive prompt) To disable INSERTs into the WAREHOUSELOG table, KHD_WHLOG_ENABLE=N can be set in the WPA's configuration file. To then get the same information printed to STDOUT in the WPA's RAS1 log, use the following RAS1 debug UNIT in the config file: KBB_RAS1=ERROR (UNIT:khdxdbex OUT) For communication problems or to trace the RPC layer, use KBS_DEBUG=Y in WPA config file Restart the WPA** AGENT-SIDE (a.k.a. "CLIENT-SIDE") KHDX TRACING Set the following variable in the Agent's config file (requires agent restart) to enable export of attribute group data at each collection interval expiration instead of at the defined "Warehouse Interval" expiration: KHD_EXPORT_DEBUG=Y The suggested trace level for diagnosing export-specific problems when TEMA is collection location: KBB_RAS1=ERROR (UNIT:kraahbin ST) (UNIT:khdx ER ST) The suggested trace level for diagnosing export-specific problems when TEMS is collection location: KBB_RAS1=ERROR (UNIT:khdx ST ER)(UNIT:kfasphst ST)(UNIT:kpxrwhpx ST)(UNIT:kpxhsloc ALL)(UNIT:krabhsco ALL) NOTE: "kraahbin" (TEMA) and "kfasphst" (TEMS) are added to show how many rows are written to the binary files during each collection interval. To trace networking or routing specific problems between Agent and the WPA: KBB_RAS1=ERROR (UNIT:khdx ER,ST)(UNIT:khdxdacl ALL)(UNIT:khdxrpca ALL) To trace problems with the binary file pruning mechanism on the TEMA: KBB_RAS1=ERROR (UNIT:khdshist ST,DET) To show which WPA data exports are sent to from the TEMA's perspective: KBB_RAS1=ERROR (UNIT:khdxdacl ALL)

** The above RAS1 tracing can be set dynamically (without WPA restart) via the WPA's service console. Ina browser, goto http://<wpa_host>:1920 and select the "* IBM Tivoli Monitoring Service Console" hyperlink under the "Service Point: <user>.<hostname>_hd" heading. You will need to enter a valid username/password on the WPA system to log in. Once in, to enable a particular RAS1 setting enter it after the "ras1 set" command string in the field at the bottom and then hit <enter>, i.e.:

ras1 set (UNIT:khdx ST,ER)

You can then use the "ras1 list" command to verify that it was set correctly.
To then dynamically disable that same trace unit use:

ras1 set (UNIT:khdx ANY)

Once the component traces have been set and the components have been restarted, recreate the problem and collect the logs.

Collector Tool

As of ITM V6.2 a new tool called pdcollect exists to aid in collecting PD information. Instructions for using pdcollect in a V6.1 ENV can be found from the technote. pdcollect is available for Linux, UNIX, Windows. Once the you have collected the PD information with pdcollect, upload it to IBM using the steps provided in this URL: Exchanging information with IBM Technical Support

Manually gathering general information

This section details how to manually collect information from the on which the
WPA is installed:

From a command prompt on a Unix/Linux WPA, collect:
# cinfo -i > /tmp/cinfo_i.out
# cinfo -t > /tmp/cinfo_t.out

From a command prompt on a Windows WPA, collect:
C:\> kincinfo -i > \cinfo_i.out
C:\> kincinfo -t > \cinfo_t.out

Collect the WPA logs:
$CANDLEHOME/logs/*hd_*
$CANDLEHOME/config/*hd* (%CANDLE_HOME%\tmaitm6\KHDENV on Windows)

Additional information for the WPA Agent

Operating system and level
/etc/SuSE-release (for SuSE Linux)
/etc/system-release (for Redhat)
winver (for Windows)

Hostname and IP address
netstat -a
Firewall configuration information (if applicable)
Operating system error log messages (if applicable)
/var/adm/messages (if applicable)

Submitting information to IBM Support

After a PMR is open, you can submit diagnostic MustGather data to IBM.
See this URL Exchanging information with IBM Technical Support for methods to submit the information, including FTP, using SR, and ISA.

Related information

Troubleshooting information for supported versions of Tivoli Monitoring v6 is in the Problem Determination Guides, available at the IBM Tivoli Monitoring v6 Information Center. The IBM Tivoli Monitoring Version 6.3 Information Center is now available. You can access this information center at:
http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3fp2/welcome.htm.