Best Practice and Troubleshooting Model Essay

Submitted By sierra509
Words: 477
Pages: 2

Best Practices for Network Troubleshooting
March 16, 2015
Best Practices for Network Troubleshooting A troubleshooting model is a process that outlines troubleshooting steps to help resolve network issues quicker and less arduous. They can come in many standards such as step-by-step process to follow when a problem arises. When troubleshooting a network issue, one should follow a systematic process that involves recognizing, diagnosing, and resolving the issue. This helps to ensure that one does not waste time or cause further damage or disruption by making incorrect assumptions and taking the wrong steps to resolve the problem. According to the article I researched most companies best practice approach to troubleshooting networks do not follow a standardized process. However, some approaches for best practice for network troubleshooting, the process can vary within any organization. In today’s process some think of the trial and error approach is a good way to troubleshoot a problem. One can implement a change and wait to see if it resolves the problem and continue to repeat the process until all issues have been resolved. Another approach to troubleshooting some might implement is collaboration with others. While the trial and error method for troubleshooting may still be needed for some unique problems a troubleshooting model should be implemented. According to Fluke Corporation (2014), “troubleshooting time can be greatly reduced by setting up the support team with defined process to isolate the majority of problems and providing a set of tools that can reduce collaboration time.” By having a best practice approach when it comes to troubleshooting it can reduce the resolution time so it can free up staff members to work on other projects or matters. Fluke Networks has defined the best practice for troubleshooting as; find common problems, automation, and collaboration: Finding common problems can quickly identify the problem and save some time. Creating a check list of common problems for a technician can reduce downtime. Once the problem has been