Key terms
Make sure you can explain each of these in your own words. The glossary has short definitions.
- Top-down
- bottom-up
- divide and conquer
- ping
- traceroute
- nslookup
- netstat
- log
- baseline
- root cause
- ticket
Self-check questions
Write your answers first, then open the answers to check them.
- List the steps of the CompTIA-style troubleshooting method in order.
- A user can ping 8.8.8.8 but cannot open websites by name. What is the likely fault and how do you confirm it?
- Which tool shows where along a path packets stop?
- A Linux web server is not responding. Name five checks you would do.
- What does an IP address of 169.254.12.5 on a client indicate?
- Why should you change only one thing at a time?
Show answers
- Identify the problem (gather information, reproduce, define the scope).
- Establish a theory of probable cause.
- Test the theory to determine the cause.
- Establish a plan of action and identify its impact.
- Implement the solution (or escalate).
- Verify full system functionality and apply preventive measures.
- Document findings, actions and outcomes.
DNS failure; confirm with
nslookup www.example.comand by changing the DNS server (for example to 8.8.8.8).tracert(Windows) ortraceroute(Linux).Any five, for example:
pingthe server and check its IP settings (ip a).systemctl status apache2to see whether the web service is running.ss -tulpnto check it is listening on port 80/443.sudo ufw statusto check the firewall allows the port.journalctl -u apache2and/var/log/apache2/error.logfor error messages;apache2ctl configtestfor syntax.df -h,free -handtopfor a full disk, low memory or high CPU.nslookup/digto check the name resolves to the right address.
The client failed to get a DHCP address and self-assigned an APIPA address.
So you can tell which change fixed the problem or caused a new one and can easily undo it.
Next: when you are confident with this unit, test yourself with the multiple-choice questions for Unit 9 in the Final Revision section.