HP NonStop G-Series - Manual (Page 416)

Problem Solving Techniques
Guardian User’s Guide — 425266-001
A- 6
Task 4: Focus on Prevention
Task 3.2: Provide Documentation
If you decide to escalate the problem, you might be required to document the problem
by providing:
•
A problem identification number
•
A problem classification
•
A complete description and history of the problem
•
Diagnostic information such as copies of the event log, results of memory dumps,
and so on
You might also have procedures at your site for logging problems. If you have a shift
log or problem log, this is the appropriate time for making entries in such a log.
Task 4: Focus on Prevention
Solving problems that occur with your system can be exciting because it is active and
stimulating. Preventing problems is often less dramatic. But in the end, prevention is
more productive than solving problems. Of course, the more work you do to prevent
problems before they arise, the fewer problems will occur at potentially critical times.
These questions provide a framework for your problem-prevention efforts:
•
Why did this problem occur? What was the root cause? Were there any contributing
causes?
•
How serious was the problem?
•
What is the likelihood that it will occur again?
•
Would it be possible to eliminate the causes of this problem?
•
Would it be possible to reduce the likelihood that this problem will occur in the
future?
•
Could automation tools be used to detect and respond to preliminary symptoms of a
problem such as this?
•
Can anything be done now to minimize the damage that would result from a
reoccurrence of this problem?
•
Can the problem resolution process be improved in any way?