Unit 10 Flashcards
Actually identify underlying problem—what’s actually causing
symptoms to manifest themselves
* Obtain information from three sources
User experiencing problem
Computer in form of logs and error messages
Personal observation if possible
* Make backup copy to restore if needed
Identify the Problem
Establish list of all probable causes
List all, including those that may seem insignificant or unlikely such as
unplugged cable or device turned off
* Prioritize from most likely to least likely
* If no probable cause can be determined, escalate problem to
higher level
Problem Causes
Consider whether or not you can troubleshoot the issue on
your own, or escalating it to higher authority is called for
* Test theory to determine if it is, indeed, actual cause
* If theory confirmed, move to next step
* If theory disproved, go back to step two or step one, as
needed and repeat
Test the Theory
Can be simple or complex
* Write plan out step by step to determine best course of action
* Identify possible repercussions that problem resolution may
introduce into network
* Identify downtime if required
* Schedule not to impact other users
* May require coordination with other offices or agencies
* Escalate the problem to more senior level if necessar
Establish a Plan of Action
Make one change at a time then test to confirm change has
resolved problem
* If not resolved, reverse change if appropriate and implement
new change
* Consider multiple causes of problem
* Keep record of each change and reversal; include effects
were, if any, on system
Implement a Solution
Sometimes, fix will introduce new issue(s), so test for full
system functionality
* Implement preventative measures so problem does not
reoccur
* If full system functionality has not occurred, go back to step
one and continue to work through troubleshooting
methodology
Verify Functionality
Define problem
Gather information, data and evidence
Identify all issues and events that contributed to problem
Determine root causes
Identify recommendations for eliminating or mitigating the
reoccurrence of problems or events
Implement identified solutions
- Basic Root Cause Analysis
Document findings, actions, and outcomes
* When problem occurs again, information available to
troubleshoot and resolve issue
* Captures history of equipment and users so that perpetual
issues become known and recorded
* Document both positive and negative outcomes
Save time during future troubleshooting
Prevent others from taking same missteps taken
Document the Solution