Unit 5 Assignment: Troubleshooting an Infrastructure Service
No matter how good the operating system is there are going to be times when the services that the infrastructure depends upon like Networking, DHCP, DNS. Apache web server and the other vital services just stop working for various reasons. It these times that administrators want to pull their hair out.
This course has asked you to do some research on the how these vital services work and to make sure they continue to work every day. This assignment will look at when these things do not work effectively and to discover how resolve these issues.
Write a one-page report in the form of a handout in which you describe the steps that you would use to troubleshoot your service. You may need to search the public web using a search engine like Google or Bing to find description of the commands. Cite any sources you use in APA format; this includes sources for any screenshots that are not your own.
Troubleshooting Principles Troubleshooting is the process that leads to the diagnosis and, if possible, resolution of a problem. Troubleshooting is usually triggered when a person reports a problem. In modern and sophisticated environments that deploy proactive network monitoring tools and techniques, a failure/problem may be discovered and even fixed/resolved before end users notice or business applications get affected by it. Some people say that a problem does not exist until it is noticed, perceived as a problem, and reported as a problem. This implies that you need to differentiate between a problem, as experienced by the user, and the actual cause of that problem. The time a problem is reported is not necessarily the same time at which the event causing the problem happened. Also, the reporting user generally equates the problem to the symptoms, whereas the troubleshooter often equates the problem to the root cause. For example, if the Internet connection fails on Saturday in a small company, it is usually not a problem, but you can be sure that it will turn into a problem on Monday morning if it is not fixed before then. Although this distinction between symptoms and cause of a problem might seem philosophical, you need to be aware of the potential communication issues that might arise from it. Generally, reporting of a problem triggers the troubleshooting process. Troubleshooting starts by defining the problem. The second step is diagnosing the problem, during which information is gathered, the problem definition is refined, and possible causes for the problem are proposed. Eventually, this process should lead to a hypothesis for the root cause of the problem. At this time, possible solutions need to be proposed and evaluated. Next, the best solution is selected and implemented. Figure 1-1 illustrates the main elements of a structured troubleshooting approach and the transition possibilities from one step to the next. Figure ...
Troubleshooting DNS in Linux
Troubleshooting DNS in Linux
Domain Name System errors can prevent a person from navigating websites or access specific applications. One can get DNS errors due to various reasons such as DNS server is not available or the names are configured correctly (Janbeglou, 2010). Troubleshooting the cause of a DNS error can use many methods which can help to identify the cause of the DNS problem. Some basic DNS troubleshooting involves collecting the information created by the DNS problem by investigating ...