Using a structured approach to troubleshooting
9.2.2 Troubleshooting is a process that allows a user to find problems on a network. This page explains why an orderly process should be used to troubleshoot a network. This process should be based on the networking standards set in place by a network administrator. Documentation is a very important part of the troubleshooting process.
The steps in this model are as follows:
Step 1 Collect all available information and analyze the symptoms of the failure.
Step 2 Localize the problem to a particular network segment, module, unit, or user.
Step 3 Isolate the trouble to specific hardware or software within the unit, module, or user network account.
Step 4 Locate and correct the problem.
Step 5 Verify that the problem has been solved.
Step 6 Document the problem and the solution.
Another approach to troubleshooting. These are not the only ways to troubleshoot a network. However, an orderly process is important to keep a network running smoothly and efficiently.
When a structured approach is used, every member of a network support team knows which steps the other team members have completed to troubleshoot the network. If a variety of troubleshooting ideas are tried with no organization or documentation, problem solving is not efficient. Even if a problem is solved in the non-structured environment, it will be difficult to replicate the solution for similar problems.
The Interactive Media Activity will help students become familiar with the troubleshooting process.
The next page will teach students the types of errors that occur at the first three layers of the OSI model.
9.2.2 Troubleshooting is a process that allows a user to find problems on a network. This page explains why an orderly process should be used to troubleshoot a network. This process should be based on the networking standards set in place by a network administrator. Documentation is a very important part of the troubleshooting process.
The steps in this model are as follows:
Step 1 Collect all available information and analyze the symptoms of the failure.
Step 2 Localize the problem to a particular network segment, module, unit, or user.
Step 3 Isolate the trouble to specific hardware or software within the unit, module, or user network account.
Step 4 Locate and correct the problem.
Step 5 Verify that the problem has been solved.
Step 6 Document the problem and the solution.
Another approach to troubleshooting. These are not the only ways to troubleshoot a network. However, an orderly process is important to keep a network running smoothly and efficiently.
When a structured approach is used, every member of a network support team knows which steps the other team members have completed to troubleshoot the network. If a variety of troubleshooting ideas are tried with no organization or documentation, problem solving is not efficient. Even if a problem is solved in the non-structured environment, it will be difficult to replicate the solution for similar problems.
The Interactive Media Activity will help students become familiar with the troubleshooting process.
The next page will teach students the types of errors that occur at the first three layers of the OSI model.
No comments:
Post a Comment