Annotation of /trunk/lab.tex

Revision 5 - (view) (download) (as text)

1 :	mark	1	\documentclass{book}
2 :
3 :	mark	5	\author{Oslo University College, Norway\\~\\Mark Burgess}
4 :			\title{Network Infrastructure and Security Laboratory Workbook\\Version 2.4}
5 :	mark	1	\date{\today}
6 :
7 :
8 :
9 :			%\topmargin -30pt
10 :
11 :	mark	4	\usepackage{epsfig}
12 :	mark	1	\usepackage{alltt}
13 :			\usepackage{bookman} % -- good
14 :			\usepackage{fancyheadings}
15 :			\usepackage{tocloft}
16 :
17 :
18 :			\usepackage{a4}
19 :			\usepackage{shadethm}
20 :			\pagestyle{fancyplain}
21 :			\lhead[\fancyplain{}{}]{\fancyplain{}{\rightmark}}
22 :			\rhead[\fancyplain{}{\leftmark}]{\fancyplain{}{}}
23 :
24 :
25 :			%\textheight 20cm
26 :			\textwidth 15.5cm
27 :			\oddsidemargin -20pt
28 :			\evensidemargin -20pt
29 :
30 :			\def\sex{\begin{alltt}\small}
31 :			\def\esex{\end{alltt}}
32 :			\def\ex{\begin{alltt}}
33 :			\def\eex{\end{alltt}}
34 :			\def\code{\tt\small}
35 :			\def\file{\tt\small}
36 :			\def\href{\tt\small}
37 :			\def\samp{\tt\small}
38 :			\def\kbd{\tt\small}
39 :			\def\key{\sc}
40 :			\def\var{\em}
41 :			\def\beq{\begin{eqnarray}}
42 :			\def\eeq{\end{eqnarray}}
43 :			\def\2{\frac{1}{2}}
44 :
45 :			%\setcounter{tocdepth}{1}
46 :
47 :			\usepackage{amsthm}
48 :
49 :			\newshadetheorem{expt}{Experiment}
50 :			\newshadetheorem{defin}{Definition}
51 :			\newtheorem*{corollary}{Corollary to principle}
52 :			\newshadetheorem{suggestion}{Suggestion}
53 :			\newtheorem{example}{Example}
54 :			\newtheorem{question}{Question}
55 :			\makeindex
56 :
57 :
58 :			\begin{document}
59 :			%\begin{figure}[ht]
60 :			%\psfig{file=NetlabCover.eps,width=14cm}
61 :			%\end{figure}
62 :			\maketitle
63 :			\bibliographystyle{plain}
64 :
65 :			%\setlength{\cftchapnumwidth}{18pt}
66 :			%\setlength{\cftsecnumwidth}{31pt}
67 :			%\setlength{\cftsubsecnumwidth}{40pt}
68 :
69 :			\tableofcontents
70 :
71 :			\part{Introduction}
72 :
73 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
74 :
75 :			\chapter{Introduction}
76 :
77 :			This booklet is your guide to the laboratory work for the Master's
78 :			degree in Network and System Administration.
79 :
80 :			MS009A is designed to demonstrate and practise the concepts of design,
81 :			configuration and maintenance of networked systems with a hands-on
82 :			approach. Another aim of the course is to foster independent and
83 :			scientific/diagnostic thinking. You will work with the same hardware
84 :			and development tools used by enterprise and service providers.
85 :
86 :			In order to carry out the experimental work, you will need to develop
87 :			your planning skills and your diagnostic (trouble shooting) skills.
88 :			The experiments are deliberately described in little detail to make
89 :			you devise your own plan to succeed.
90 :			In each experiment ask yourself --- how can I measure whether this
91 :			is working? How can I test this?
92 :
93 :			{\em You will work in pairs} in the lab, but everyone must write an individual
94 :			report. It is not acceptable to submit the same report as another student.
95 :			The estimated time for each experiment is noted in the text, but
96 :			this is not a fixed limit.
97 :
98 :			A handful of lectures will be given on special topics:
99 :			\begin{itemize}
100 :			\item General orientation.
101 :			\item Setting up an experiment.
102 :			\item Statistics and measurements.
103 :			\item Troubleshooting methods.
104 :			\end{itemize}
105 :			This is not a book of recipes but a guide to help you to make your own
106 :			decisions and investigations.
107 :
108 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
109 :
110 :			\chapter{Safety and responsibility in the Lab}
111 :
112 :
113 :			Oslo University College is committed to providing a safe and healthy
114 :	mark	5	working environment for its students and staff, and to teaching safe
115 :			and healthy practices in your later employment. You will learn working
116 :			practices that you will take with you when you leave the College. It
117 :			is your ethical duty to spread safe working practices and procedures
118 :			beyond this College in the workplace.
119 :	mark	1
120 :
121 :			Oslo University College requires its students, staff, and faculty to
122 :			adhere to basic General Laboratory Safety Rules in the Electrical
123 :			Engineering laboratories.
124 :
125 :			These rules apply to everyone. If you see someone ignoring the rules,
126 :			it is your duty to remind them of their responsibilities.
127 :
128 :			\noindent {\em This discipline is a mark of professionalism -- it is not for
129 :			annoyance or for show. You might find other labs that do not care about
130 :			safety, but as a student of Oslo University College, we expect the highest
131 :			standards.}
132 :
133 :	mark	5
134 :
135 :	mark	1	\section{General Laboratory Safety Rules}
136 :
137 :			\begin{enumerate}
138 :	mark	5	\item The lab is a dry and noisy environment. You should try to organize
139 :			your work so that you do not spend more than three or four hours in the lab
140 :			at any one time. If you need to talk to your work partners, go out of the
141 :			lab into a quiet area rather than shouting.
142 :
143 :	mark	1	\item Food and drink must not be brought into, stored in
144 :			or consumed in a laboratory.
145 :
146 :	mark	5	\item Never wear personal headphones or play music to drown out the noise:
147 :			you can damage your hearing by playing loud music, and cause accidents by
148 :			being distracted. Your full attention should be on your work.
149 :
150 :	mark	1	\item Shoes must be worn, and appropriate
151 :			personal clothing shall be worn in laboratories.
152 :
153 :	mark	5	\item Do not wear items of metal jewelry when using electronic equipment. You might cause a short-circuit, get a shock or get the jewelry caught in something.
154 :	mark	1
155 :	mark	5	\item Bags and coats should be left at the doorway.
156 :	mark	1
157 :	mark	5	\item {\em BE TIDY AND TREAT ALL EQUIPMENT WITH RESPECT}. Do not
158 :			tread on or run over cables with chairs or heavy objects.
159 :
160 :	mark	1	\item Never drop items on the floor. Always put equipment in the correct box or storage place provided for it. Fold cables neatly to avoid long-term damage to them.
161 :
162 :			\item Learn and know what to do in an emergency.
163 :
164 :			\item Do not expose yourself or others to risk. Do not joke around in the lab.
165 :
166 :			\item Un-authorized persons MUST NOT be admitted to the laboratory.
167 :
168 :			'Authorized' means having business in the laboratory with the permission
169 :			of the College. No-one under the age of eighteen
170 :			may enter the lab unsupervised. Only trained individuals and students enrolled in courses using the lab may touch the equipment.
171 :
172 :			\item Laboratory shall remain locked when unoccupied.
173 :			\item Never open (remove cover) of any equipment in the laboratories, unless you are
174 :			instructed to do so.
175 :			\item Report all problems to drift@iu.hio.no (extensions 3268/3264/3263)
176 :			\end{enumerate}
177 :
178 :			\section{Electrical Safety Guidelines}
179 :
180 :			\begin{enumerate}
181 :			\item Be familiar with the electrical hazards associated with your workplace.
182 :
183 :			\item Be as careful for the safety of others as for yourself. Think before
184 :			you act. Be tidy and systematic.
185 :			\item Avoid bulky, loose or trailing clothes. Avoid long loose hair. Remove
186 :			metal bracelets or watch-straps.
187 :
188 :			\item Do not take food or drink into the laboratory. Avoid wet
189 :			hands and clothing. \item Use extension cords (skj\o
190 :			teledninger) only when necessary and only on a temporary basis.
191 :			Request new power outlets if your work requires equipment in an
192 :			area without an outlet.
193 :
194 :			\item ALWAYS report damaged cords and cables, including cables that become hot, or with
195 :			exposed wiring. Never ignore these or replace them for others to use.
196 :
197 :
198 :			\item Experiments left unattended should be isolated. If
199 :			for a special reason, it must be left on, a barrier and a warning notice
200 :			are required.
201 :			\item Equipment found to be faulty in any way should be reported immediately
202 :			and not used until it is inspected and declared safe.
203 :
204 :			\item Voltages above 50 V RMS AC and 120 V DC are always dangerous. Extra precautions
205 :			should be considered as voltage levels are increased.
206 :
207 :			\item Never make any changes to circuits or mechanical layout without first
208 :			isolating the circuit by switching off and removing connections to supplies.
209 :
210 :			\item Know what you must do in an emergency.
211 :
212 :			\item Be acquainted with the Emergency Power Off:
213 :
214 :
215 :			\item When touching equipment that might be electrically "live" always use the {\em back of your hand}. Never grip anything with your fingers, since and electric shock will tend to make you grip tighter.
216 :
217 :			\item Electrical power sockets should not be overloaded.
218 :
219 :			\item {\b No cables should ever be stretched.} Tape them firmly to a table or floor. Remember that people can trip over cables.
220 :
221 :			\item Hold the plug firmly by the insulating cover when plugging it in or unplugging it.
222 :			{\bf NEVER} unplug an electrical device by pulling on its cord!
223 :
224 :			\item Do not attempt to lift or move heavy equipment alone.
225 :
226 :			\end{enumerate}
227 :
228 :			\section{Electrical Emergency Response}
229 :
230 :			The following instructions provide guidelines for handling two types
231 :			of electrical emergencies:
232 :
233 :
234 :			When someone suffers serious electrical shock, he or she may be
235 :			knocked unconscious. If the victim is still in contact with the
236 :			electrical current, immediately turn off the electrical power
237 :			source. If you cannot disconnect the power source, push in the
238 :			Emergency Power Off button.
239 :			\begin{enumerate}
240 :
241 :			\item Do not touch a victim that is still in contact with a power source; you
242 :			could electrocute yourself.
243 :
244 :			\item Have someone call for emergency medical assistance immediately. Administer
245 :			first-aid, as appropriate.
246 :
247 :			\item If an electrical fire occurs, try to disconnect the electrical power
248 :			source, if possible.
249 :
250 :
251 :
252 :			\item In case of fire, pull out power sockets if possible, taking care not to be electrocuted.
253 :			\item Use of {\bf clean water} to put out electrical fire is acceptable.
254 :			\end{enumerate}
255 :
256 :
257 :			\section{Handling equipment}
258 :
259 :
260 :			All electronic equipment should be treated as highly fragile and
261 :			easily damaged, regardless of how sturdy it is. Today we are far too
262 :			blas\'e towards electronic equipment.
263 :			\begin{itemize}
264 :			\item Never insert or remove power cords to equipment without ensuring that it is switched off.
265 :			\item Take care when inserting multi-pin connectors that the pins are oriented the right way up and that no pins are bent on insertion.
266 :			\end{itemize}
267 :			Moreover:
268 :			\begin{itemize}
269 :			\item {\em Read instructions:}
270 :			When dealing with hardware, one should always look for and {\em read}
271 :			instructions in a manual. It is foolish to make assumptions about expensive
272 :			purchases. Instructions are there for a reason.
273 :			\item {\em Interfaces and connectors:}
274 :			Hardware is often connected to an interface by a cable or connector.
275 :			Obtaining the correct cable is of vital importance. Many manufacturers
276 :			use cables which look similar, superficially, but which actually are
277 :			different. An incorrect cable can result in damage to an interface.
278 :			Modem cables in particular can damage a computer or modem if they
279 :			are incorrectly wired, since some computers supply power through these
280 :			cables which can damage equipment which does not expect to find a
281 :			power supply coming across the cable.
282 :
283 :			\item {\em Handling components:}
284 :			Modern day CMOS chips work at low voltages (typically 5 volts or lower).
285 :			Standing on the floor with insulating shoes, you can pick up a
286 :			static electric charge of several thousand volts. Such a charge
287 :			can instantly destroy computer chips. Before touching any
288 :			computer components, earth yourself by touching the metal
289 :			casing of the computer. If you are installing equipment inside
290 :			a computer, wear a conductive wrist strap. Avoid wearing rubber sandals
291 :			or shoes that insulate you from Earth when dealing with
292 :			open case equipment, since these cause the body to
293 :			build up charge that can discharge through that equipment; on the
294 :			other hand this might be good advice when working around high voltage
295 :			or current sources.
296 :			\index{Components, handling}
297 :			\index{Handling components}
298 :
299 :			\item {\em Disks:}
300 :			Disk technology has been improving steadily for two decades. The most
301 :			common disk types, in the workplace, fall into two families: ATA
302 :			(formerly IDE) and SCSI. The original IDE (Integrated Drive
303 :			Electronics) and SCSI (Small Computer Software Interface) had
304 :			properties that have since evolved faster than the prejudices about
305 :			them. ATA (formerly IDE) disks are now generally cheaper than SCSI
306 :			disks (due to volume sales) and excel at sequential access, but SCSI
307 :			disks have traditionally been more efficient at handling multiple
308 :			accesses due to a multitasking bus design, and are therefore better in
309 :			multitasking systems, where random access is important. However,
310 :			filesystem design also plays an important role in determining the
311 :			perceived performance of each; i.e. how operating systems utilize
312 :			buses during updates is at least as important as bus performance
313 :			itself. Interesting comparisons show that IDE technology has caught up
314 :			with the head start that SCSI disks once had\cite{white1} for many
315 :			purposes, but not all.
316 :
317 :			SCSI\cite{lisa93157} comes in several varieties, SCSI 1, SCSI
318 :			2, wide SCSI, fast-wide etc. The difference has to do with the width
319 :			of the data-bus and the number of disks which can be attached to each
320 :			controller. There are presently three SCSI standards SCSI-1, SCSI-2
321 :			and SCSI-3. The SCSI-2 standard defines also wide, fast and fast/wide
322 :			SCSI.
323 :			Each SCSI disk has its own address (or number) which must be set by
324 :			changing a setting on the disk-cabinet or by changing jumper settings
325 :			inside the cabinet. Newer disks have programmable identities.
326 :			\index{SCSI disks}
327 :			\index{IDE disks}
328 :			\index{ATA disks}
329 :			Disk chain buses must be terminated with a proper terminating
330 :			connector. Newer disks often contain automatic termination mechanisms
331 :			integrated into the hardware.
332 :			The devices on the SCSI bus talk to the computer through a
333 :			controller. On modern PCs the SCSI controller is usually connected to
334 :			the PCI bus either as an on-board solution on motherboards or as a
335 :			separate card in a PCI slot. Other buses are also used as the carrier
336 :			of the SCSI protocol, like FireWire (IEEE 1394) and USB. The SCSI
337 :			standard also supports removable media devices (CD-ROM, CD-R, Zip
338 :			drives), video frame grabbers, scanners and tape streamers (DAT, DLT).
339 :
340 :
341 :			\item {\em Memory:}
342 :			Memory chips are sold on small pluggable boards. They
343 :			are sold in different sizes and with different speeds.
344 :			A computer has a number of slots where they can be installed.
345 :			When buying and installing RAM, remember
346 :			\index{SIMM}
347 :			\begin{itemize}
348 :
349 :			\item The physical size of memory plug-ins is important. Not all of
350 :			them fit into all sockets.
351 :
352 :			\item Memory is sold in units with different capacities and data rates. One
353 :			must find out what size can be used in a system. In many cases one
354 :			may not mix different types.
355 :
356 :			\item There are various incompatible kinds of RAM that work in
357 :			different ways. Error correcting RAM, for instance, is tolerant to
358 :			error from external noise sources like cosmic rays and other ultra
359 :			short wave disturbances. It is recommended for important servers,
360 :			where stability is paramount.
361 :
362 :			\item On some computers one must fill up RAM slots in a particular
363 :			order, otherwise the system will not be able to find them.
364 :			\end{itemize}
365 :
366 :			\end{itemize}
367 :
368 :
369 :			\index{Weather}
370 :			Another aspect of hardware is the extent to which weather and
371 :			environment are important for operation..
372 :
373 :			\begin{itemize}
374 :
375 :			\item {\em Lightning:}
376 :			strikes can destroy fragile equipment. No fuse will protect hardware
377 :			from a lightning strike. Transistors and CMOS chips burn out much faster
378 :			than any fuse. Electronic spike protectors can help here, but nothing
379 :			will protect against a direct strike.
380 :
381 :			\item {\em Power:}
382 :			failure can cause disk damage and loss of data. A UPS
383 :			(Un-interruptible power supply) can help.
384 :
385 :			\item {\em Heat:}
386 :			The blazing summer heat or a poorly placed heater oven can cause
387 :			systems to overheat and suddenly black out. One should not let the
388 :			ambient temperature near a computer to rise much above about 25
389 :			degrees Centigrade. Clearly some equipment can tolerate heat, better
390 :			than other equipment. Bear in mind that metals expand significantly,
391 :			so moving parts like disks will be worst affected by heat. Increased
392 :			temperature also increases noise levels that can reduce network
393 :			capacities by a fraction of a percent. While this might not sound like
394 :			much, a fraction of a percent of a Giga-bit cable is a lot of
395 :			capacity. Heat can cause RAM to operate unpredictably and disks to
396 :			misread/miswrite. Good ventilation is essential for computers and
397 :			screens for avoiding electrical faults.
398 :
399 :			\item {\em Cold:}
400 :			Sudden changes from hot to cold are just as bad. They can
401 :			cause unpredictable changes in electrical properties of chips and
402 :			cause systems to crash. In the long term, these changes could lead
403 :			to cracks in the circuit boards and irreparable chip damage.
404 :
405 :			\item {\em Humidity:} In times of very cold weather and very
406 :			dry heat, the humidity falls to very low levels. At these times, the
407 :			amount of static electricity builds up to quite high levels, without
408 :			dissipating. This can be a risk to electronic circuitry. Humans pick
409 :			up charge just by walking around, that can destroy fragile
410 :			circuitry. Paper sticks together causing paper crashes in laser
411 :			printers. Too much humidity can lead to condensation and short circuits.
412 :
413 :			\end{itemize}
414 :			How could you go about verifying that conditions in the lab are
415 :			appropriate?
416 :
417 :
418 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
419 :
420 :			\chapter{When entering and leaving the laboratory}
421 :
422 :	mark	5	\section{Planning your time}
423 :
424 :			Time in the lab is precious. Do not arrive without having planned what
425 :			you are going to do. The lab environment is not conducive to thinking
426 :			and planning---it is a stressful and noisy environment. You should do
427 :			most of your thinking in advance. Other people could be using time
428 :			that you waste.
429 :
430 :	mark	1	\section{Sharing the lab}
431 :
432 :			In order to share the lab resources between many different groups, you
433 :			should expect that:
434 :			\begin{itemize}
435 :			\item When entering the laboratory, none of the equipment will be in a
436 :			pre-configured condition.
437 :
438 :			\item After your time in the lab, all reasonable equipment should be
439 :			returned to its original condition. Remove temporary cables and
440 :			store them neatly. If you want to preserve any parts of your
441 :			experiment, it is up to you to arrange it with the others on the course.
442 :			\end{itemize}
443 :			This presents you with a challenge. You should begin your lab term by
444 :			devising a way of saving your configurations and setting up your
445 :			experiments at short notice. {\em You must never save any
446 :			configuration in the memory of the routers, or on the PC hard-disks. }
447 :
448 :			Solving this problem will give you a good working practice that will benefit
449 :			you in a real working environment.
450 :
451 :			\section{Resources}
452 :
453 :			Cables need to last a long time. They can be damaged by running chairs
454 :			over them, stepping on them or stretching them.
455 :			\begin{itemize}
456 :			\item Please keep cables neat and tidy. Coil them and sort them by their
457 :			approximate length, so that others will be able to find them.
458 :			\item Make sure that you know the difference between ordinary Ethernet cables
459 :			and crossover (null-modem) cables. The latter are often colour-coded
460 :			yellow. Are there any other colour codes or markings.
461 :			\item Make sure that you know the difference between DCE and DTE serial
462 :			cables.
463 :			\end{itemize}
464 :			Tools should never be removed from the lab -- others will need them after you.
465 :
466 :
467 :			\begin{figure}[ht]
468 :	mark	5	\psfig{file=lab.eps,width=13cm}
469 :	mark	1	\caption{Lab layout.}
470 :			\end{figure}
471 :
472 :			\section{Security: the key}
473 :
474 :			No one has general access to the lab. You have been given a key card
475 :			to enter. Please do not lend this to others, under any circumstances.
476 :
477 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
478 :
479 :
480 :			\chapter{Documenting your lab-work}
481 :
482 :			Different kinds of experiment warrant different kinds of report.
483 :			You should aim to use your judgement in documenting work. It will
484 :			take you some time to learn how to write good reports.
485 :
486 :			\section{Keep a notebook}
487 :
488 :			You should buy a (paper) notebook for recording a diary of your
489 :			procedures, measurements and results from the lab. Keeping a tidy,
490 :			legible notebook is important for your later understanding of what you
491 :			did. Part of your grade will be based on how well you keep your
492 :			notebook. If you later come to doubt your results, you will need to be able
493 :			to read and understand the notes that you made, and perhaps reproduce the
494 :			results again exactly.
495 :
496 :			\section{Plan your work}
497 :
498 :			The purpose of the lab experiments is two-fold:
499 :			\begin{itemize}
500 :			\item To develop your practical skills.
501 :			\item To develop your analytical and reporting skills.
502 :			\end{itemize}
503 :			You should take your report writing seriously, since your grade will be based on this.
504 :			Each experiment should be written up as a document, giving all details
505 :			of your procedure and results. The document should have the form:
506 :			\begin{itemize}
507 :			\item {\bf Describe the aim of your experiment}: write an introduction motivating the
508 :			experiment, referring to any sources of information that you use
509 :			explicitly or implicitly.
510 :			\item {\bf Describe the equipment and tools} to solve the experimental task. Explain why you make these choices and what the possible limitations are.
511 :
512 :			\item {\bf Describe the experimental setup}: How is the equipment set up and
513 :			configured? Use diagrams and words to describe the motivate the
514 :			configuration.
515 :
516 :			\item {\bf Describe the experimental procedure}: What is it that you actually do?
517 :			How do you collect measurements?
518 :
519 :			\item {\bf Describe the results}: Use tables and graphs, along with qualitative
520 :			discussions of what happens. Make sure that you collect enough data to
521 :			support the conclusions that you will make.
522 :
523 :			\item {\bf Use of statistics to estimate uncertainty}: Statistics are a tool for
524 :			quoting results with more certainty, and also estimating the level of
525 :			uncertainty in the quoted results. Use statistics to present your
526 :			results and analyze their reliability. Be careful and realistic about
527 :			your figures, If there is uncertainty in your measurements, describe it and
528 :			estimate it. Never try to cover up uncertainty.
529 :
530 :			\item {\bf Interpret results and draw conclusions}: The final stage of an experiment
531 :			is to interpret the data that you have collected and explain any
532 :			anomalies in the results. What are the data telling you? How certain
533 :			can you be of your conclusion?
534 :			\end{itemize}
535 :
536 :
537 :
538 :			\section{The main elements}
539 :
540 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
541 :
542 :	mark	5	When reporting about an investigation, it is normal to use the following template:
543 :	mark	1	\begin{itemize}
544 :			\item {\bf Introduction}: An explanation of what the aim of the experiment
545 :			is, in your own words and opinion. Since the experiments are very open-ended,
546 :			you can choose to colour them with your own interests. Explain here what it
547 :			was you were looking for and provide an overview to the reader.
548 :
549 :			\item {\bf Method}: In this part of the report you should describe exactly
550 :			what you did. There should be enough detail to allow another person to be able
551 :			to reproduce exactly what you did and get the same results.
552 :
553 :			\item {\bf Results}: This part of the report is where you document what
554 :			actually happened. If you make measurements, you should make tables of them here
555 :			and perform any statistical analysis here. Again, the purpose of documenting
556 :			this is not to impress anyone, but to create a faithful record of what you have
557 :			observed, together with the analysis you use to draw your conclusions.
558 :			If you have written this up properly, then it should be easy to find any mistakes
559 :			that might arise.
560 :
561 :			\item {\bf Conclusions and discussion}: You should be able to state what you have discovered
562 :			in your experiment. In your conclusions you should address things like:
563 :			\begin{itemize}
564 :			\item How effective was your method?
565 :			\item How reliable are your results?
566 :			\item What is the chain of cause and effect?
567 :			\item How certain can you be of your results.
568 :			\item What is the best hypothesis to explain what happened in the experiment.
569 :			\item Criticize your own work and say what you would have done differently under other
570 :			circumstances.
571 :			\end{itemize}
572 :			\end{itemize}
573 :
574 :	mark	5	Some notes on this:
575 :
576 :			\begin{itemize}
577 :			\item You do not have to take this four-fold list as a literal structure for
578 :			your report. Sometimes it is useful to break up the report into
579 :			subsections that are organized differently. Every part of your work
580 :			should contain these four elements however.
581 :
582 :			\item {\em The point of documentation is to show critical thinking. There is
583 :	mark	1	no right or wrong answer.}
584 :
585 :	mark	5	\item Using Latex for writing your report is recommended.
586 :	mark	1
587 :	mark	5
588 :			\item Although some of you will be asked to produce corporate presentations
589 :			in your future workplace, you should not write your reports here as corporate
590 :			psychobabble. Here, we are interested in doing science, not in marketing
591 :			gimmicks.
592 :			\end{itemize}
593 :
594 :
595 :	mark	1	\section{Analysing results}
596 :
597 :			Analyzing results requires experience and a proper understanding of tools
598 :			like mathematics and statistics. In industry, one can buy all kinds of
599 :			programs that plot graphs and make nice pictures --- but how many users
600 :			of these programs actually understand what they are seeing?
601 :
602 :			The correct way to analyze results is to maintain a constant dialogue
603 :			between {\em hypothesis} and {\em observation}, being critical at all
604 :			times. Tools like statistics can be used to organize observations
605 :			logically and test the reliability of our beliefs, but there is no
606 :			substitute for scientific thinking.
607 :
608 :			\begin{itemize}
609 :			\item Tabulate raw data in appendices. Include your estimate of how much uncertainty
610 :			there is in the values that you have observed.
611 :
612 :			\item Are the data numerical or qualitative?
613 :			\begin{itemize}
614 :			\item How should they be organized?
615 :			\item What information do they provide?
616 :			\end{itemize}
617 :			\item What is the mean and standard deviation of the data?
618 :
619 :			\item What is the distribution of data about the mean?
620 :			\end{itemize}
621 :
622 :
623 :	mark	3
624 :	mark	1	\section{Your grade}
625 :
626 :			Your final grade in this course will be based on several things:
627 :			\begin{itemize}
628 :			\item The quality of your documentation.
629 :			\item How well you show scientific thinking (an enquiring mind, formulating clear hypotheses) and present your results in a critical way.
630 :			\item How well you develop sound routines for working in the lab, including
631 :			safety, tidiness and methodology. (You will be asked to present your
632 :			`best practice' working procedures to the class about half-way through the
633 :			course -- so you should be thinking constantly about how you can improve).
634 :			\end{itemize}
635 :
636 :	mark	3	\chapter{Plotting graphs}
637 :
638 :
639 :			There are many tools available for plotting graphs. An especially
640 :			powerful tool is the free software program {\tt xmgrace} (formerly
641 :			{\tt xmgr}). This tool parses files of numbers and plots them in two
642 :			dimensions. It generates output in JPEG, PNG and EPS formats, for easy
643 :			inclusion into web pages, Word or Latex documents.
644 :
645 :			\section{Xmgrace}
646 :
647 :			The program has a graphical user interface and a command-line batch mode.
648 :			Both of these are quite useful.
649 :
650 :			\begin{figure}[ht]
651 :			\begin{center}
652 :			\psfig{file=graph2.eps,width=10cm}
653 :			\caption{Figure without error bars.\label{fig1}}
654 :			\end{center}
655 :			\end{figure}
656 :
657 :			\begin{figure}[ht]
658 :	mark	4	\begin{center}
659 :			\psfig{file=graph1.eps,width=10cm}
660 :	mark	3	\caption{Figure with error bars.\label{fig2}}
661 :	mark	4	\end{center}
662 :	mark	3	\end{figure}
663 :
664 :			For example, the following graphs in fig. \ref{fig1} and fig
665 :			\ref{fig2} have been generated from a file of data that has this form:
666 :
667 :			\begin{verbatim}
668 :			1 9.669296 14.743795
669 :			2 3.836614 2.676340
670 :			3 3.513647 2.650355
671 :			4 3.907752 2.221279
672 :			5 3.606293 2.578484
673 :			6 2.923111 1.948955
674 :			7 3.180441 1.898489
675 :			8 6.231966 7.795706
676 :			9 5.284695 3.546003
677 :			10 5.774313 3.107895
678 :			11 5.222317 4.321972
679 :			12 6.515415 3.246366
680 :			13 8.258536 3.403739
681 :			14 7.499281 3.464971
682 :			15 8.041888 4.894231
683 :			...
684 :			\end{verbatim}
685 :			The graphs were generated using the commands:
686 :			\begin{verbatim}
687 :			xmgrace -settype xy www-in.xy.cfenv -hardcopy -hdevice EPS
688 :			xmgrace -settype xydy www-in.xydy.cfenv -hardcopy -hdevice EPS
689 :			\end{verbatim}
690 :			to generate Encapsulated Postscript files directly from the data,
691 :			without using the graphical interface. They could also have been
692 :			generated from the graphical interface by following the menus: Data,
693 :			Import, ASCII, (SetType) etc.
694 :
695 :			Xmgrace reads several file formats.
696 :			\begin{verbatim}
697 :			X,Y
698 :			X,Y,DY
699 :			X,Y1,Y2,Y3...
700 :			\end{verbatim}
701 :			i.e. a single line-graph with $x,y$ points, a single line with error
702 :			bars $x,y\pm dy$, or overlaid lines $x,y1,y2,...$
703 :
704 :			\section{Adding labels and legends}
705 :
706 :			A graph is not complete without a caption to explain what it is
707 :			showing, and labels on the axes. If your graph contains several lines,
708 :			it should display a legend, which explains what the different lines
709 :			are. The default is to plot lines in different colours; this can be
710 :			changed for black and white printing.
711 :
712 :			For example, suppose we read in a multiline data-set:
713 :			\begin{verbatim}
714 :			0 11.520878 46.062277 63.216033 ...
715 :			1 12.733537 47.316163 70.035250 ...
716 :			etc
717 :			\end{verbatim}
718 :			\begin{enumerate}
719 :			\item Start the program in graphical mode.
720 :			\item Select, Data, Import, ASCII.
721 :			\item In the dialogue box, remove the Filter ``*.dat'' to see all the files
722 :			in a directory.
723 :			\item Select ``Load as NXY'', select the filename and press OK. Press Cancel to get rid of the dialogue.
724 :			\item You should now see a graph like this:
725 :			\begin{figure}[ht]
726 :	mark	4	\begin{center}
727 :	mark	3	\psfig{file=ex1.eps,width=6cm}
728 :	mark	4	\end{center}
729 :	mark	3	\end{figure}
730 :			\item Select Plot, Axis properties and enter labels for the X and Y axes (press ``Apply'' for each change).
731 :
732 :			\item You should now see a graph like this:
733 :			\begin{figure}[ht]
734 :	mark	4	\begin{center}
735 :	mark	3	\psfig{file=ex2.eps,width=6cm}
736 :	mark	4	\end{center}
737 :	mark	3	\end{figure}
738 :
739 :			\item To change from colour to black and white,
740 :			select Plot, Set Appearence, and click on ``Symbols''.
741 :
742 :			Select a new colour and line style in ``Line properties''.
743 :			For each set in the ``select set'' dialogue, click and select a style.
744 :			Press ``Apply'' for each change.
745 :
746 :			\item You should now see a graph like this:
747 :			\begin{figure}[ht]
748 :	mark	4	\begin{center}
749 :	mark	3	\psfig{file=ex3.eps,width=6cm}
750 :	mark	4	\end{center}
751 :	mark	3	\end{figure}
752 :
753 :			\item To create a legend box, select Plot, Graph Appearence, Leg. box.
754 :			(This does not seem to work in some versions.)
755 :
756 :			The difficult part about the legend box is finding it! It tends to
757 :			fall off the end of the displayed area. You must specify coordinates
758 :			where it will appear. Note that the viewport coordinate range is described on
759 :			the ``Main'' tab of Graph Properties.
760 :
761 :			\end{enumerate}
762 :
763 :			If you generate postscript file, you can edit the strings in the
764 :			postscript for greater finesse.
765 :
766 :			\section{Trouble-shooting}
767 :
768 :			Problems: you might see the error message "Strings are not allowed".
769 :			This means that a non-numerical string was found in the file, where a
770 :			numerical value was expected. Check that no occurrences of ``NaN'' or
771 :			``nan'' have not come into the file, if you have generated the file
772 :			from a program.
773 :
774 :			\section{Command summary}
775 :
776 :			\begin{verbatim}
777 :			host\$ xmgrace -nxy cfenv-averages
778 :			host\$ xmgrace rootprocs.cfenv
779 :			host\$ xmgrace -settype xydy rootprocs.cfenv
780 :			host\$ xmgrace -settype xydy rootprocs.cfenv -hardcopy -hdevice JPEG
781 :			\end{verbatim}
782 :
783 :
784 :	mark	1	\chapter{Troubleshooting}
785 :
786 :			Trouble-shooting is a general skill. You can learn more about it in
787 :	mark	5	ref. \cite{burgessbook}. In this course you will develop your
788 :			trouble-shooting skills. A few hints can be borne in mind.
789 :	mark	1
790 :	mark	5	One of the important things to learn in the la is to not be afraid of
791 :			handling the equipment. If something does not work, or if you make a mistake,
792 :			you should be confident in your ability to fix the problem. If you are
793 :			afraid of making changes, you will never master the equipment.
794 :
795 :	mark	1	First of all, you should remember obvious things:
796 :			\begin{itemize}
797 :			\item Is it switched on?
798 :			\item Am I logged in as supervisor (enable)?
799 :			\item Is the cable crossed over or not?
800 :			\item Is the cable damaged?
801 :			\end{itemize}
802 :			You can amplify on certain points yourself. For instance:
803 :			\begin{itemize}
804 :			\item Be aware that not all of the equipment components work perfectly. If something is not working, try changing the component for a different one.
805 :			\item Are cables working or connected properly? Do you have the right kind of cable?
806 :			\item Are port lights active? Is the port working?
807 :			\item Are IP addresses set correctly?
808 :			\item Have you allowed several minutes for switch ARP tables to be updated? (Only then will you be able to make a connection to a router.)
809 :			\item Is there `ping' connectivity?
810 :			\item Use show/traceroute to see where problems arise.
811 :			\item Verify that configuration commands actually succeed before assuming that they have.
812 :			\end{itemize}
813 :			See the example troubleshooting diagram below. You can formulate your own
814 :			troubleshooting procedures.
815 :			\begin{figure}[ht]
816 :	mark	5	\psfig{file=troubleshoot.eps,width=13cm}
817 :	mark	1	\caption{Example troubleshooting procedure for routers.}
818 :			\end{figure}
819 :
820 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
821 :
822 :			\part{The Experiments}
823 :
824 :			\chapter{Lab Orientation}
825 :
826 :
827 :
828 :			%%%%%%%%%
829 :			\begin{expt}
830 :
831 :			The purpose of this experiment is to become familiar with the lab
832 :	mark	4	equipment and to build a number of network models, using especially
833 :			the switches that are general tools for connecting PCs into a local
834 :			area network. You will have need for these tools when building
835 :			Ethernet networks in later experiments.
836 :	mark	1
837 :	mark	4	In each case you should perform some kind of performance test and
838 :			evaluate the setup procedure you carry out so as to
839 :			compare the different solutions.
840 :
841 :			You must think of your own criteria
842 :			for comparing the parts of the experiment. Place yourself in the role
843 :			of a system administrator looking for the best solution for a large
844 :			important network. Your ability to evaluate the results of your experiment
845 :			could be vital for saving time and money.
846 :
847 :	mark	1	\begin{itemize}
848 :	mark	5	\item {\bf Estimated time}: Two weeks
849 :	mark	1	\item {\bf Preparation}: Read about VLAN.
850 :			\item {\bf Equipment}: PCs and Catalyst switches
851 :
852 :			\begin{enumerate}
853 :	mark	4	\item Catalyst or Nortel switch
854 :			\item Routing module or Juniper M7
855 :	mark	1	\end{enumerate}
856 :	mark	4
857 :	mark	1	\item {\bf How to leave the lab after session}: No configurations must be stored.
858 :			\end{itemize}
859 :			\end{expt}
860 :
861 :			In this exercise you are asked to work step by step through some simple recipes
862 :			for using the configurable LAN switches and then answer some basic questions about
863 :			LAN connectivity.
864 :
865 :			{\em This exercise is different from those that follow it, in
866 :			that we are guiding you with some specific questions.}
867 :
868 :
869 :			\section{Equipment}
870 :
871 :			\subsection{Router capabilities}
872 :
873 :			Make a brief summary of the different interfaces and capabilities of
874 :			the routers and switches in the network laboratory.
875 :
876 :			\subsection{Cable types}
877 :
878 :			Make a brief summary of the different cable types used in the network
879 :			lab, and what they are used for.
880 :
881 :			\subsection{Quick configuration}
882 :
883 :			\begin{enumerate}
884 :			\item Create scripts that can be loaded via {\tt minicom} to blank out the router configurations and to set up
885 :			new configurations. You can use the exercises from MS005A as test
886 :			examples, if you like.
887 :
888 :			\item Make brief notes on your solution. We shall discuss these solutions with all groups
889 :			in plenum.
890 :			\end{enumerate}
891 :
892 :
893 :			\subsection{Catalyst switches}
894 :
895 :			The 5509 catalyst switch contain two separate switching fabrics,
896 :			called Channel 1 and Channel 2, a supervisor engine that controls the
897 :			switching behaviour and a routing module that is used to map VLANs to
898 :			subnets. The 5513 switch does not have a routing module and hence
899 :			cannot be used to create connected VLAN subnets unless we couple a
900 :			router to it.
901 :
902 :			\subsubsection{Switching Supervisor Engine}
903 :
904 :			The first step is to establish the Console Port Connection from a PC
905 :			workstation to the switch supervisor engine.
906 :
907 :			\begin{enumerate}
908 :			\item Access the console port using the console terminal "minicom" and a special cable S3-console. Be careful -- some of the cables are crossed over and others are not. Silver ``extensions'' box-connectors can be used to crossover the cable and join cables together.
909 :
910 :			\item Turn ON the power to the switch and the console terminal.
911 :
912 :			After turning on the power to the switch and console terminal on
913 :			systems with Supervisor Engine�III, you see this initial boot-up
914 :			display:
915 :
916 :
917 :			System Power On Diagnostics
918 :			\sex
919 :			NVRAM Size..............................128KB
920 :			LED Test................................Done
921 :			ID Prom Test............................Passed
922 :			DPRAM Size..............................16KB
923 :			DPRAM Data 0x55 Test....................Passed
924 :			DPRAM Data 0xaa Test....................Passed
925 :			DPRAM Address Test......................Passed
926 :			Clearing DPRAM..........................Done
927 :			System DRAM Memory Size.................16MB
928 :			DRAM Data 0x55 Test.....................Passed
929 :			DRAM Data 0xaa Test.....................Passed
930 :			DRAM Address Test.......................Passed
931 :			Clearing DRAM...........................Done
932 :			etc..
933 :			\esex
934 :
935 :
936 :			\item At the Enter password: prompt, press Return.
937 :
938 :			\item Enter privileged mode.
939 :			\ex
940 :			enable
941 :			\eex
942 :			\item At the Enter password: prompt, press Return.
943 :
944 :
945 :			\end{enumerate}
946 :
947 :			\subsubsection{Configuring a catalyst switch}
948 :
949 :			The catalyst switches are programmable network switches. They can be
950 :			made to behave as though they were several independent switches.
951 :			An independent switch is called a VLAN, or virtual local area network.
952 :
953 :			For example, the first row of ports could be made into one VLAN and the
954 :			second row could be made into another. Alternatively, the first five
955 :			ports of the first row could be a VLAN and the rest of the switch could
956 :			be another. You can program (almost) as many VLANs as you like.
957 :
958 :			The PCs in one VLAN form a broadcast domain. Computers in VLAN1 are
959 :			all connected together and can communicate by ethernet, as usual.
960 :			Computers in VLAN1 and computers in VLAN2 cannot talk to each other by
961 :			default. They are disconnected, as if they were separate subnets. To
962 :			connect them together you must either attach a cable from a port in
963 :			VLAN1 to a port in VLAN2\footnote{There is no point in doing this,
964 :			since you could simply join the two VLANs together by reprogramming
965 :			them into a single VLAN using the switch supervisor engine.}, or you
966 :			must connect them {\em logically} using a router.
967 :
968 :			One of the catalyst switches has a router module that allows you to
969 :			create virtual router interfaces between the VLANs. The larger switch
970 :			does not have a router module, so its VLANs cannot be connected without
971 :			the help of an external router.
972 :
973 :			To create VLANs on the switch, you must be in supervisor mode (enable).
974 :			You use the command:
975 :			\begin{verbatim}
976 :			set vlan <number> <port list>
977 :			\end{verbatim}
978 :			The ports do not have to be next to one another on the switch, so we
979 :			have great flexibility of configuration.
980 :
981 :
982 :			\subsection{Nortel BayStack switch}
983 :
984 :	mark	2	The Nortel BayStack 5510 switch is a programmable layer 3 switch that
985 :			can be used to create VLANs, like the Cisco catalyst switches. Unlike
986 :			one of the Catalysts, it does not have its own routing module; if you
987 :			want to route between different VLAN subnets, you have to use the
988 :			InterSwitch Connection protocol 801.1q., otherwise known as `tagging'.
989 :	mark	1
990 :	mark	2	The Nortel switch has twenty-four copper gigabit Ethernet ports and
991 :			one optical gigabit Ethernet port (which replaces port 23). This can
992 :			be used with an optical cable to connect it to the optical port on the
993 :			Juniper M7 router. Together the Baystack and the Juniper M7 can work
994 :			as a VLAN.
995 :
996 :			The Nortel switch has a web server interface, a menu based console interface
997 :			and a command line interface. Take you pick!
998 :
999 :	mark	1	\subsection{Juniper routers}
1000 :
1001 :	mark	2	The lab has two Juniper J-series 2300 routers, each with two fast
1002 :			ethernet interfaces, and a Juniper M7i router with a single optical
1003 :			Gigabit Ethernet switch. This optical interface can be used to connect
1004 :			to the Baystack switch. Together the Baystack and the Juniper M7 can
1005 :			work as a VLAN.
1006 :	mark	1
1007 :	mark	2	The Juniper routers are modified FreeBSD machines, with specialized
1008 :			hardware. They have a web interface and a command shell, much like Unix.
1009 :			Using the command shell is very easy and is recommended. You can type ``?''
1010 :			to get help or completions at any stage.
1011 :
1012 :			Connecting to the console, you log in as root and can then type normal
1013 :			Unix commands:
1014 :			\begin{verbatim}
1015 :			root@amboeba\% ifconfig -a
1016 :			root@amboeba\% ls
1017 :			\end{verbatim}
1018 :			etc.
1019 :
1020 :			The Juniper machines have a specialized shell called the Command Line
1021 :			Interface:
1022 :			\begin{verbatim}
1023 :			root@amboeba\% cli
1024 :			root@amboeba\% ping 10.10.10.10
1025 :			\end{verbatim}
1026 :
1027 :			Once inside this, you can use ``?'' to get help. (See the example
1028 :			configurations below.)
1029 :
1030 :			The Juniper OS uses a version control system like CVS for updating
1031 :			configurations. When in configure mode, making changes to the Juniper
1032 :			configuration, nothing is changed until you type ``commit''.
1033 :
1034 :			\begin{verbatim}
1035 :			cli
1036 :			configure
1037 :			edit system root-authentication
1038 :			set plain-text-password
1039 :			set system host-name amoeba
1040 :			commit
1041 :			\end{verbatim}
1042 :
1043 :
1044 :
1045 :	mark	1	\section{Connecting computers together}
1046 :
1047 :			{\em In this section we look at how computer are connected together by
1048 :			different kinds of hardware, starting with the simplest case of a single wire.
1049 :			We look at the most basic use of the switches: as a
1050 :			smart replacement for a multi-port repeater or hub. Each port receives
1051 :			only its own frames rather than seeing every Ethernet frame on the
1052 :			LAN.}
1053 :
1054 :			\subsection{Connect two PCs together using a direct Ethernet to Ethernet connection}
1055 :
1056 :			Find a NULL modem (crossover) cable and connect two PCs directly by a cable.
1057 :			Set IP addresses and default routes to the machines using any IP address
1058 :			and network of your choice. Verify that the machines can ping one another.
1059 :
1060 :			\subsection{Connect two PCs together by a switch}
1061 :
1062 :			\begin{enumerate}
1063 :			\item Log onto the switch in supervisor mode (enable)
1064 :			\item Find two correct cables and connect the PCs to two of the switch ports (it can be any port)
1065 :			\item Make sure that the lights on the interface are green
1066 :			\item check the ports using the command
1067 :
1068 :			\ex
1069 :			show port
1070 :			show port x/y
1071 :			show vlan
1072 :
1073 :			\eex
1074 :			where x in the module and y is the port number.
1075 :
1076 :			\item Configure the PC interfaces so that they are on the same subnet
1077 :			\item Remember to create a static route from one PC to the other
1078 :
1079 :			To configure a static route for each PC address in Linux, you might need to
1080 :			set a route table entry (depending on what version of linux you are using)
1081 :			use e.g.
1082 :			\ex
1083 :			route add 222.45.3.8 eth0
1084 :			route add 222.45.3.9 eth0
1085 :			\eex
1086 :			and so on. Note that a default route is no good here, since we do not have a router.
1087 :			Modern opersting systems should be able to handle this automatically.
1088 :
1089 :			\item Show that you can ping one PC from the other
1090 :
1091 :			\end{enumerate}
1092 :
1093 :			\subsection{Showing that broadcast traffic is unrestricted with a basic switch setup}
1094 :
1095 :			\begin{enumerate}
1096 :			\item Connect a third PC to the switch and make sure that you can ping it,
1097 :			\item You might need to set a static route to each PC in order to be able to ping between arbitrary PCs.
1098 :			\item Show that you can see the packets on all PCs if you ping to 222.45.3.255 (i.e. the broadcast address)
1099 :			(Note that older versions of tcpdump do not show ICMP traffic)
1100 :			All of these tasks so far are using the default: vlan 0.
1101 :			To make more virtual LANs we must create some logical networks in the router module.
1102 :
1103 :			To log onto the router from the switch supervisor engine, type
1104 :			\ex
1105 :			> session 7
1106 :			\eex
1107 :			since the routing module is on slot 7. We then look to see what virtual interfaces are
1108 :			defined on the routing module. On a regular router, there would be an Ethernet-IP mapping
1109 :			for each interface. In the routing module, we have such a pair for each {\em virtual interface}.
1110 :			\sex
1111 :			Router>
1112 :			Router>
1113 :			Router>en
1114 :			Router#show ip arp
1115 :			Protocol Address Age (min) Hardware Addr Type Interface
1116 :			Internet 10.10.43.1 - 00d0.d3bf.cc00 ARPA Vlan43
1117 :			Internet 10.10.44.1 - 00d0.d3bf.cc00 ARPA Vlan44
1118 :			Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0
1119 :			Internet 192.16.20.60 - 00d0.d3bf.cc00 ARPA Vlan1
1120 :			\esex
1121 :			Now get rid of vlan1
1122 :
1123 :			\sex
1124 :			Router#config t
1125 :			Enter configuration commands, one per line. End with CNTL/Z.
1126 :			Router(config)#no interface vlan1
1127 :			Router(config)#no interface vlan43
1128 :			Router(config)#no interface vlan44
1129 :			CTRL-Z
1130 :			\esex
1131 :			Now we have only the default vlan0
1132 :			\sex
1133 :			Router#show ip arp
1134 :			Protocol Address Age (min) Hardware Addr Type Interface
1135 :			Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0
1136 :			\esex
1137 :			We cannot remove this vlan - it is like having no VLANs at all. i.e. we are now using the switch
1138 :			as a "smart hub" with all ports as a single LAN.
1139 :
1140 :			\end{enumerate}
1141 :
1142 :			NOTE: when creating VLANs in the Catalyst switch, you need to define the
1143 :			VLAN first in the switch before you can use them as virtual interfaces in the
1144 :			router module.
1145 :
1146 :	mark	2	\subsection{Splitting our 3 PCs into 2 connected VLANs with Cisco}
1147 :	mark	1
1148 :
1149 :			We will now place 2 of the three PCs on one vlan and the third on the
1150 :			other. Once this is done we will have separated the broadcast domains
1151 :			so that a broadcast on one VLAN does not reach the PC on the other
1152 :			Vlan.
1153 :
1154 :			A router is needed to connect together the VLANs. We configure one
1155 :			virtual interface on the router for each separate vlan. These have
1156 :			device names vlan1 vlan2 ... vlan1023. We must also configure an IP
1157 :			address for the router on each virtual interface.
1158 :
1159 :			\noindent Note: the following does not work:
1160 :
1161 :			\sex
1162 :			Router(config-if)#ip address 222.45.3.1
1163 :			\% Incomplete command.
1164 :			Router(config-if)#ip address 222.45.3.1 255.255.255.0
1165 :			Router(config-if)#interface vlan2
1166 :			Router(config-if)#
1167 :			\%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed state to d 0
1168 :			Router(config-if)#ip address 222.45.3.2 255.255.255.0
1169 :			222.45.3.0 overlaps with Vlan1
1170 :			Router(config-if)#
1171 :			\esex
1172 :			This is not allowed because the VLANs have to be on different
1173 :			subnets. This is because the router administers the separation between
1174 :			the VLANs, and its software is designed to separate traffic on subnet
1175 :			boundaries.
1176 :
1177 :			\begin{question}
1178 :			If a router can only make VLANs out of different subnets, what is the
1179 :			point of VLANs? i.e. if the different VLANs are really different
1180 :			subnets, what is the point of having a new concept for VLANs? Hint:
1181 :			how many switches and router interfaces do you need to make separate
1182 :			subnets without vlan technology? Is there new functionality? Is there
1183 :			a cost saving?
1184 :			\end{question}
1185 :
1186 :			\noindent Here is an example where we create two non-overlapping subnets on VLAN channels
1187 :			1 and 3.\footnote{Notice that we change addresses to a class B base
1188 :			network (120.45.x.x). The router software did not allow us to split a
1189 :			class C network into two subnets!}
1190 :			\sex
1191 :			Router>en
1192 :			Router#conf t
1193 :			Enter configuration commands, one per line. End with CNTL/Z.
1194 :
1195 :			Router(config)#interface vlan3
1196 :			Router(config-if)#
1197 :			\%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3, changed state to down
1198 :			Router(config-if)#
1199 :			Router(config-if)#ip address 120.45.3.129 255.255.255.128
1200 :			120.45.3.128 overlaps with Vlan2
1201 :			Router(config-if)#exit
1202 :
1203 :			Router(config)#no interface vlan2
1204 :			Router(config)#ip address 120.45.3.129 255.255.255.128
1205 :			\%LINK-5-CHANGED: Interface Vlan2,
1206 :			Router(config)#
1207 :
1208 :			Router(config)#interface vlan3
1209 :			Router(config-if)#ip address 120.45.3.129 255.255.255.128
1210 :			Router(config-if)#exit
1211 :			Router(config)#exit
1212 :			Router#
1213 :			\%SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.2)
1214 :			Router#sh ip arp
1215 :			Protocol Address Age (min) Hardware Addr Type Interface
1216 :			Internet 120.45.3.1 - 00d0.d3bf.cc00 ARPA Vlan1
1217 :			Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0
1218 :			Internet 120.45.3.129 - 00d0.d3bf.cc00 ARPA Vlan3
1219 :			\esex
1220 :
1221 :			Remember to make sure that the new virtual interfaces are
1222 :			administratively "up", by typing "no shutdown" in the router
1223 :			configuration. The command "show ip interface brief" is also useful
1224 :			for a quick summary.
1225 :
1226 :			Now connect the PCs to the switch ports, and configure them. On the
1227 :			lower subnet:
1228 :			\sex
1229 :			ifconfig eth0 120.45.3.8 netmask 255.255.255.128 broadcast 120.45.3.127
1230 :			\eex
1231 :			and on the higher subnet:
1232 :			\sex
1233 :			ifconfig eth0 120.45.3.130 netmask 255.255.255.128 broadcast 120.45.3.255
1234 :			\eex
1235 :
1236 :			After it works, you should see something like this:
1237 :
1238 :			\sex
1239 :			router#sh ip arp
1240 :			Protocol Address Age (min) Hardware Addr Type Interface
1241 :			Internet 120.45.3.1 - 00d0.d3bf.cc00 ARPA Vlan1
1242 :			Internet 120.45.3.8 0 0060.085b.65bd ARPA Vlan1
1243 :			Internet 120.45.3.9 2 000b.db4b.3e08 ARPA Vlan1
1244 :			Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0
1245 :			Internet 120.45.3.129 - 00d0.d3bf.cc00 ARPA Vlan3
1246 :			router# ping 120.45.3.8
1247 :
1248 :			Type escape sequence to abort.
1249 :			Sending 5, 100-byte ICMP Echos to 120.45.3.8, timeout is 2 seconds:
1250 :			!!!!!
1251 :			Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
1252 :
1253 :			router# ping 120.45.3.9
1254 :
1255 :			Type escape sequence to abort.
1256 :			Sending 5, 100-byte ICMP Echos to 120.45.3.9, timeout is 2 seconds:
1257 :			!!!!!
1258 :			\esex
1259 :
1260 :			\section{Security features}
1261 :
1262 :			Find out about how to restrict MAC addresses that can connect to a port.
1263 :
1264 :			\section{Remote connectivity}
1265 :
1266 :			To configure the in-band Interface (Telnet Connectivity)
1267 :
1268 :			\begin{enumerate}
1269 :			\item If you are using a local network connection to the console port, set the logical port sc0.
1270 :
1271 :			Assign the Catalyst 5000 switch IP address to a VLAN
1272 :			The switch is assigned to the same VLAN as the one containing its IP address
1273 :			\sex
1274 :			set interface sc0 up
1275 :			set interface sc0 [vlan] [ip_addr [netmask [broadcast]]]
1276 :			\esex
1277 :
1278 :			\item Configure static routes.
1279 :
1280 :			\sex
1281 :			set ip route destination gateway [metric] [primary]
1282 :			\esex
1283 :
1284 :			\item Configure a default route, if desired.
1285 :
1286 :			\sex
1287 :			set ip route default gateway [metric] [primary]
1288 :			\esex
1289 :
1290 :			\item Check the configuration status of the switch.
1291 :
1292 :			\sex
1293 :			show interface
1294 :
1295 :			\esex
1296 :
1297 :
1298 :			\item Display the route table entries of the configuration.
1299 :
1300 :			\sex
1301 :			show ip route
1302 :
1303 :			Fragmentation Redirect Unreachable
1304 :			------------- -------- -----------
1305 :			enabled enabled enabled
1306 :
1307 :			The primary gateway: 192.16.20.1
1308 :
1309 :			Destination Gateway RouteMask Flags Use Interface
1310 :			--------------- --------------- ---------- ----- -------- ---------
1311 :			default 192.16.20.1 0x0 UG 2 sc0
1312 :			192.16.20.0 192.16.20.50 0xffffff00 U 89751 sc0
1313 :
1314 :			Console> (enable) show interface
1315 :			Console> (enable)
1316 :			\esex
1317 :
1318 :			After entering the set interface sc0 up command and the set ip route command, you see this display:
1319 :
1320 :			\sex
1321 :
1322 :			Console> (enable) set interface sc0 up
1323 :			Interface sc0 administratively up.
1324 :			Console> (enable) set interface sc0 192.16.20.50 255.255.255.0
1325 :			Interface sc0 IP address and netmask set.
1326 :
1327 :			Console> (enable) show interface
1328 :			Console> (enable) show ip route
1329 :			D-Checking Port Capabilities
1330 :			\esex
1331 :
1332 :
1333 :			The show port capabilities command allows you to determine the
1334 :			capabilities of the modules and ports in a switch. This example shows
1335 :			you how to show the port capabilities for module 6, port 1:
1336 :
1337 :			\sex
1338 :			Console> show port capabilities 6/1
1339 :			Model WS-X5225R
1340 :			Port 6/1
1341 :			Type 10/100BaseTX
1342 :			Speed auto,10,100
1343 :			Duplex half,full
1344 :			Trunk encap type 802.1Q,ISL
1345 :			Trunk mode on,off,desirable,auto,nonegotiate
1346 :			Channel 6/1-2,6/1-4
1347 :			\esex
1348 :
1349 :			\end{enumerate}
1350 :
1351 :			%%%%%%%%%
1352 :
1353 :	mark	2	\section{Creating VLANs with the Nortel-Juniper collaboration.}
1354 :
1355 :			To make a VLAN with an external router, we create a series of VLAN
1356 :			broadcast domains on the Nortel switch, which overlap at a single port
1357 :			(here, the optical port 23). We enable 801.1q tagging on that port and
1358 :			set a VLAN id. All the traffic is then labelled or tagged by the
1359 :			switch and is sent via port 23 to the router. The router removes the
1360 :			tags and sends the relevant traffic to the relevant logical interface.
1361 :
1362 :			To create vlans on the Juniper M7 router, we create virtual interfaces
1363 :			with Juniper's logical interface "units", and then tag them with an
1364 :			801.1Q vlan id. First we prepare the interface for 801.1q tagging:
1365 :
1366 :			\begin{verbatim}
1367 :			root@amoeba# cli
1368 :			root@amoeba# configure
1369 :			root@amoeba# set interfaces ge-1/3/0 vlan-tagging
1370 :			\end{verbatim}
1371 :			Then we define a virtual interface for each VLAN, using the Juniper virtual ``units''.
1372 :			\begin{verbatim}
1373 :			# set interfaces ge-1/3/0 unit 0 vlan-id 0
1374 :			# set interfaces ge-1/3/0 unit 1 vlan-id 100
1375 :			# set interfaces ge-1/3/0 unit 1 family inet address 128.39.65.3/24
1376 :			# set interfaces ge-1/3/0 unit 2 vlan-id 200
1377 :			# set interfaces ge-1/3/0 unit 2 family inet address 10.10.10.10/24
1378 :			# commit
1379 :			# quit
1380 :			\end{verbatim}
1381 :
1382 :			The unit 0 interface seems to be reserved, though we have not found this in
1383 :			any documentation. Once you enable VLAN-tagging, all of the sub-interfaces
1384 :			must have a VLAN-id, even unit 0.
1385 :
1386 :			\begin{verbatim}
1387 :
1388 :			# show interfaces
1389 :
1390 :			interfaces {
1391 :			ge-1/3/0 {
1392 :			vlan-tagging;
1393 :			unit 0 {
1394 :			vlan-id 0;
1395 :			}
1396 :			}
1397 :			unit 1 {
1398 :			vlan-id 100;
1399 :			family inet {
1400 :			address 128.39.65.3/24;
1401 :			}
1402 :
1403 :			unit 2 {
1404 :			vlan-id 200;
1405 :			family inet {
1406 :			address 10.10.10.10/24;
1407 :			}
1408 :			}
1409 :			}
1410 :			}
1411 :
1412 :			\end{verbatim}
1413 :
1414 :			The router should now be ready.
1415 :
1416 :			On the Nortel Baystack, login on the console (wait for the rolling
1417 :			banner to stop!) and use the menus to configure the ports. In the
1418 :			menu system the space-bar changes a value and ENTER selects it.
1419 :
1420 :			On the main menu, choose ``Switch Configuration'', then ``VLAN
1421 :			configuration'' then ``VLAN Port Configuration''. Under this section
1422 :			you will set two things:
1423 :			\begin{itemize}
1424 :			\item AutoPVID (all ports) should be enabled.
1425 :			\item Tagging should be switched off on all ports except the trunking port (23).
1426 :			\end{itemize}
1427 :			\small
1428 :			\begin{verbatim}
1429 :			VLAN Port Configuration
1430 :
1431 :			Port: [ 1 ]
1432 :			Filter Untagged Frames: [ No ]
1433 :			Filter Unregistered Frames: [ No ]
1434 :			Port Name: [ Port 1 ]
1435 :			PVID: [ 100 ]
1436 :			Port Priority: [ 0 ]
1437 :			Tagging: [ Untag All ]
1438 :
1439 :			AutoPVID (all ports): [ Enabled ]
1440 :
1441 :			VLAN Port Configuration
1442 :
1443 :			Port: [ 23 ]
1444 :			Filter Untagged Frames: [ No ]
1445 :			Filter Unregistered Frames: [ No ]
1446 :			Port Name: [ Port 23 ]
1447 :			PVID: [ 1 ]
1448 :			Port Priority: [ 0 ]
1449 :			Tagging: [ Tag All ]
1450 :
1451 :			AutoPVID (all ports): [ Enabled ]
1452 :			\end{verbatim}
1453 :			\normalsize
1454 :			Turning on auto PVID on all ports maps the VLAN id-number to the
1455 :			port series number automatically. Now go back to the menu above and choose
1456 :			``VLAN configuration''.
1457 :			\begin{itemize}
1458 :			\item Create VLAN 100, and enable it.
1459 :			\item Create VLAN 200. and enable it.
1460 :			\end{itemize}
1461 :			Use the port membership interface to set the ports you want to belong
1462 :			to the current VLAN:
1463 :			\small
1464 :			\begin{verbatim}
1465 :			VLAN Configuration
1466 :
1467 :			Create VLAN: [ 100 ] VLAN Type: [ Port-Based ]
1468 :			Delete VLAN: [ ] Protocol Id (PID): [ None ]
1469 :			VLAN Name: [ VLAN #100 ] User-Defined PID: [ 0x0000 ]
1470 :			Management VLAN: [ No ] Now: 1 VLAN State: [ Active ]
1471 :
1472 :
1473 :			Port Membership
1474 :			1-6 7-12 13-18 19-24
1475 :			------ ------ ------ ------
1476 :
1477 :			Unit #1 ++++++ ------ ------ ----+-
1478 :
1479 :			KEY: + = A Member of This VLAN, - = Not a Member of This VLAN
1480 :			Use space bar to display choices, press <Return> or <Enter> to select choice.
1481 :			Press Ctrl-R to return to previous menu. Press Ctrl-C to return to Main Menu.
1482 :			\end{verbatim}
1483 :			\normalsize
1484 :			Note that you have to make sure the VLANs do not overlap on the ports yourself.
1485 :			Except on the trunk port (23), where they must overlap.
1486 :
1487 :
1488 :
1489 :			Note that the Nortel switch a somewhat sensitive to the order in which
1490 :			you do things. If you find that a VLAN is not working, try undefining
1491 :			or deleting the VLAN and re-defining it. Remember to turn on AutoPVID first.
1492 :			If you get stuck, you can always choose to reset the switch to factory defaults
1493 :			and start again.
1494 :
1495 :			Place one PC on VLAN 100 and another on VLAN 200, and make sure you can ping your
1496 :			way around the network.
1497 :			Remember to set the default routes on the PCs to point to the router addresses.
1498 :			Since all interfaces are local, you should not need to run a routing protocol.
1499 :			\small
1500 :			\begin{verbatim}
1501 :			pc-100# ifconfig eth0 128.39.65.77 netmask 255.255.255.0 broadcast 128.39.65.255
1502 :			pc-100# route add default gw 128.39.65.3
1503 :
1504 :			pc-200# ifconfig eth0 10.10.10.2 netmask 255.255.255.0 broadcast 10.10.10.255
1505 :			pc-200# route add default gw 10.10.10.10
1506 :
1507 :			pc100# ping 128.38.65.3
1508 :			pc100# ping 10.10.10.10
1509 :			pc100# ping 10.10.10.2
1510 :			\end{verbatim}
1511 :			\normalsize
1512 :
1513 :	mark	1
1514 :
1515 :			\chapter{Advanced routing}
1516 :
1517 :			%%%%%%%%%
1518 :			\begin{expt}
1519 :
1520 :			The purpose of this experiment is to develop your experience with
1521 :			the simplest distance vector routing protocols.
1522 :
1523 :			\begin{itemize}
1524 :			\item {\bf Estimated time}: Three weeks
1525 :			\item {\bf Preparation}: Read about
1526 :			\item {\bf Equipment}: PCs routers and switches.
1527 :			\item {\bf How to leave the lab after session}: No configurations must be stored.
1528 :			\end{itemize}
1529 :			\end{expt}
1530 :
1531 :
1532 :			This experiment starts with the scenario described in the preliminary
1533 :			course MS003A between routers in Oslo and Paris. You should not
1534 :			configure OSPF in this exercise however.
1535 :
1536 :			\section{RIP V1/V2}
1537 :
1538 :			The first part of the experiment is about the Routing Internet
1539 :			Protocol. In the course MS003A, only the basic version 1 protocol was
1540 :			discussed, but several improvements have been made to RIP that make it
1541 :			a workable solution for small network clusters.
1542 :
1543 :			You can use the text book {\em Cisco Cookbook}, chapter 6 to help you with this exercise.
1544 :
1545 :			\begin{enumerate}
1546 :
1547 :			\item Configure RIP on Paris, Oslo and Backbone and verify that RIP is up and running
1548 :			\sex
1549 :			128.39.0.0/16 is variably subnetted, 2 subnets, 2 masks
1550 :			R 128.39.0.0/16 [120/1] via 10.10.43.3, 00:00:03, Ethernet0
1551 :			10.0.0.0/24 is subnetted, 2 subnets
1552 :
1553 :			backbone#sh ip route rip
1554 :			128.39.0.0/16 is variably subnetted, 2 subnets, 2 masks
1555 :			R 128.39.0.0/16 [120/1] via 10.10.43.3, 00:00:18, FastEthernet0/0
1556 :			\esex
1557 :			This shows which route has been learned by the router.
1558 :
1559 :			RIP is a distance vector protocol which broadcasts its full
1560 :			routing table to all routers in the network. The advertised routes are
1561 :			received by all the other routers. These routers regularly update their
1562 :			forwarding tables.
1563 :
1564 :			\sex
1565 :			23:19:28: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2)
1566 :			23:19:28: network 222.45.3.0, metric 1
1567 :			23:19:28: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3)
1568 :			23:19:28: default, metric 1
1569 :			23:19:28: network 128.39.0.0, metric 2
1570 :			23:19:28: network 10.0.0.0, metric 1
1571 :			23:19:34: RIP: received v1 update from 10.10.43.3 on Ethernet0
1572 :			23:19:34: 128.39.0.0 in 1 hops
1573 :			23:19:56: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2)
1574 :			23:19:56: network 222.45.3.0, metric 1
1575 :			23:19:56: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3)
1576 :			23:19:56: default, metric 1
1577 :			23:19:56: network 128.39.0.0, metric 2
1578 :			23:19:56: network 10.0.0.0, metric 1
1579 :			23:20:04: RIP: received v1 update from 10.10.43.3 on Ethernet0
1580 :			23:20:04: 128.39.0.0 in 1 hops
1581 :			23:20:24: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2)
1582 :			23:20:24: network 222.45.3.0, metric 1
1583 :			23:20:24: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3)
1584 :			23:20:24: default, metric 1
1585 :			23:20:24: network 128.39.0.0, metric 2
1586 :			23:20:24: network 10.0.0.0, metric 1
1587 :			23:24:57: RIP: received v1 update from 10.10.43.4 on Ethernet0
1588 :			23:24:57: 0.0.0.0 in 1 hops
1589 :			23:24:57: 198.18.1.0 in 1 hops
1590 :			23:24:57: 199.19.1.0 in 1 hops
1591 :			\esex
1592 :
1593 :			\item There's a number of techniques that are used to reduce the complexity and the
1594 :			issue of large periodic broadcasting. By reading in the course texts, find out what these are and
1595 :			use them to:
1596 :			\begin{itemize}
1597 :			\item Speed up the convergence time.
1598 :			\item Reduce the bandwidth utilization on the network.
1599 :			\item Manage the network in general: i.e. specify routes, filter routes and summarize routes.
1600 :			\end{itemize}
1601 :
1602 :
1603 :			% Timers for update, route maps, filtering, triggered updates, interface-passive command, RIP authentication?
1604 :
1605 :			\item Add a loopback interface on the network with the same network as the Oslo network but a different subnet
1606 :			Show the routing summary output from RIP and explain the result you get. What is happening?
1607 :
1608 :			\item Try to prevent the updating on an interface by using a {\tt passive-interface} command.
1609 :
1610 :			\end{enumerate}
1611 :
1612 :
1613 :			\section{EIGRP - an improved RIP?}
1614 :
1615 :			You can use the text book {\em Cisco Cookbook}, chapter 7 to help you with this exercise.
1616 :
1617 :			\begin{enumerate}
1618 :
1619 :			\item Configure basic EIGRP on the network now and compare it with RIP
1620 :			Can you use the same techniques as with RIP? What is the advantage of using EIGRP instead of RIP?
1621 :			Which one would you recommend to your customer (explain your answer)?
1622 :
1623 :			\item Load balancing is the capability of a router to distribute traffic over all its network ports
1624 :			that are the same distance from the destination address. Load balancing increases
1625 :			the utilization of network segments. This means that it increases the network
1626 :			capacity. There are two types of load balancing: {\em equal cost path} and {\em unequal
1627 :			cost path}.
1628 :
1629 :			Do some reading so that you will understand how unequal cost path load
1630 :			balancing works in the Enhanced Interior Gateway Routing Protocol (EIGRP).
1631 :			Test out the flow of traffic on balanced routes, explaining what
1632 :			tools you use to make measurements.
1633 :			\end{enumerate}
1634 :
1635 :			\section{Routing loops}
1636 :
1637 :			Recall the problem of routing loops and counting to infinity.
1638 :			Several methods and techniques exist for preventing these problems:
1639 :			\begin{itemize}
1640 :			\item Split horizon: never advertise a route out of the interface through which you learned it.
1641 :			\item Poison reverse: once you learn of a route through an interface, advertise it as unreachable back through that same interface.
1642 :			\end{itemize}
1643 :			If you have time, learn about these methods and test them out.
1644 :
1645 :
1646 :			\chapter{BGP Policies and Virtual Tunnels}
1647 :
1648 :			%%%%%%%%%
1649 :			\begin{expt}
1650 :			The purpose of this experiment is to become more familiar with the
1651 :			BGP routing system and with concepts such as peering.
1652 :			\begin{itemize}
1653 :			\item {\bf Estimated time}: Three weeks
1654 :			\item {\bf Preparation}: Read about BGP and Virtual Tunnels.
1655 :			\item {\bf Equipment}: PCs routers and switches.
1656 :
1657 :
1658 :			\item {\bf How to leave the lab after session}: No configurations must be stored.
1659 :			\end{itemize}
1660 :			\end{expt}
1661 :
1662 :
1663 :
1664 :			In this experiment you must set up a network consisting of three
1665 :			autonomous systems. The underlying routing can be configured by
1666 :			any suitable method.
1667 :
1668 :			\section{Autonomous systems}
1669 :
1670 :			\begin{figure}[ht]
1671 :			\psfig{file=bgp.eps,width=12cm}
1672 :			\caption{A fragment of AS1 tunnels though AS2 in order to be contiguous with its larger parent network region.}
1673 :			\end{figure}
1674 :
1675 :			Use 2 routers in AS2 and 1 router in all the other domain fragments
1676 :			above. The two routers in AS2 should communicate with iBGP and there
1677 :			should be eBGP communication between the ASs.
1678 :
1679 :			The question in this exercise is: what happens to the smaller fragment of
1680 :			AS1 on the left hand side of the figure? Suppose that this is a branch office of
1681 :			a larger company that is geographically separate from the
1682 :			main centre. Formally, one would like the entire company to be
1683 :			identified with AS1, but the BGP believes that the routing
1684 :			domain is a convex region with a definite boundary.
1685 :
1686 :			The way one normally handles this is to create a point to point link that
1687 :			makes the two sub-regions into a convex one. This can be done by one of two methods:
1688 :			\begin{itemize}
1689 :			\item A physical point-to-point connection from the sub-region to the main region.
1690 :			\item A virtual ``tunnel'' from the sub-region to the main region.
1691 :			\end{itemize}
1692 :			Virtual tunnels are a part of the IPSec functionality, for instance.
1693 :
1694 :			Create a secure tunnel from the fragment of AS1 to the main region
1695 :			and tie them together with the underlying routing protocol.
1696 :
1697 :			\section{Peering}
1698 :
1699 :			Add a direct connection between AS1 and AS3 and
1700 :			create a peer group between AS1 and AS2 so that they share policy.
1701 :			Describe the filtering policies that you implement.
1702 :
1703 :
1704 :			\section{Configuration errors}
1705 :
1706 :			One of the problems with policy based management is that there is
1707 :			no one policing the consistency of the rules at different parts of
1708 :			the network. What happens if two ASs advertise the same routes as being
1709 :			local to themselves?
1710 :
1711 :			Use the routers to create a "black hole" in which one of the ASs
1712 :			advertises a network that it does not have. Show how this causes a
1713 :			problem for the inter-AS routing.
1714 :
1715 :			\section{Equilibration}
1716 :
1717 :			Measure how long it takes for a consistent configuration to emerge in
1718 :			the BGP network above when a change is made.
1719 :
1720 :			\chapter{Traffic Shaping and Quality of Service}
1721 :
1722 :			%%%%%%%%%
1723 :			\begin{expt}
1724 :
1725 :			The purpose of this experiment is to perform a scientific study of
1726 :			network performance under varying load. You will need to study methods
1727 :			of measurement and inquiry and plan how to proceed. You must present your
1728 :			report detailing the method, results and conclusions of your study.
1729 :			\begin{itemize}
1730 :			\item {\bf Estimated time}: Four to five weeks
1731 :			\item {\bf Preparation}: Read about measurement and scientific method. Recall exercises on frame relay. Read about traffic shaping and Quality of Service.
1732 :			\item {\bf Equipment}: PCs, routers and switches.
1733 :			\item {\bf How to leave the lab after session}: No configurations must be stored.
1734 :			\end{itemize}
1735 :			\end{expt}
1736 :
1737 :			\begin{figure}[ht]
1738 :			\psfig{file=shaping.eps,width=11cm}
1739 :			\end{figure}
1740 :
1741 :			You can use the course book {\em Cisco Cookbook}, chapter 10.1 and 10.4 etc.
1742 :			to help you here.
1743 :
1744 :			\section{Scenario 1}
1745 :
1746 :			Imagine a small group of organizations that share a connection to the
1747 :			Internet by a leased line. In this experiment you will measure the
1748 :			performance (under varying loads) of a router with multiple hosts. Set up
1749 :			a scenario for sharing the bandwidth of a trunk line that will be shared
1750 :			equally between several end hosts. Various functionality exists in IOS:
1751 :
1752 :
1753 :			\begin{itemize}
1754 :			\item Bandwidth management through rate limiting - Allows you to control the maximum rate of traffic sent or received on an interface.
1755 :			\item Traffic policing is often configured on interfaces at the edge of a network to limit traffic into or out of the network.
1756 :			\item Traffic that falls within the rate parameters is sent, whereas traffic that exceeds the parameters is dropped, or sent with a different priority.
1757 :			\item Packet marking through IP precedence, QoS group and so on.
1758 :			\end{itemize}
1759 :
1760 :			The idea of this experiment is to pick a protocol with Quality of
1761 :			Service (QoS)/traffic shaping support and compare this to a
1762 :			competitively shared medium like Ethernet. Determine how these
1763 :			different strategies compare in performance when traffic is low/high and when the
1764 :			number of users sharing the link is low/high?
1765 :
1766 :			Referring to the figure above, you might choose to create 4 virtual
1767 :			sub-interfaces on the left hand side, with four different virtual
1768 :			circuits between end nodes and the right hand side. You would then compare
1769 :			this to four Ethernet nodes connected directly by a hub or LAN switch on the
1770 :			left.
1771 :
1772 :			When planning this experiment, think of the following points:
1773 :			\begin{enumerate}
1774 :			\item You should think about the problem above and interpret it in terms of the equipment
1775 :			you have available.
1776 :			\item What protocols and data rates will you use? (10MB Ethernet, 100MB Ethernet? 56kB Frame Relay?)
1777 :			You will want to address questions like:
1778 :
1779 :			\begin{itemize}
1780 :			\item How much of the prioritized bandwidth is idle under different loads?
1781 :			\item At which points in the network will you monitor the flows of traffic?
1782 :			\item What will you use to monitor the flows? (ttcpd? show interface etc.)
1783 :			\item What will you use to generate the flows? (ttcpd, private program etc)
1784 :			\end{itemize}
1785 :
1786 :			\item You are asked, below, to find the change in behaviour of the system
1787 :			when you vary just one of many parameters that could be changed.
1788 :			Explain how you will isolate these independent channels of cause-effect.
1789 :			\end{enumerate}
1790 :
1791 :			You can not simulate the huge amounts of data that would be used in a
1792 :			real organization, so you will have to scale your experiment down to
1793 :			simulate a realistic case in the lab. Be sure to explain carefully how
1794 :			you do this.
1795 :
1796 :			In order to compare the performance of different sharing policies,
1797 :			you will have to do some thinking. We do not have an Ethernet and
1798 :			a Frame Relay connection with the same channel capacity, so you will have
1799 :			to measure the efficiencies and compare them by scaling or dividing by the
1800 :			maximum for that medium.
1801 :
1802 :			\section{Measurements}
1803 :
1804 :			Once you have designed your experiment and the system is working:
1805 :
1806 :			\begin{enumerate}
1807 :			\item Define a measure of performance for each protocol: how much of the
1808 :			potential channel capacity is being used, e.g.
1809 :
1810 :			If the total channel capacity is $C$ and we split it into 3 shares, then it should be possible
1811 :			to insert $C/3$ from each end host without problems. How much of this traffic actually arrives
1812 :			however? What happens if you try to send more than $C/3$?
1813 :
1814 :			\item How does the relative performance of the transmission vary between Ethernet and Frame Relay with the amount of traffic? i.e. as the maximum channel capacity is approached, how quickly are data sent? To be thorough, you can try both Frame Relay with and without traffic shaping limits.
1815 :
1816 :			\item How does the performance of total transmission vary with the number of users?
1817 :			\item How does the performance of each customer's transmission vary with the number of users, assuming an equal share to all?
1818 :			\end{enumerate}
1819 :
1820 :			What data will you have to record to find answers to the questions above?
1821 :			How many times must you repeat the experiments to obtain a sensible answer?
1822 :			Use elementary statistics to show how reliable your estimates are.
1823 :
1824 :
1825 :			\section{Scenario 2}
1826 :
1827 :	mark	5	Frame-relay traffic shaping can also be applied to multi-service
1828 :			links. Find out, for instance, how to do Voice over IP by connecting
1829 :			an analogue telephone to the FX ports (on those routers that have
1830 :			them).
1831 :	mark	1	\begin{enumerate}
1832 :			\item Start with configuring a frame-relay network with point to point sub-interfaces
1833 :
1834 :			\item After checking that the frame-relay is active use QoS to enable traffic shaping on the network
1835 :
1836 :			Here's a sample that show a traffic shaping configuration
1837 :
1838 :			\sex
1839 :			policy-map mypolicy
1840 :			class voice
1841 :			priority 16
1842 :			class priority-data
1843 :			bandwidth 16
1844 :			class other-data
1845 :			priority 5
1846 :
1847 :			!--- Create a policy-map and apply the bandwidth
1848 :			!--- command to a class.
1849 :
1850 :			!
1851 :			int s0/1
1852 :			encapsulation frame-relay IETF
1853 :			load-interval 30
1854 :			frame-relay traffic-shaping
1855 :
1856 :			!--- Enable Frame Relay TS.
1857 :
1858 :			!
1859 :			interface Serial0/0.1 point-to-point
1860 :			frame-relay interface-dlci 160
1861 :			class frclass
1862 :
1863 :			!--- Apply the map-class to the Frame Relay PVC.
1864 :
1865 :			!
1866 :			map-class frame-relay frclass
1867 :			service-policy output mypolicy
1868 :			frame-relay cir 64000
1869 :			frame-relay bc 640
1870 :
1871 :			!--- Apply the service-policy inside the map-class
1872 :
1873 :			\esex
1874 :
1875 :			\end{enumerate}
1876 :
1877 :
1878 :
1879 :
1880 :
1881 :
1882 :
1883 :
1884 :
1885 :			\chapter{Wireless Networking}
1886 :
1887 :			%%%%%%%%%
1888 :			\begin{expt}
1889 :
1890 :			The purpose of this experiment is to perform a scientific study of
1891 :			wireless network performance.
1892 :			\begin{itemize}
1893 :			\item {\bf Estimated time}: Two weeks
1894 :			\item {\bf Preparation}: Read about wireless transmission and security.
1895 :			\item {\bf Equipment}: PCs, routers and switches. Wireless sender.
1896 :
1897 :
1898 :			\item {\bf How to leave the lab after session}: No configurations must be stored.
1899 :			\end{itemize}
1900 :			\end{expt}
1901 :
1902 :			Imagine creating a wireless network for a small business or home.
1903 :			Set up a wireless transmitted/receiver, connected to a LAN switch and
1904 :			use a PC connected to the LAN to send and receive traffic to a mobile
1905 :			laptop PC with a network card.
1906 :
1907 :			In this exercise you will be asked to test out the physical properties
1908 :			of wireless communication. You will need to find a way to measure data
1909 :			dates and signal strength and estimate the uncertainty in your measurements.
1910 :
1911 :			\begin{itemize}
1912 :			\item Measure how far away from the source you can be.
1913 :			\item What materials shield the signal from the sender?
1914 :			\item Integrate the wireless network with the VLANs.
1915 :			\end{itemize}
1916 :
1917 :			You can investigate anything that you like, but you should at least investigate the following
1918 :			and collect data for analysis:
1919 :			\begin{enumerate}
1920 :			\item Test the wireless network by line of sight (with no walls etc in between).
1921 :			\begin{enumerate}
1922 :			\item Plot the signal strength $S$ against the inverse distance $1/d$ and its square $1/d^2$.
1923 :			\item Plot the maximum data rate against the inverse distance $1/d$ and its square $1/d^2$.
1924 :			\end{enumerate}
1925 :			Comment on the graphs that you have obtained.
1926 :
1927 :			\item Test two or three substances (walls, metals, clothing etc) for their signal shielding properties.
1928 :			Find a substance that will block transmission. Does it matter whether there are holes in the
1929 :			material? What thickness of your chosen materials will stop the signal completely (so that it
1930 :			is indistinguishable from noise)?
1931 :
1932 :			For example, try to get hold of some `chicken wire' or garden
1933 :			fencing and see whether it shields the signal from the wireless transmitter.
1934 :			\end{enumerate}
1935 :
1936 :
1937 :
1938 :
1939 :
1940 :			\chapter{VPN and IPSec}
1941 :
1942 :			%%%%%%%%%
1943 :			\begin{expt}
1944 :
1945 :			The purpose of this experiment is to explore possibilities inherent in
1946 :			IPSec and virtual tunnelling technologies.
1947 :			\begin{itemize}
1948 :			\item {\bf Estimated time}: Four weeks
1949 :			\item {\bf Preparation}: Read about security.
1950 :			\item {\bf Equipment}: PCs, routers with sufficient memory and CPU.
1951 :
1952 :
1953 :			\item {\bf How to leave the lab after session}: No configurations must be stored.
1954 :			\end{itemize}
1955 :			\end{expt}
1956 :
1957 :
1958 :
1959 :			\begin{itemize}
1960 :
1961 :			\item Software encryption:
1962 :			\begin{itemize}
1963 :			\item Cisco IOS Release 12.1(3)XI or later.
1964 :			\end{itemize}
1965 :			\item Hardware encryption.
1966 :			For the 3600 series routers, you will need
1967 :			\begin{itemize}
1968 :			\item Data encryption Advanced Integration Module (AIM)
1969 :			\item Network Module (NM) provide hardware-based encryption.
1970 :			\end{itemize}
1971 :			The data encryption AIMs and NM are hardware Layer3 (IPSec) encryption modules and provide DES and Triple DES IPSec encryption for multiple E1s of bandwidth. They also have hardware support for Diffie-Hellman, RSA, and DSA key generation.
1972 :			\end{itemize}
1973 :
1974 :			IPSEC commands on a 3660 router:
1975 :			\sex
1976 :			crypto isakmp policy 10
1977 :			hash md5
1978 :			authentication pre-share
1979 :			crypto isakmp key cisco123 address X.X.X.X
1980 :			!
1981 :			crypto ipsec transform-set myset esp-des esp-md5-hmac
1982 :			!
1983 :			crypto map mymap local-address FastEthernet0/0
1984 :			crypto map mymap 10 ipsec-isakmp
1985 :			set peer X.X.X.X
1986 :			set transform-set myset
1987 :			match address 101
1988 :			!
1989 :			interface Tunnel0
1990 :			ip address X.X.X.X 255.X.X.X
1991 :			no ip directed-broadcast
1992 :			ipx network BB
1993 :			tunnel source FastEthernet0/1
1994 :			tunnel destination X.X.X.X
1995 :			crypto map mymap
1996 :			\esex
1997 :
1998 :
1999 :
2000 :			\chapter{Virtual machines and large installation configuration}
2001 :
2002 :			\begin{expt}
2003 :
2004 :			The purpose of this experiment is to investigate the problem of managing
2005 :			a large number of computers that are networked together. Since we do not
2006 :			have a large number of computers, you will simulate them using virtual machines.
2007 :
2008 :			\begin{itemize}
2009 :			\item {\bf Estimated time}: Three weeks
2010 :			\item {\bf Preparation}: Read about User-Mode Linux and test it out. Read about getting started with cfengine.
2011 :			\item {\bf Equipment}: hosts netlab1-netlab4.
2012 :
2013 :
2014 :			\item {\bf How to leave the lab after session}: simulations can run if there are sufficient
2015 :			resources.
2016 :			\end{itemize}
2017 :			\end{expt}
2018 :
2019 :			\section{Virtual networks}
2020 :
2021 :	mark	5	You should spend a week learning how to configure User Mode Linux and
2022 :			designing a network structure, with two subnets.
2023 :	mark	1
2024 :			\section{Managing the network}
2025 :
2026 :			Once you are familiar with how to create a virtual network simulation:
2027 :			\begin{enumerate}
2028 :			\item Using User-Mode Linux, design and set up a network consisting of two different subnets
2029 :			and about fifty machines. Give your subnets different subnet masks.
2030 :
2031 :			\item Set up E-mail services, several web servers and use cfengine to manage the hosts.
2032 :
2033 :			\item Simulate the activity of users by writing scripts that create files and use up CPU and memory, and using programs like {\tt wget} to simulate
2034 :			web downloads.
2035 :
2036 :			\item You should set up cfengine to report to you as system administrator by E-mail.
2037 :			Investigate how well the cfengine management scales with numbers of machines, especially
2038 :			when files are being distributed from a central origin.
2039 :
2040 :			\item Can you make your network run on IPv6?
2041 :			\end{enumerate}
2042 :
2043 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2044 :
2045 :	mark	5
2046 :
2047 :			\chapter{Sensor monitoring}
2048 :
2049 :			\begin{expt}
2050 :
2051 :			The purpose of this experiment is to build a custom
2052 :			temperature-monitoring system and gather temperature information from
2053 :			the lab using Smartec temperature sensors. This project includes two
2054 :			parts:
2055 :
2056 :
2057 :			\begin{itemize}
2058 :			\item {\bf Estimated time}: Two weeks
2059 :			\item {\bf Preparation}: Construction, soldering, SNMP.
2060 :			\item {\bf Equipment}: hosts netlab1-netlab4.
2061 :
2062 :
2063 :			\item {\bf How to leave the lab after session}: simulations can run if there are sufficient
2064 :			resources.
2065 :			\end{itemize}
2066 :			\end{expt}
2067 :
2068 :			This project requires some basic knowledge about electrical circuits, and
2069 :			it is an advantage with some soldering experience.
2070 :
2071 :			\begin{enumerate}
2072 :			\item Assemble the temperature kit by soldering a semiconductor
2073 :			temperature sensor and the temperature acquisition board together. You
2074 :			can attach up to 4 sensor to one temperature acquisition board.
2075 :
2076 :			\item Collect the temperature data from the temperature acquisition board,
2077 :			as a time-series, and find a way to store long-term temperature
2078 :			data. Visualize the temperature development using e.g. RRDTool,
2079 :			xmgrace or gnuplot (RRDTools is recommended due to its round robin
2080 :			design!).
2081 :
2082 :			\end{enumerate}
2083 :			What is considered acceptable temperatures for the different equipment?
2084 :			How is the temperature in the racks affected by optimizing the air flow?
2085 :			What are the differences in temperature between the intake and the outtake?
2086 :
2087 :			If you have more time you can also gather all the temperature
2088 :			information on a single web page so that it can be included in the NOC*.
2089 :
2090 :			\small
2091 :			\begin{verbatim}
2092 :
2093 :			http://www.smartec.nl/temperature_kit.htm
2094 :			http://www.smartec.nl/temperature_sensor.htm
2095 :			\end{verbatim}
2096 :			\normalsize
2097 :
2098 :
2099 :
2100 :
2101 :
2102 :			\chapter{XEN Virtual machines}
2103 :
2104 :			\begin{expt}
2105 :
2106 :			The purpose of this experiment is to explore the XEN virtualization
2107 :			technology and measure the performance overhead and scalability of
2108 :			XEN virtual machines.
2109 :
2110 :			\begin{itemize}
2111 :			\item {\bf Estimated time}: Three weeks
2112 :			\item {\bf Preparation}: Read about XEN and set up some virtual machines.
2113 :			\item {\bf Equipment}: Available PCs.
2114 :
2115 :
2116 :			\item {\bf How to leave the lab after session}:
2117 :
2118 :			\end{itemize}
2119 :			\end{expt}
2120 :
2121 :			The authors of Xen claim that running a machine as a Xen domain
2122 :			instantiation only adds a worst-case overhead of 8\% and an average overhead
2123 :			of 2\%.
2124 :
2125 :			Experiment with creating, destroying, and migrating Xen domains from
2126 :			one PC to another. See how the performance worsens as the number of
2127 :			concurrent machines is increased.
2128 :
2129 :
2130 :			\small
2131 :			\begin{verbatim}
2132 :
2133 :			http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
2134 :
2135 :			http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html
2136 :
2137 :			http://www.fedoraproject.org/wiki/FedoraXenQuickstart
2138 :
2139 :			\end{verbatim}
2140 :			\normalsize
2141 :
2142 :
2143 :			\chapter{XORP router}
2144 :
2145 :			\begin{expt}
2146 :
2147 :
2148 :
2149 :			The purpose of this experiment is to build a XORP router
2150 :			and measure the performance by comparing it to Cisco and Juniper
2151 :			routers.
2152 :
2153 :			\begin{itemize}
2154 :			\item {\bf Estimated time}: Four weeks
2155 :			\item {\bf Preparation}: Read about XORP and collect the necessary equipment.
2156 :			\item {\bf Equipment}: Available PCs.
2157 :
2158 :
2159 :			\item {\bf How to leave the lab after session}:
2160 :
2161 :			\end{itemize}
2162 :			\end{expt}
2163 :
2164 :			\begin{enumerate}
2165 :
2166 :			\item Build a software router using XORP.
2167 :
2168 :			\item Perform a qualitative comparison of the functionality of the router
2169 :			with the commerical routing equipment in the lab.
2170 :
2171 :			\item Measure its performance in terms of routing table convergence and
2172 :			packet transmission rate, etc, for at least two different protocols.
2173 :
2174 :
2175 :			\item How do old and new routers compare to the XORP router?
2176 :
2177 :			\item Are there any advantages to the XORP approach over
2178 :			a dedicated commerical router?
2179 :			\end{enumerate}
2180 :
2181 :
2182 :			\chapter{Linux Terminal Server Project}
2183 :
2184 :			\begin{expt}
2185 :
2186 :
2187 :
2188 :			The purpose of this experiment is to measure the response and
2189 :			scalability of Linux running over a virtual terminal server.
2190 :			You should formulate some questions of your own.
2191 :
2192 :			\begin{itemize}
2193 :			\item {\bf Estimated time}: Three weeks
2194 :			\item {\bf Preparation}: Read about LTSP and set up some instances.
2195 :			\item {\bf Equipment}: Available PCs.
2196 :
2197 :
2198 :			\item {\bf How to leave the lab after session}:
2199 :
2200 :			\end{itemize}
2201 :			\end{expt}
2202 :
2203 :			\begin{enumerate}
2204 :			\item Build and configure a LTSP network using either LTSP or Skolelinux, with
2205 :			and at least four thin clients.
2206 :
2207 :			\item How many clients can connected at the
2208 :			same time?
2209 :
2210 :			\item How much load can a single server handle before the system
2211 :			becomes unusable (in terms of delay and "sluggishness").
2212 :
2213 :			\item What are the
2214 :			bottlenecks?
2215 :
2216 :			\item What is more important; the number of clients, or the power
2217 :			(RAM/CPU) of the server?
2218 :
2219 :			\item What about scalability? How does this solution
2220 :			compare to other comparable technologies such as RDP (Windows) and
2221 :			Nomachine?
2222 :
2223 :
2224 :			\end{enumerate}
2225 :
2226 :
2227 :	mark	1	\chapter{High availability web services}
2228 :
2229 :
2230 :
2231 :			\begin{expt}
2232 :
2233 :			The purpose of this experiment is to investigate strategies for redundant, high-volume
2234 :			network services.
2235 :
2236 :			\begin{itemize}
2237 :			\item {\bf Estimated time}: Three weeks
2238 :			\item {\bf Preparation}: Read about User-Mode Linux and test it out. Read about getting started with cfengine.
2239 :			\item {\bf Equipment}: hosts netlab1-netlab4.
2240 :
2241 :
2242 :			\item {\bf How to leave the lab after session}: simulations can run if there are sufficient
2243 :			resources.
2244 :			\end{itemize}
2245 :			\end{expt}
2246 :
2247 :			\begin{enumerate}
2248 :			\item Set up a GNU/Linux Apache web server on a relatively old (slow) PC and test its ability
2249 :			to serve files.
2250 :
2251 :			\item Investigate how the performance of the server varies with the number of pre-forked
2252 :			processes and the configuration parameter that governs the maximum number of servers.
2253 :			Measure the latency (average time to wait) and the average data rate, using tools of your own choice.
2254 :
2255 :			\item Create a load balancer that allows you to connect two PCs in parallel. How does the performance
2256 :			f this parallel configuration compare to the performance of a single machine as the same parameters
2257 :			are varied as above.
2258 :
2259 :			\item Install a Microsoft Windows 2000 Internet Information Server (IIS) and compare its
2260 :			performance with a single Apache server on Linux, on the same hardware. Compare the performance
2261 :			of the servers, the latency and the scalability of these two solutions. Can you say whether one or the
2262 :			other is ``better''?
2263 :
2264 :			\item Suggest a design for a high volume server.
2265 :			\end{enumerate}
2266 :
2267 :
2268 :
2269 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2270 :
2271 :	mark	4	\chapter{Disk and RAID performance}
2272 :	mark	1
2273 :
2274 :			\begin{expt}
2275 :
2276 :	mark	4	The purpose of this experiment is to investigate the performance of
2277 :			ATA (IDE) and SCSI disks under different loads and to test the
2278 :			performance penalty for using RAID solutions. You should design an
2279 :			experiment to stress test these technologies under single and
2280 :			multi-user access.
2281 :	mark	1
2282 :			\begin{itemize}
2283 :			\item {\bf Estimated time}: Two to three weeks
2284 :			\item {\bf Preparation}: Read about ATA (IDE) and SCSI disks, their strengths and weaknesses.
2285 :			\item {\bf Equipment}: Anything you can get your hands on!
2286 :
2287 :			\item {\bf How to leave the lab after session}: Equipment should be tidied but may be labelled
2288 :			or reserved for the group.
2289 :			\end{itemize}
2290 :			\end{expt}
2291 :
2292 :			Design your own experiment to measure the performance of a disk.
2293 :			\begin{itemize}
2294 :			\item Consider what it is that you will measure.
2295 :			\item What tools will you use?
2296 :			\item What hypotheses will you form and test?
2297 :			\item How will you organize and analyze your data?
2298 :			\item How will you arrange to test the disks to their limits?
2299 :			\item How does performance change as load increases? Using current prices, work out the
2300 :			performance of each disk per price/MB.
2301 :
2302 :			\item Using any tools that you can find, format a new disk (filesystem) and write some
2303 :			recognizable data to it. Then delete all of the files. Using tools of your choice,
2304 :			see how much of the data you are able to recover from the disk.
2305 :			\end{itemize}
2306 :
2307 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2308 :
2309 :	mark	5	\chapter{SNMP and Network Operations Centre}
2310 :	mark	1
2311 :			The Simple Network Management Protocol is an important technology for network
2312 :			devices. This experiment asks you to learn about its use.
2313 :	mark	5
2314 :	mark	1	\begin{expt}
2315 :
2316 :			The purpose of this experiment is to investigate investigate some of the characteristics
2317 :			of the Simple Network Management Protocol.
2318 :
2319 :			\begin{itemize}
2320 :			\item {\bf Estimated time}: One to two weeks
2321 :			\item {\bf Preparation}: Read about SNMP and monitoring on the web.
2322 :			\item {\bf Equipment}: Any.
2323 :
2324 :
2325 :			\item {\bf How to leave the lab after session}: software etc. must be removed once
2326 :			the experiment is over.
2327 :
2328 :			\end{itemize}
2329 :			\end{expt}
2330 :
2331 :			When using the SNMP tools below, use a program like {\tt tcpdump} to show the
2332 :			traffic that passes between your console and the devices. In your final report,
2333 :			you should comment on the overhead incurred by SNMP.
2334 :
2335 :			\begin{enumerate}
2336 :			\item Find out whether you need to enable SNMP services on routers and switches.
2337 :			\item Write a PHP or Perl script that queries SNMP data from a printer.
2338 :			\item Locate, download and compile the {\tt scli} tool.
2339 :			\item Locate MRTG noting that this might be already installed on the machine
2340 :			you are using. Install it and get it running. Show how it generates plots of traffic activity.
2341 :			\item Investigate using the {\tt scli} tool to configure routers and switches.
2342 :			\end{enumerate}
2343 :
2344 :
2345 :	mark	5	\small
2346 :			\begin{verbatim}
2347 :	mark	1
2348 :	mark	5	http://www.emeapress.att.com/library/images/att_noc_01.jpg
2349 :	mark	1
2350 :	mark	5	http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/
2351 :	mark	1
2352 :	mark	5	http://php.net
2353 :			\end{verbatim}
2354 :			\normalsize
2355 :	mark	1
2356 :
2357 :
2358 :
2359 :	mark	5
2360 :			%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2361 :
2362 :			\chapter{Miscellaneous}
2363 :
2364 :
2365 :	mark	1	You are free to suggest your own experiments for the laboratory.
2366 :			You will gain course credit as long as the course instructors have approved
2367 :			the plan. An experiment should start by asking a question and should contain
2368 :			a degree of analysis.
2369 :			\begin{itemize}
2370 :			\item What is your hypothesis?
2371 :			\item How will you test it critically? (You should not set out to prove a hypothesis, bust rather to disprove it!)
2372 :			\end{itemize}
2373 :			Suggested topics:
2374 :			\begin{itemize}
2375 :			\item Novell/Windows integration.
2376 :			\item Cfengine on windows.
2377 :			\item Compare OSPF routing with IS-IS routing.
2378 :			\item Dialup services.
2379 :			\item Compare difference operating systems.
2380 :			\item IP Telephony.
2381 :	mark	5	\item Dummynet and traffic shaping with freebsd.
2382 :	mark	1	\end{itemize}
2383 :
2384 :	mark	5
2385 :
2386 :	mark	1	\bibliography{LISAbib}
2387 :
2388 :			\end{document}

Administrator	ViewVC Help
Powered by ViewVC 1.0.3