How to troubleshoot problems in OMEGAMON for Storage

Use this sequential list of questions to troubleshoot issues with OMEGAMON® for Storage. These questions can help you determine the source of the issues and identify the required solutions.

1. Does the problem seem to be caused by or related to the monitoring agent?

2. When does the problem occur or how does the problem occur?

3. Can trace logs reveal details about the problem?

4. Can more focused trace logs reveal more details about the problem?

5. Is there documentation for the problem that the logs reveal?

6. Is the problem solved?

1. Does the problem seem to be caused by or related to the monitoring agent?

You can avoid a basic problem with OMEGAMON for Storage when you understand the basic product architecture.

The OMEGAMON for Storage monitoring agent must report to a local Tivoli® Enterprise Monitoring Server that is installed and configured in the same z/OS® address space.

The local server for each agent must report to a hub server. The hub server can be running on any supported system. If located in a z/OS system, the hub server can also act as the local server for a specific monitoring agent.

Your answer:	Next steps:
No	Refer to IBM Tivoli Monitoring Troubleshooting Guide. This document helps you resolve problems beyond a specific monitoring agent, such as problems with the Tivoli Enterprise Portal and problems with historical reporting.

Do not worry if you cannot answer this question with certainty at this stage. Later in this process, you generate trace logs that can pinpoint the source of a problem.

2. When does the problem occur or how does the problem occur?

In this step, you will find references to the documentation that might help you find a solution.

Problem area:	Refer to: *
Install, configure agent	Troubleshooting installation and configuration *
Data collection	Troubleshooting data collection * Tips regarding the collection of diagnostic data
Performance issues	Troubleshooting performance issues *
Error conditions	Troubleshooting error conditions
Specific product features	Troubleshooting specific product features * Product features include Dataset Attribute Database.

* If the references in this step do not provide solutions to your problem, go to Step 3. Can trace logs reveal details about the problem?.

3. Can trace logs reveal details about the problem?

Trace logs frequently reveal the source of a problem. You can check specific locations to trace the logs.

Your answer:	Next steps:
No	If you are certain that trace logs cannot help you, go to Step 6. Is the problem solved?.
Yes	Read about logging in Sources of troubleshooting data for OMEGAMON for Storage . Set up trace logs for the affected component. Also see Chapter 1, General troubleshooting for the OMEGAMON Monitoring Agent on z/OS , for information on these topics: Locations of IBM Tivoli Monitoring trace logs. Locations of trace logs for a specific monitoring agent. Setting up RAS1 tracing, interpreting those logs, and sending logs to IBM Software Support. Setting up OMEGAMON for Storage debugging logs, interpreting those logs, and sending logs to IBM Software Support. Note: The unique utilities in OMEGAMON for Storage, such as the Storage Toolkit and Dataset Attribute Database, log their messages to the Tivoli Enterprise Portal log. Consult the Tivoli Enterprise Portal log when you are troubleshooting these utilities.

Your answer:

Next steps:

If you are certain that trace logs cannot help you, go to Step 6. Is the problem solved?.

Yes

Read about logging in Sources of troubleshooting data for OMEGAMON for Storage . Set up trace logs for the affected component. Also see Chapter 1, General troubleshooting for the OMEGAMON Monitoring Agent on z/OS , for information on these topics:

Locations of IBM Tivoli Monitoring trace logs.
Locations of trace logs for a specific monitoring agent.
Setting up RAS1 tracing, interpreting those logs, and sending logs to IBM Software Support.
Setting up OMEGAMON for Storage debugging logs, interpreting those logs, and sending logs to IBM Software Support.

Note: The unique utilities in OMEGAMON for Storage, such as the Storage Toolkit and Dataset Attribute Database, log their messages to the Tivoli Enterprise Portal log. Consult the Tivoli Enterprise Portal log when you are troubleshooting these utilities.

Note: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade performance of the monitoring agent. You must restore RAS1 tracing to the minimal KBB_RAS1=ERROR setting after problem diagnosis is completed.

4. Can more focused trace logs reveal more details about the problem?

When the previous steps do not help, you might want to check on more focused trace logs to troubleshoot your problem.

Your answer:	Next steps:
No	Go to Step 6. Is the problem solved?
Yes	Define a different type of trace logging, using the methods that are referenced in Step 3. Can trace logs reveal details about the problem? Note: See the troubleshooting tips in Tips regarding the collection of diagnostic data, as needed, to ensure successful capture of diagnostic data.

5. Is there documentation for the problem that the logs reveal?

The trace logs might provide helpful key words regarding your problem, including unique message numbers.

Use key words regarding your problem to search in the following sources:

Troubleshooting Guide for the monitoring agent
IBM Tivoli Monitoring Troubleshooting Guide, GC32-9458
RETAIN database

Your answer:	Next steps:
No	Go to Step 6. Is the problem solved?
Yes	Follow the instructions that are documented for the problem. Then, go to Step 6. Is the problem solved?

6. Is the problem solved?

If your problem is still not resolved, it is a good idea to contact IBM Software Support.

Your answer:	Next steps:
No	Compile information about the problem and contact IBM Software Support. See Capturing z/OS logs to send to IBM Software Support.
Yes	(No further action is required.)