Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

NC 2.17: A method for finding network faults

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

60 minutes

One desk cannot connect

Desk 14 has no connection. Desk 15, next door, works. A new installer swaps the switch, the cable and the computer all at once. The desk works again, but nobody knows which change fixed it.

A good fault-finder works in a fixed order, changes one thing at a time and writes it down.

Key words

WordWhat it means
Faultsomething that stops a system doing its job
Routine monitoringchecking a system on a schedule, before anyone complains
Diagnosisworking out the cause of a fault from the facts
Baselinethe record of how a system behaved when it was working well
Eliminaterule a cause out because the facts do not fit it
Shortlistthe few causes that are still possible
Resolutionthe fix, and the steps that stop the fault coming back
Networkdevices joined so they can share data
Network planthe record of what is installed and every change made to it

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can follow the four stages of troubleshooting and apply them to a fault.

Starter: testing

Have a go

Starter: testing

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Stage 1: identify the problem

A problem is found in one of two ways. A fault occurs and a user reports it. Or routine monitoring spots it first.

Write down what is wrong, where, since when, and who is affected. Be exact. "No network at desk 14 since 9 am" is better than "it is broken".

Stage 2: diagnose

First gather information. Ask what the user did and what changed. Use the reporting tools: logs, alerts and the lights on the ports.

Then analyse. Compare with the baseline. Compare with a similar system that works, such as the next desk. Finally consider the causes: eliminate what the facts rule out, and list what is left.

Stage 3: test what is left

Test the shortlist one cause at a time. Change one thing, then check. If a cause is wrong, rule it out and move on. Keep going until one cause explains the fault.

Changing many things at once hides the answer.

Check: the first three stages

Have a go

Check: the first three stages

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

The lesson goes on

7 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.