|
|
11.1 | General Approach to Troubleshooting | ||
| 11.1.1 | Overview |
|
The keys to maintaining a problem-free
network environment are documentation, planning, and communication.
These three factors also determine the ability to isolate and fix a
network fault quickly. This requires a framework of procedures and
personnel that are established long before any network changes take
place. The goal of this module is to help isolate and resolve the
most common connectivity and performance problems in a network
environment.
Networks continue to add services as time goes on, and each additional service introduces more variables in network implementation. This also adds to the complexity of troubleshooting the network. Therefore, organizations increasingly depend on network administrators and network engineers with strong troubleshooting skills. Engineers spend a large portion of their time troubleshooting. Therefore, all procedural tools that can be used to simplify the process are important. The time it takes to become familiar with each procedural tool may reduce the time spent troubleshooting in the field. The decision to invest time into learning a new procedure is not an easy choice to make. The main goal is to optimize the time spent learning new procedures to help shorten the time spent working in the field. After the protocols and product lines
have been considered, troubleshooting is essentially an exercise in
logic
Deductive reasoning works from the more
general to the more specific
Inductive reasoning works the opposite
way, moving from specific observations to broader generalizations and
theories
|