Hardware and Network Troubleshooting Flashcards
First step in the troubleshooting methodology; ensure the problem is properly understood
Identify the problem
Part of this troubleshooting methodology means do not confuse symptoms with being the problem
Identify the problem
What are some questions to get to the details of questioning the user?
What were they doing? Exact error message details;
What has changed since things were working properly;
Review relevant logs
Second part of the troubleshooting methodology; can we identify what caused the problem symptoms?
Establish a Theory of Probable Cause
Part of this troubleshooting methodology is to prioritize by likelihood
Establish a Theory of Probable Cause
Part of this troubleshooting methodology is to escalate
Establish a Theory of Probable Cause
Part of this troubleshooting methodology is to research
Establish a Theory of Probable Cause
Third part of the troubleshooting methodology; select the most likely problem cause and determine how to best test the most likely problem cause
Test the theory
As part of this troubleshooting methodology, if you don’t have the tools or ability to test, you can escalate
Test the theory
What are some best practices when testing the theory?
- Change one thing at a time
- Document as you go along
- Determine the root cause
What happens when you are testing the theory and that theory fails?
Establish a new theory, go to your next theory in the sequence, or escalate the problem
Fourth part of the troubleshooting methodology; how are you going to deploy the solution?
Establish a Plan of Action
As part of this troubleshooting methodology, you must prepare a rollback plan
Establish a Plan of Action
As part of this troubleshooting methodology, you’ll want to backup data and configurations
Establish a Plan of Action
As part of this troubleshooting methodology, if you can’t execute the plan, escalate
Establish a Plan of Action
As part of this troubleshooting methodology, you must determine the solution scope - is it just one user, the server, network devices?
Establish a Plan of Action
As part of this troubleshooting methodology, plan solution implementation
Establish a Plan of Action
As part of this troubleshooting methodology, put the solution into motion
Establish a Plan of Action
Fifth part of the troubleshooting methodology; after going through the fix, did it work?
Verify System Functionality
As part of this troubleshooting methodology, one must ask, are affected users happy with the solution?
Verify System Functionality
As part of this troubleshooting methodology, we must ask how we can ensure this problem is not repeated
Verify System Functionality
As part of this troubleshooting methodology, we must monitor the solution over time
Verify System Functionality
As part of this troubleshooting methodology, we might need to contact Subject Matter Experts (SMEs).
Verify System Functionality
As part of this troubleshooting methodology, we must ask if new problems been introduced because of the solution? We’ll need to but preventative measures into effect
Verify System Functionality