Troubleshooting Process

Today’s post is going to be talking about troubleshooting and where to start the troubleshooting process. Yes there is an actual process that every technician should be aware of. You can also use this troubleshooting process at home, you may not know how to fix it but at least you know where the issue is and find someone who can.

Before we begin if you haven’t seen yet, let me introduce to you the troubleshooting process:

  • You want to gather information about the problem. (What happened?)
  • Keep it simple, verify the obvious issues FIRST! (Is the device powered on?)
  • Try some quick solutions first (restart, reinstall, verify connections)
  • Gather information from the device (Device Manger, if you are in routers or switches use “Show” commands and “Debug” commands)
  • Use your research skills! Evaluate the problem and try possible solutions. (Internet searches, Online Forums, past experiences etc.)
  • Finally keep note of what you did even if you did not fix the issue. (Keep an engineer notebook!)

This may look simple, and it is! This is the exact method I use when troubleshooting a problem. Troubleshooting is a hard skill to have, as you really can’t learn from it in a book. You have to have experience with the type of technology you’re working with. One thing I use all the time is my research skills this can be a life saver if you know what to look for, use key details! The internet can be helpful but putting generic terms like “windows XP is not working” will not help you but instead waste your time. Use the key terms when have an issue like an error code, type the error message, describe what you can’t do, etc. Chances are somebody somewhere has had the same problem or at least something like it and decided to post it.

Another thing I like to do when checking on a problem is going to the source! Although there are helpful places around web like forums, and chat systems I usually use this last. If I am having a problem with Windows for example I’ll go to Microsoft Support. Same thing if I have an issue with a Cisco product I’ll go to Cisco’s Support webpage before I go and search my problem around the web. Finally remember ask other technicians if they have seen the problem.

By using these steps and guidelines will be able to become better at troubleshooting like before it’s something you can’t learn from a book you must have experience with technology before you can even start troubleshooting. My last word of advice is keeping a record! Write down the steps you did, why did them and what where the solutions to the problem? If you couldn’t figure it still write it down. That way if the issue occurs again you and other people know exactly how to fix the problem or also know what solutions not work last time and not waste any of your time, like always I hope this information was informative and if you have an idea about the next ICND1 or ICND2 topic comment below.

Advertisements