TELE301 is a paper about network management. We cover topics such as system administration using Linux, Ethernet, and network management using a typical router interface.
The paper is assessed via a number of labs worth up to 5% each, no assignments, and a final exam worth 50%.
There are two labs per week, each two hours long. The reading for this paper is primarily to read the lab notes, which in total are large enough to consitute a usefully sized text-book, which you will likely find useful after the course as well.
Because of the diverse background of students coming into this paper, you should all make certain to work through the pre-lab material. This will ensure that you can log in, and have basic Linux/Unix experience; it is also important for getting everyone off to a smooth start without having login problems etc.
If you are not doing any Computer Science papers this semester, you need to make certain that you have signed and returned an Acceptable Use form, which you can pick up from the Computer Science office in the Owheo building. Otherwise, you will not have a user-account created, and you won't be able to login.
In order to stay up-to-date with events in the paper, you are expected to check your Computer Science e-mail once a day also. If you are not using your Computer Science address for your daily correspondence, it is your responsibility to have it forwarded. You can do this through the Computer Science webmail interface. If forwarding off-campus, you are required to ensure that a copy remains on-campus; that way if your off-campus e-mail becomes unreachable for whatever reason, you still have it available locally.
You will have been used to papers previously where the structure of the paper was very linear: each lab depends on all the labs previously. That cannot be the case in a paper such as this where there are many dependencies in knowledge. This is illustrated in the following diagram.
As you can see, many labs depend on DNS. This mirrors reality: many networks services, such as Web servers use DNS, but you don’t need to know about FTP services in order to set up a SSH server. There are some broad themes however; you can break this paper into three parts: the first part introduces you to aspects of the individual system; the second part introduces you to network services run on servers for clients; and the third part looks at network services that run between devices such as routers, which clients have very little to do with.
So if you’re feeling a bit lost, wondering how a particular lab relates to the previous lab, realise that it probably doesn’t and that this mirrors real life, but that there are some labs that you will have needed to complete in order to progress onto others.