Annotation of /trunk/lab.tex

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

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

Administrator	ViewVC Help
Powered by ViewVC 1.0.3