3 answers
1
Question
Asked
724 views
What are some of the hardest problems to troubleshoot and how often do they occur?
I am a student at Npower with the ITF+ certification and currently working towards the A+ certification. I also have great interest in networking. #networking
Login to comment
3 answers
Updated
Ankush’s Answer
The hardest problems to troubleshoot I feel based on my experience are performance related, includes, latency issues.
They can occur very frequently or you can say every day on an average.
While troubleshooting these, you really need to be very good in your basics. Basic troubleshooting steps are most important while dealing with these kind of problems as that is what decides your troubleshooting directions and next steps.
Hamed Ettefagh
Senior Manager Cloud Engineering & Infrastructure
5
Answers
Updated
Hamed’s Answer
Kenny,
More and more services and application are moving to a SaaS and PaaS model. These solutions are served over the internet from the cloud and to access them requires a good network connection. Generally there is no route path control over the internet and when it comes to troubleshooting you will be dealing with many uncontrollable factors. It's important to take a methodological approach in troubleshooting any issues and rule out one by one.
More and more services and application are moving to a SaaS and PaaS model. These solutions are served over the internet from the cloud and to access them requires a good network connection. Generally there is no route path control over the internet and when it comes to troubleshooting you will be dealing with many uncontrollable factors. It's important to take a methodological approach in troubleshooting any issues and rule out one by one.
Updated
Chad’s Answer
Kenny,
In my experience, the hardest problems to troubleshoot would be related to performance of technology within a user's unique environment. In a static, controlled environment, where all the variables are the same, it's easy to track down problems related to networking, processing, storage or more. Once you inject the uniqueness of a customer's environment, it becomes more difficult.
It's difficult, but not impossible. The underlying basics of technology don't change. What changes is how customers are using the technology and the various loads that are being put on the systems. Sometimes, a variable in one place can cause an issue someplace that doesn't even seem related.
The cool part about what we do is the investigative work, almost like Sherlock Holmes, to figure out where the issue comes from. You will use things like process of elimination, logging, observation and recreating the problem in order to keep whittling down the various places it could be until you find the problem itself.
It's a very rewarding process, not only because you feel good about yourself, but more importantly because you helped someone who really needed your help!
You will learn basic troubleshooting tips throughout your career and these will help you on any type of troubleshooting you need to do, whether it's application, networking, compute or storage.
Good luck and keep searching for that bug!
Check out some books on basic technology troubleshooting.
In my experience, the hardest problems to troubleshoot would be related to performance of technology within a user's unique environment. In a static, controlled environment, where all the variables are the same, it's easy to track down problems related to networking, processing, storage or more. Once you inject the uniqueness of a customer's environment, it becomes more difficult.
It's difficult, but not impossible. The underlying basics of technology don't change. What changes is how customers are using the technology and the various loads that are being put on the systems. Sometimes, a variable in one place can cause an issue someplace that doesn't even seem related.
The cool part about what we do is the investigative work, almost like Sherlock Holmes, to figure out where the issue comes from. You will use things like process of elimination, logging, observation and recreating the problem in order to keep whittling down the various places it could be until you find the problem itself.
It's a very rewarding process, not only because you feel good about yourself, but more importantly because you helped someone who really needed your help!
You will learn basic troubleshooting tips throughout your career and these will help you on any type of troubleshooting you need to do, whether it's application, networking, compute or storage.
Good luck and keep searching for that bug!
Chad recommends the following next steps: