Chapter Summary
Troubleshooting networks is an activity with which network administrators become very familiar. Successful troubleshooting does not happen by accident; rather, the troubleshooting process follows some defined procedures. These procedures include the following:
1. |
Establish what the symptoms are. |
2. |
Identify the affected areas. |
3. |
Establish what has changed. |
4. |
Select the most probable cause. |
5. |
Implement a solution. |
6. |
Test the results. |
7. |
Recognize the potential effects of the solution. |
8. |
Document the solution. |
You can use several strategies when troubleshooting different topologies, and each topology has unique troubleshooting considerations. When you are troubleshooting a network, it is necessary to identify the topology that is being used and think about the troubleshooting strategies associated with that particular topology.
Troubleshooting client connectivity is a common task for network administrators. There are several areas to check when troubleshooting connectivity: You need to verify authentication, verify permissions, confirm physical connectivity, and confirm the protocols. Each of these areas may be at the root of a client connectivity issue, but the correct troubleshooting procedure requires starting with the most probable cause and working from there.
At times, you might find yourself troubleshooting wiring and infrastructure problems. Although they are less common than other troubleshooting areas, wiring and network devices should be considered possible causes of a problem. Tracking down infrastructure problems often requires using documentation and network maps or taking baselines to compare network performance.
KEY TERMS
|