5. Network Troubleshooting Flashcards
The first step of troubleshooting; involves gathering facts and identifying what’s wrong.
Identify the Problem
Ask for logs, observe behavior, or check device status to understand the issue.
Gather Information
Speak with users to understand when and how the problem occurred.
Question Users
Look for commonalities across affected systems—errors, slowness, disconnects.
Identify Symptoms
Check if new software, updates, changes, or configurations triggered the issue.
Determine if Anything Has Changed
Attempt to recreate the issue to better understand and observe it.
Duplicate the Problem
Tackle one issue at a time rather than combining them—simplifies troubleshooting.
Approach Multiple Problems Individually
Use logic to guess the most likely root cause of the issue.
Establish a Theory of Probable Cause
Look for obvious causes before diving deep.
Question the Obvious
Start at one end of the OSI model and work your way through each layer.
Top-to-Bottom / Bottom-to-Top
Pick a midpoint in the OSI model and work toward both ends to isolate the issue.
Divide and Conquer
Run tests or replace components to validate the cause of the problem.
Test the Theory
If your theory is confirmed, create a strategy to resolve the issue.
Determine Next Steps to Resolve Problem
If your theory is wrong, either adjust your theory or escalate the issue to a higher tier.
Establish a New Theory or Escalate
Develop a fix and consider what impact it might have on the system or users.
Establish a Plan of Action
Apply the fix, or escalate if it’s outside your authority or skill set.
Implement the Solution or Escalate
Check that the fix worked, and confirm everything is running smoothly.
Verify Full System Functionality
Add configurations, alerts, or processes to prevent the issue from returning.
Implement Preventive Measures
Record everything you did, what worked, and what didn’t—used for future reference and training.
Document Findings, Actions, Outcomes, and Lessons Learned
You can’t fix what you don’t understand—this first step includes gathering all relevant details, asking questions, and confirming what’s broken.
Identify the Problem
This means pulling logs, checking error messages, examining topology maps, and reviewing system status.
Gather Information
Users can offer insight into what happened and when—crucial for timeline reconstruction.
Question Users
Recognizing patterns across systems helps isolate the issue—slow speeds, app crashes, dropped connections are all examples.
Identify Symptoms
Often the root of issues—config updates, hardware changes, or environmental factors may have triggered the problem.
Determine if Anything Has Changed