Chapter 2 Objectives: Structured Troubleshooting

Chapter 2:
Structured Troubleshooting
CCNP TSHOOT: Maintaining and Troubleshooting IP Networks
Course v7 Chapter #
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 1
Chapter 2 Objectives
 Meaning of structured troubleshooting method and
procedure
 The subprocesses of structured troubleshooting, the actions
taken within each subprocess, and how and when you
move from one to another progressively
 Troubleshooting example utilizing the structured
troubleshooting method and procedures
Chapter #
© 2010, Cisco Systems, Inc. All rights reserved. 1

Presentation_ID.scr
Troubleshooting Method and Procedure
 The generic troubleshooting process consists of the
following tasks (subprocesses):
1. Defining the problem
2. Gathering information
3. Analyzing the information
4. Eliminating potential causes
5. Proposing a hypothesis (likely cause of the problem)
6. Testing and verifying validity of the proposed hypothesis
7. Solving the problem and documenting the work
Chapter #
Defining the Problem
All troubleshooting tasks begin with defining the problem.

However, what triggers a troubleshooting exercise is a failure
experienced by someone who reports it to the support group.
Chapter #

Presentation_ID.scr
Gathering Information
Before gathering information, you should select your initial troubleshooting

method and develop an information-gathering plan. As part of this plan,
you need to identify what the targets are for the information-gathering
process.
Chapter #
Analyzing the Information
During the analysis of the gathered information, you are typically trying to
determine two things: What is happening on the network and what should
be happening. If you discover differences between these two, you can
collect clues for what is wrong or at least a direction to take for further
information gathering.
Chapter #

Presentation_ID.scr
Eliminating Potential Causes
Analyzing the gathered information while considering and incorporating

existing information, such as network baseline and documentation, helps
you eliminate many potential causes.
You must make note of the important influence that your assumptions
have in eliminating the potential causes. Assumptions may or may not be
true. If you end up with conflicting conclusions or scenarios that make no
sense, you might have to reevaluate your assumptions by gathering more
information and analyzing the new information accordingly.
Chapter #
Proposing a Hypothesis
The proposed hypothesis leads us to
the next stage of the structured
troubleshooting process: testing the
hypothesis.
If you decide to escalate the problem,

ask yourself whether this ends your
involvement in the process.
If you cannot solve the problem, but it

is too urgent to wait for the problem
to be solved through an escalation,
you might need to come up with a
workaround.
Chapter #

Presentation_ID.scr
Testing and Verifying Validity of the Proposed
Hypothesis
Usually, implementing a possible
solution involves making changes
to the network. Therefore, if your
organization has defined
procedures for regular network
maintenance, you must follow
your organization’s regular
change procedures.
If the problem is not solved, you

need to have a way to undo your
changes and revert to the original
situation.
Chapter #
Solving the Problem and Documenting the

Work
You will have to document all changes to make sure that the network
documentation still accurately describes the current state of the network.
Your troubleshooting job is not complete until you communicate that the
problem has been solved. At a minimum, you will have to communicate
back to the original user that reported the problem; if you have involved
others as part of an escalation process, however, you should
communicate with them, too.
Chapter #

Presentation_ID.scr
Chapter 2 Summary
 The generic troubleshooting process consists of the
following tasks (subprocesses):
1. Defining the problem
2. Gathering information
3. Analyzing the information
4. Eliminating potential causes
5. Proposing a hypothesis (likely cause of the problem)
6. Testing and verifying validity of the proposed hypothesis
7. Solving the problem and documenting the work
Chapter #
Chapter 2 Discussion
 Troubleshooting Example Based on the Structured
Method and Procedures
Chapter #

Presentation_ID.scr
Chapter #
Acknowledgment
• Some of the texts and images are from Troubleshooting and Maintaining Cisco
IP Networks (TSHOOT) Foundation Learning Guide by Amir Ranjbar
(158720455X)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva
Chapter #

Presentation_ID.scr

Chapter 2 Objectives: Structured Troubleshooting

Uploaded by

Copyright:

Available Formats

Chapter 2 Objectives: Structured Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 2 Objectives: Structured Troubleshooting

Uploaded by

Copyright:

Available Formats

Chapter 2:

CCNP TSHOOT: Maintaining and Troubleshooting IP Networks

© 2010, Cisco Systems, Inc. All rights reserved. 1

Defining the Problem

All troubleshooting tasks begin with defining the problem.

© 2010, Cisco Systems, Inc. All rights reserved. 2

Before gathering information, you should select your initial troubleshooting

Analyzing the Information

© 2010, Cisco Systems, Inc. All rights reserved. 3

Analyzing the gathered information while considering and incorporating

If you decide to escalate the problem,

If you cannot solve the problem, but it

© 2010, Cisco Systems, Inc. All rights reserved. 4

If the problem is not solved, you

Solving the Problem and Documenting the

© 2010, Cisco Systems, Inc. All rights reserved. 5

© 2010, Cisco Systems, Inc. All rights reserved. 6

© 2010, Cisco Systems, Inc. All rights reserved. 7

You might also like