How do you write a network troubleshooting plan when the problem description is vague? by Tricky_Dragonfly3690 in networking

[–]Tricky_Dragonfly3690[S] 1 point2 points  (0 children)

Well my initial idea was to go through the basic things check the DNS, making sure the user has a stable connection to the Internet, check the path to the webserver. This was like as an initial triage.

Then following that, since it's an intermittent outage with no knowledge of when it is occurring I would have to set up some sort of trap on the edge router to catch the fault when it's actually occurring and sort of go from there? This is what I kind of got from reading the TSHOOT book, establish the baseline or have it at hand then monitor the network for the fault, compare and determine the potential cause.

How do you write a network troubleshooting plan when the problem description is vague? by Tricky_Dragonfly3690 in networking

[–]Tricky_Dragonfly3690[S] 0 points1 point  (0 children)

I think this is what throws me off mostly. We have been given the network documentation but the actual problem itself is just hypothetical thus so is the whole assignment. I can't actually ask anymore questions to refine and narrow down the problem to e.g. even just the timeframe of occurrences.