Introduction to Fault Finding

RN3383-30A

Nokia Siemens Networks

RN33831EN30GLA0

Objectives
After completing this module the participant shall be able to:
Understand the basics how to become a good fault finder.
Understand the process of the fault finding.
Understand how individuals have different ways to approach
troubles.

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting learning model

P
e
r
s
o
n
a
l
c
o
m
f
o
r
t
l
e
v
e
l

UNCONSCIOUSLY ABLE
APPLICATION

CONSCIOUSLY ABLE
PRACTICE

END OF COURSE

CONSCIOUSLY UNABLE
AWARENESS

UNCONSCIOUSLY UNABLE

T I M E

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting learning model (Contd.)

It takes time, hard work and studying to become a professional fault
finder. This module focuses on troubleshooting and gives you
guidelines for finding problems in the system.
This course follows the basic learning model, the goal of which is to
improve your personal comfort level when handling the topic.

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting styles

Tester

Gambler
Thinker

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting styles (Contd.)

In general, a system comprising numerous elements is engineered to perform certain
predefined functions and designed so that failure probability is kept to a minimum.
However, since faults and errors can never be entirely eliminated, we need to
establish ways for correcting faults.
There is not clear-cut answer for how to troubleshoot. Everyone has their own style for
finding faults and solving problems.
The competent troubleshooter uses a variety of styles and knows how to select the
best possible solution, with the help of acquired knowledge, skills, and experience.
In observing troubleshooters at work, you will notice that each one goes about their
business in an individual way. Hence, troubleshooting does not propose a single
solution for faults. Rather, troubleshooters recognize symptoms of a problem and
draw from their past experience with similar problems to find a solution.
But how should you react in a totally new fault situation?
After six years of intensive study, the Universities of Illinois at Urbana, and
Carbondale in the US identified three primary troubleshooter categories:
Gambler
Tester
Thinker
These
categories compriseRN33831EN30GLA0
a variety of methods for solving problems.
6
Nokia Siemens Networks

Gambler

Wanderer
-random search

Risk Taker
-experimental search

Odds maker
-guess the fault

Swapper
-change all

Nokia Siemens Networks

RN33831EN30GLA0

Gambler (Contd.)
Gamblers, for example, generally try to solve problems using a trial and error method.
However, their personal styles are further categorized into four groups:
Wanderer
Risk taker
Odds maker
Swapper
The wanderer relies on chance to find a problem. This style involves walking around
the system and selecting random components to check, in the hope that the
selected component is the faulty one. There is no logical sequence to this method,
and for the most part, it does not succeed.
The risk taker experiments with the system and its components, by reconfiguring and
modifying important system files and testing to see if this corrects the error.
The odds maker assumes the it is always the same elements that cause failure. If
proven wrong, odds makers quickly become wanderers.
As the name implies, the swapper swaps units. Swapping often results in quick
recovery of a fault, yet has the effect of not being entirely sure which unit is faulty
because swappers often replace major components to repair minor faults.
8

Nokia Siemens Networks

RN33831EN30GLA0

Tester

Sensor
-look, listen, touch and smell

Tracer
-follow diagram

Splitter

- divide and conquer

Nokia Siemens Networks

RN33831EN30GLA0

Tester (Contd.)
Testers perform equipment tests and use their senses to locate faults.
Testers are divided into:
Sensor
Tracer
Splitter
Like the name implies, a sensor likes to look, listen, touch, and smell. This
method is useful only if you know what you are looking for. After finding a
faulty component you must then use another style to determine the reason
for the fault.
The tracer generally uses schematic diagrams to trace the faults. Tracers
can have a systematic starting point from which to trace the fault. They
can also start from the symptoms and search backwards to locate the
source of the error. Tracing requires skills, since a tracer with limited skills
could easily miss the right symptoms.
The splitter divides the system into two parts and checks for desired results.
If fault indications persist, the splitter continues to split the faulty part of the
system by dividing it into two parts. This goes on until there is only one
possible component left, the faulty one.
10

Nokia Siemens Networks

RN33831EN30GLA0

Thinker

Reader
-use documents

Recaller
-good memory

Designer
-theoretical knowledge

Analyzer
-think before act

11

Nokia Siemens Networks

RN33831EN30GLA0

Thinker (Contd.)
The thinker is a logical troubleshooter who processes information received from a faulty
system. There are four subcategories of thinkers:
Reader
Recaller
Designer
Analyser
The reader uses service manuals and fault isolation charts to track down and isolate the
problem. Skilled readers know when they need help from other sources the right source of
information.
The recaller draws on past experience and as such is able to make conclusions quickly. A
recaller will not necessarily be a good troubleshooter in the case of a new system problem.
The designer uses theoretical knowledge, such as detailed circuit analysis techniques, to
evaluate the fault. This approach can be very time consuming, since detailed thinking takes a
long time and can also lead to being sidetracked. Designers tend to think that all faults were
born on the designing table. Whereas a field engineer will prove that the system was
operational before the failure, and can then concentrate on the failed component.
Analyzers, having detailed understanding of the system, use their knowledge of the system to
observe the symptoms and eliminate portions of the system in a logical way. Analytical
troubleshooting takes the approach 'always think before you act'.
The style you choose is very personal. Your way of tackling problems may differ from someone
else, and will also depend on your level of knowledge and experience in the subject.
Furthermore, a single style is not effective in every situation. Effective troubleshooters have
developed different styles to handle a variety of problems in real-life situations.
12

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting questions
When analyzing the problem, you might want to ask yourself the
following questions:

When was the problem first reported?

How did the problem become known?
From which geographical area was it first reported?
Are there similar complaints coming from other cells?
Is the problem spreading in the network or is it happening only in one/few
RNCs?
Which types of calls are affected?
Does it happen all the time or occasionally?

13

Nokia Siemens Networks

RN33831EN30GLA0

Troubleshooting questions (Contd.)

This is not a complete list, but can be used as a general guideline.
Your questions will be specific for a given problem and your network
definitions.
Having compiled enough information, analyze it. You can use the
following tips as a guideline:

14

Describe in clear terms what could be and is not the problem.

Think of possible sources for the problem.
Verify the possible causes and eliminate non-probable ones.
Check your alternatives and risks and think about what you can do.
Make sure that your plan will not aggravate the situation further.
Prioritize your plan of action and proceed with the available tools.

Nokia Siemens Networks

RN33831EN30GLA0

Brainstorming
What comes up in your mind when you read the questions?
Collect everything together at the board.
What kind of
documents could
help me in
troubleshooting?

What kind of
alarms could help
me in
troubleshooting?

15

Nokia Siemens Networks

RN33831EN30GLA0

Which hard- and

software could help
me in
troubleshooting?

Which people could

help me in
troubleshooting?

Brainstorming (Contd.)

Examples:
Useful documents:
NED
...

People who could help:

colleague
...

Technical tools:
Flexi Platform tools
...

Alarms:
fsclish Alarms
...

16

Nokia Siemens Networks

RN33831EN30GLA0