Network Troubleshooting Flashcards
traceroute/tracert
used to trace the route from client to server, etc.
netstat
shows all active connections
-n lists numerically
-b shows executable file
-o shows process id
-a shows all active ports
-r shows routing table
Troubleshooting Methodology Step 1
Identify the Problem
1. Gather information
2. Question users
3. Identify symptoms
4. Determine if anything has changed
5. Duplicate problems if possible
Troubleshooting Methodology Step 2
Establish a Theory of Probable Cause
1. Question the obvious
2. Consider multiple approaches (top to bottom/bottom to top/divide and conquer)
Troubleshooting Methodology Step 3
Test the Theory to Determine the Cause
1. If theory is confirmed, determine next steps
2. If theory is not confirmed, reestablish new theory or escalate
Troubleshooting Methodology Step 4
Establish a plan of action
Troubleshooting Methodology Step 5
Impmlement the solution or escalate as necessary
Troubleshooting Methodology Step 6
Verify full system functionality and if applicable, implement preventative measures
Troubleshooting Methodology Step 7
Document findings, actions, outcomes, and lessons learned
Speed/Bandwidth of cable
Theoretical maximum data rate (size of the pipe)
Throughput
Amount of data transferred in a given timeframe (how much water is flowing through the pipe)
Protocol Analyzer
Gathers frames on the network (or in the air)
Can view traffic patterns, identify unknown traffic, etc.
iperf
used to measure speed and performance - requires server and client
Port Scanners
Used to identify IP addresses and open ports (OS, services, et.c)
NetFlow
Gathers traffic statistics from all traffic flows. Uses probes and collectors to create reports.