This article covers CST-111 Week 3 Topic 3 DQ 2: Network Troubleshooting 101
Comprehensive Essay Overview on Network Troubleshooting 101
Network Troubleshooting 101
One of the most frequent IT-related issues we encounter deals with connectivity. “I can’t get to the Web,” “The Internet is down,” and “It doesn’t work” are far more complicated than you think.
In general, networking issues fall into one of four categories:
- Problem with the computer network interface
- Problem with the local network(Comprehensive Essay Overview on Network Troubleshooting 101)
- Problem between the local network and the rest of the web
- Problem with the target resource. (website, server, application)
Research network troubleshooting as it relates to each of these categories of problems and how they may be resolved.
Create a flowchart that illustrates how to navigate the troubleshooting process to most effectively solve the problems.
Be sure to cite your research using APA guidelines found in the APA Style Guide, located in the Student Success Center.
Basic Network Troubleshooting Steps and Tools
An Extensive Study of Network Troubleshooting with the Tools used.
We explored all about Network Security along with its types in our previous tutorial.
When we run a network or while working in any system there are always chances of failure in the smooth operation owing to technical, physical or any other faults.(Comprehensive Essay Overview on Network Troubleshooting 101)
For uninterrupted running of the system, we need to resolve the raised issues as soon as possible and for this, we need to detect the cause of the problem first and then fix it.(Comprehensive Essay Overview on Network Troubleshooting 101)
Must Read => Beginner’s Guide to Networking
Thus the process of detection, minimization and resolving the faults that arise in the network while performing the various day to day activities is known as troubleshooting.(Comprehensive Essay Overview on Network Troubleshooting 101)
Here we will explore the different kinds of troubleshooting steps and the tools we use for fault detection and closure of the same.
What You Will Learn: [show]
In this tutorial, we are only concerned about the computer networking fault diagnosis and rectification.
Based on the type of issue, we will discuss its troubleshooting steps and tips.
Basic Network Problems(Comprehensive Essay Overview on Network Troubleshooting 101)
Cable Problem: The cable which is used to connect two devices can get faulty, shortened or can be physically damaged.
Connectivity Problem: The port or interface on which the device is connected or configured can be physically down or faulty due to which the source host will not be able to communicate with the destination host.
Configuration Issue: Due to a wrong configuration, looping the IP, routing problem and other configuration issues, network fault may arise and the services will get affected.(Comprehensive Essay Overview on Network Troubleshooting 101)
Software Issue: Owing to software compatibility issues and version mismatch, the transmission of IP data packets between the source and destination is interrupted.
Traffic overload: If the link is over utilized then the capacity or traffic on a device is more than the carrying capacity of it and due to overload condition the device will start behaving abnormally.
Network IP issue: Due to improper configuration of IP addresses and subnet mask and routing IP to the next hop, the source will not be able to reach the destination IP through the network.(Comprehensive Essay Overview on Network Troubleshooting 101)
Network Troubleshooting 101
Network Troubleshooting Flowchart
Steps Involved in Network Diagnostics
Here steps to troubleshoot and diagnose various network problems like IP, connectivity, wireless connection, etc.
Troubleshooting IP Problems(Comprehensive Essay Overview on Network Troubleshooting 101)
In the TCP/IP protocol suite, if we are not able to reach at the destination IP address and not able to find the route to reach the next hop at any point in the network, then we will use PING and TRACEROUTE tools for troubleshooting the cause and location of the issue.
The generic steps to troubleshoot the IP related issues in the network include:
Firstly locate the pair of devices between the source and the destination host between which the connectivity issue has occurred.(Comprehensive Essay Overview on Network Troubleshooting 101)
Once you locate the devices using the tools, the fault can be due to a physical connectivity issue. Thus check the physical connections all over the path.
There can be a fault in the LAN connectivity as well if you are working in a LAN network. So check the LAN connections. The local port can be faulty or down due to which the source cannot be able to reach the destination IP.(Comprehensive Essay Overview on Network Troubleshooting 101)
One of the reasons of the fault can be the router connectivity issue while traveling through various paths to reach the destination. Hence check that if the router is defined properly at each of the intermediate hops.
Check the configuration settings.
Troubleshooting Local Connectivity Issues
Once on the broad level, if you find that there is an issue in the LAN connectivity, then in order to locate the root cause and to resolve it, you should follow the below steps:
If the destination and the source are of the identical subnet mask, then try to ping the destination IP.
Else, if the destination is of some other subnet mask then try to ping the gateway IP address of the router.
Now, if both the ping fails, then first check that in the configuration settings, if both the subnet mask and route to be followed to reach the destination are defined properly in the routing table or not?(Comprehensive Essay Overview on Network Troubleshooting 101)
Once you are done with the configuration part and found everything OK, then check if your source host is able to ping some another hop in the LAN network other than the destination host or route to that?
If you are not able to ping to another device then there can be many reasons for this. It may even be a configuration issue, a physical connectivity issue, and repetitive IP address entry issue.
Correcting the Repetitive IP address Entry Issue
For rectifying the duplicate entry of an IP issue, disconnect the doubtful device from the LAN and also make the interface on which the device was connected shut down.
Now ping the device from some another device of the same subnet or LAN network. If the ping is OK, then it indicates that the IP is being used by some other device as well on the network. From the ARP table of the device, find out its MAC address and modify the IP address according to planning.(Comprehensive Essay Overview on Network Troubleshooting 101)
But if the problem persists still, then there will be a physical connectivity or configuration issue in it.
Troubleshooting Physical Connectivity Issues
The list of faults that come under this category are:
Improper connection of cables
Router, switch or hub port is faulty or down.
Traffic overload on the link or particular interface.
Configuration issue at layer-1.
Let’s take a look at the above in detail.
#1) Checking Cable connectivity Issue: The cables are used for connections, based on the type of connectivity. Like, for connectivity between a router and a computer the crossover pair of the cable is used. Thus make sure that the suggested and suitable cable is used to make a physical connection between any two devices.(Comprehensive Essay Overview on Network Troubleshooting 101)
If connections are found ok, then maybe the cable is faulty, so check the connectivity by replacing the existing cable with a newer one. Still, if the problem persists, then check the port or interface on which the link is terminated. There is a possibility for the port to be faulty.
Network Troubleshooting 101
#2) Port Faulty Scenario: Check that the port or interface on which the link is established is not shut down. Verify the duplex mode and speed as well. If the port is up and still the problem persists, then there are indicator lights that are present on each of the device to show the running status of the port.(Comprehensive Essay Overview on Network Troubleshooting 101)
From the indicator lights, check if the port is physically radiating or down. If the port is physically malfunctioning then it will appear by light status. In this situation, configure the link on some other free port or interface.
#3) Traffic overload: If there is more traffic than the carrying capacity at a link or interface then at some point it will start behaving abnormally. Thus verify these criteria to ensure smooth running.
#4) Configuration Issue: Check the router configuration on the interface by show ip interface and show running-config commands.(Comprehensive Essay Overview on Network Troubleshooting 101)
Troubleshooting Routing Problems
When we route the data packets in the network, then the chances for occurrences of fault are usual. Thus depending on the type of fault, we will prepare our plan for resolving the faults.
The kind of fault that occurs between the source and destination hosts while floating data packets in a network are listed below:
The route is not defined in the router between the source and destination.
A wrong Routing protocol is used to find out the route to the next hop or destination.
Software related fault at the router.(Comprehensive Essay Overview on Network Troubleshooting 101)
Any filter or firewall may be barring the entry of data packets to the destination node.
There may be configuration faults that arise at the source router end.
Network Troubleshooting 101
How to proceed for resolution:
To find out the resolution, the first step is to locate the hop between the source and the destination where the problem has occurred.
The process verifies the IP connectivity and routing protocols connectivity at each hop starting from the source host towards the destination one.(Comprehensive Essay Overview on Network Troubleshooting 101)
We can also use the traceroute tool to locate the hop where the problem has arised. But this is not helpful in all the cases. Hence, it is better if we proceed with the first one.
Once we locate the problematic hop, then login to that router via telnet and then try to ping the source and destination host.
If the ping is not successful, then verify the routing table for routes between the source and destination. If routes are not defined then configure the IP routes with the subnet mask and default route in the router.
In condition, if the ping responses with only a few percentages of success, then there may be multiple paths that are defined to reach the destination. But out of multiple paths, one is failing to reach the destination. The cause for this is that a routing loop can occur in the path. To rectify this, trace the looping hop, and correct the configuration.
After rectification of the above steps, if still, the problem persists, then check the routing protocol used, and change the protocol in accordance with the network.(Comprehensive Essay Overview on Network Troubleshooting 101)
The configuration issues at a particular router can be checked using a command like show ip interface for interface related faults, show ip access-group for finding out ant firewall or filter is configured in the network and you can check what is allowed to pass through it, show version for uptime and show running-config for the overall configuration.
ADDITIONAL INSTRUCTIONS FOR THE CLASS
Discussion Questions (DQ)
- Initial responses to the DQ should address all components of the questions asked, include a minimum of one scholarly source, and be at least 250 words.(Comprehensive Essay Overview on Network Troubleshooting 101)
- Successful responses are substantive (i.e., add something new to the discussion, engage others in the discussion, well-developed idea) and include at least one scholarly source.
- One or two sentence responses, simple statements of agreement or “good post,” and responses that are off-topic will not count as substantive. Substantive responses should be at least 150 words.(Comprehensive Essay Overview on Network Troubleshooting 101)
- I encourage you to incorporate the readings from the week (as applicable) into your responses.
- Your initial responses to the mandatory DQ do not count toward participation and are graded separately.
- In addition to the DQ responses, you must post at least one reply to peers (or me) on three separate days, for a total of three replies.(Comprehensive Essay Overview on Network Troubleshooting 101)
- Participation posts do not require a scholarly source/citation (unless you cite someone else’s work).
- Part of your weekly participation includes viewing the weekly announcement and attesting to watching it in the comments. These announcements are made to ensure you understand everything that is due during the week.
APA Format and Writing Quality
- Familiarize yourself with APA format and practice using it correctly. It is used for most writing assignments for your degree. Visit the Writing Center in the Student Success Center, under the Resources tab in LoudCloud for APA paper templates, citation examples, tips, etc. Points will be deducted for poor use of APA format or absence of APA format (if required).(Comprehensive Essay Overview on Network Troubleshooting 101)
- Cite all sources of information! When in doubt, cite the source. Paraphrasing also requires a citation.
- I highly recommend using the APA Publication Manual, 6th edition.
Use of Direct Quotes
- I discourage overutilization of direct quotes in DQs and assignments at the Masters’ level and deduct points accordingly.
- As Masters’ level students, it is important that you be able to critically analyze and interpret information from journal articles and other resources. Simply restating someone else’s words does not demonstrate an understanding of the content or critical analysis of the content.(Comprehensive Essay Overview on Network Troubleshooting 101)
- It is best to paraphrase content and cite your source.
- For assignments that need to be submitted to LopesWrite, please be sure you have received your report and Similarity Index (SI) percentage BEFORE you do a “final submit” to me.
- Once you have received your report, please review it. This report will show you grammatical, punctuation, and spelling errors that can easily be fixed. Take the extra few minutes to review instead of getting counted off for these mistakes.
- Review your similarities. Did you forget to cite something? Did you not paraphrase well enough? Is your paper made up of someone else’s thoughts more than your own?(Comprehensive Essay Overview on Network Troubleshooting 101)
- Visit the Writing Center in the Student Success Center, under the Resources tab in LoudCloud for tips on improving your paper and SI score.
- The university’s policy on late assignments is 10% penalty PER DAY LATE. This also applies to late DQ replies.
- Please communicate with me if you anticipate having to submit an assignment late. I am happy to be flexible, with advance notice. We may be able to work out an extension based on extenuating circumstances.
- If you do not communicate with me before submitting an assignment late, the GCU late policy will be in effect.
- I do not accept assignments that are two or more weeks late unless we have worked out an extension.
- As per policy, no assignments are accepted after the last day of class. Any assignment submitted after midnight on the last day of class will not be accepted for grading.
- Communication is so very important. There are multiple ways to communicate with me:
- Questions to Instructor Forum: This is a great place to ask course content or assignment questions. If you have a question, there is a good chance one of your peers does as well. This is a public forum for the class.
- Individual Forum: This is a private forum to ask me questions or send me messages. This will be checked at least once every 24 hours.(Comprehensive Essay Overview on Network Troubleshooting 101)