The basic troubleshooting sequence consists of five steps:
1. Document your network: A diagram of the parts of the network, as well as the signal flow paths between the various devices, is enormously helpful in visualizing the problem and saving valuable time. Theory and practical experience will determine which test to perform first. Consider experience with the same or similar equipment and related symptoms, as well as the probability of what is likely to fail or what suffers from repeated failures. A good practice however, is to start with the physical layer first, and work your way up the protocol stack.
2. Collect all available information, and analyze the symptoms of the failure.
3. Localize and isolate the problem: It's best to subdivide or isolate a problem into a smaller functional section - removing the largest convenient section first (divide and conquer approach). Start at any convenient spot near the center point of the problem and divide the problem in half. Continue halving the problem until you've isolated it to the smallest possible section.
4. Correct the problem and verify problem resolution: Don't assume that the user is providing complete and accurate information. It's best to verify it yourself, or have the user show you how the problem was discovered.
5. Document what you did
Keeping the network running optimally requires IT professionals equipped with the right combination of tools and knowledge. Fluke Networks'
LAN Testers provide frontline technicians with the ability to quickly resolve link, cable and connectivity issues - reducing problem escalation. For more difficult Ethernet problems, our
portable analyzers give technicians and engineers deep vision into LAN, WLAN, VLAN and WAN networks. The links above contain useful information about the products, technology and success stories for Basic Ethernet Troubleshooting to help you become a more powerful problem solver.