01.12.2012 Views

Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1.1 <strong>Problem</strong> determ<strong>in</strong>ation process<br />

For the purposes of this redbook, a problem can be considered as any situation<br />

where someth<strong>in</strong>g that was previously work<strong>in</strong>g correctly is now not work<strong>in</strong>g as<br />

expected.<br />

1.1.1 Def<strong>in</strong><strong>in</strong>g the problem<br />

The first step <strong>in</strong> problem resolution is to def<strong>in</strong>e the problem. It is important that<br />

the person try<strong>in</strong>g to solve the problem underst<strong>and</strong>s exactly what the users of the<br />

system perceive the problem to be. A clear def<strong>in</strong>ition of the problem is useful <strong>in</strong><br />

two ways. First of all, it can give you a h<strong>in</strong>t as to the cause of the problem.<br />

Secondly, it is much easier to demonstrate to the users that the problem has<br />

been solved if you know how the problem is seen from their po<strong>in</strong>t of view.<br />

Take, for example, the situation where a user is unable to pr<strong>in</strong>t a document. The<br />

problem may be due to the /var file system runn<strong>in</strong>g out of space. The person<br />

solv<strong>in</strong>g the problem may fix this <strong>and</strong> demonstrate that the problem has been<br />

fixed by us<strong>in</strong>g the df comm<strong>and</strong> to show that the /var file system is no longer full.<br />

This example can also be used to illustrate another difficulty with problem<br />

determ<strong>in</strong>ation. <strong>Problem</strong>s can be hidden by other problems. When you fix the<br />

most visible problem, another one may come to light. The problems that are<br />

unearthed dur<strong>in</strong>g the problem determ<strong>in</strong>ation process may be related to the one<br />

that was <strong>in</strong>itially reported, <strong>in</strong> other words, multiple problems with the same<br />

symptoms. In some cases, you may discover problems that are completely<br />

unrelated to the one that was <strong>in</strong>itially reported.<br />

In the example described above, simply <strong>in</strong>creas<strong>in</strong>g the amount of free space <strong>in</strong><br />

the /var file system may not solve the problem be<strong>in</strong>g experienced by the user.<br />

The pr<strong>in</strong>t<strong>in</strong>g problem may turn out to be a cable problem, a problem with the<br />

pr<strong>in</strong>ter, or perhaps a failure of the lpd daemon. This is why underst<strong>and</strong><strong>in</strong>g the<br />

problem from the users perspective is so important. In this example, a better way<br />

of prov<strong>in</strong>g that the problem has been resolved is to get the user to pr<strong>in</strong>t their<br />

document.<br />

1.1.2 Gather<strong>in</strong>g <strong>in</strong>formation from the user<br />

The best way of underst<strong>and</strong><strong>in</strong>g the problem from the users’ perspective is to ask<br />

them questions. From their perception of the situation, you can deduce if <strong>in</strong> fact<br />

they have a problem, <strong>and</strong> the time scale <strong>in</strong> which they expect it to be resolved.<br />

Their expectations may be beyond the scope of the mach<strong>in</strong>e or the application it<br />

is runn<strong>in</strong>g.<br />

Chapter 1. <strong>Problem</strong> determ<strong>in</strong>ation <strong>in</strong>troduction 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!