Problem determination process

[aruns_s]

Hi Gurus,
Do we have any kind of common problem determination process for RISC boxes?


Many thanks

[Peter Godron · Accepted solution]

Hi,
can you please give us a bit more info. What sort of problem ? Hardware, Software, Network ?

In my opinion, the most basic rules covering investigating all of these are:
1. Research any changes (code changes,network re-config etc)
2. Research error symptoms (ITRC/web search)
3. Start with simplest block ( Physical check of disk, cable disconnected )

[Steven E. Protter]

Shalom,

I usually start with the error message.

I rarely am the first to encounter a problem and often find cutting and pasting directly into google brings guidance.

When something happens with no explanation, I want to know what changed. What did the user do, what patches were installed, what configuration changes were made, what changes to the overall environment in the data center.

There is a very good course at HP education called HP-UX troubleshooting. Its a great way to learn these procedures.

SEP

[A. Clay Stephenson]

In keeping with the quality of your question, I'll answer that I simply use The Force.

One of the best tools that can be used for problem solving (or determining if there even is a problem) is a set of metrics for when the box is running normally.

[Jaime Bolanos Rojas.]

Aruns,

Basically never give up, know where your resources ( to get help ) are, have a contract with HP support and keep a positive attitud,

Regards,

Jaime.

[Peter Godron]

Arun,
quite a few good answers there.

If you question has been asnwered, could you please complete the thread by awarding points to helpful answers and summarising the solution for you.

http://forums1.itrc.hp.com/service/forums/helptips.do?#33 shows how to reward any useful answers given to your questions.