Parent Directory
| 
Revision Log
Revision 1 - (view) (download) (as text)
| 1 : | mark | 1 | \documentclass{book} |
| 2 : | |||
| 3 : | \author{Oslo University College, Norway\\~\\Mark Burgess and Assi Gueye} | ||
| 4 : | \title{Network Infrastructure and Security Laboratory Workbook\\Version 2.1} | ||
| 5 : | \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 : | (to appear) | ||
| 795 : | |||
| 796 : | \subsection{Juniper routers} | ||
| 797 : | |||
| 798 : | (to appear) | ||
| 799 : | |||
| 800 : | \section{Connecting computers together} | ||
| 801 : | |||
| 802 : | {\em In this section we look at how computer are connected together by | ||
| 803 : | different kinds of hardware, starting with the simplest case of a single wire. | ||
| 804 : | We look at the most basic use of the switches: as a | ||
| 805 : | smart replacement for a multi-port repeater or hub. Each port receives | ||
| 806 : | only its own frames rather than seeing every Ethernet frame on the | ||
| 807 : | LAN.} | ||
| 808 : | |||
| 809 : | \subsection{Connect two PCs together using a direct Ethernet to Ethernet connection} | ||
| 810 : | |||
| 811 : | Find a NULL modem (crossover) cable and connect two PCs directly by a cable. | ||
| 812 : | Set IP addresses and default routes to the machines using any IP address | ||
| 813 : | and network of your choice. Verify that the machines can ping one another. | ||
| 814 : | |||
| 815 : | \subsection{Connect two PCs together by a switch} | ||
| 816 : | |||
| 817 : | \begin{enumerate} | ||
| 818 : | \item Log onto the switch in supervisor mode (enable) | ||
| 819 : | \item Find two correct cables and connect the PCs to two of the switch ports (it can be any port) | ||
| 820 : | \item Make sure that the lights on the interface are green | ||
| 821 : | \item check the ports using the command | ||
| 822 : | |||
| 823 : | \ex | ||
| 824 : | show port | ||
| 825 : | show port x/y | ||
| 826 : | show vlan | ||
| 827 : | |||
| 828 : | \eex | ||
| 829 : | where x in the module and y is the port number. | ||
| 830 : | |||
| 831 : | \item Configure the PC interfaces so that they are on the same subnet | ||
| 832 : | \item Remember to create a static route from one PC to the other | ||
| 833 : | |||
| 834 : | To configure a static route for each PC address in Linux, you might need to | ||
| 835 : | set a route table entry (depending on what version of linux you are using) | ||
| 836 : | use e.g. | ||
| 837 : | \ex | ||
| 838 : | route add 222.45.3.8 eth0 | ||
| 839 : | route add 222.45.3.9 eth0 | ||
| 840 : | \eex | ||
| 841 : | and so on. Note that a default route is no good here, since we do not have a router. | ||
| 842 : | Modern opersting systems should be able to handle this automatically. | ||
| 843 : | |||
| 844 : | \item Show that you can ping one PC from the other | ||
| 845 : | |||
| 846 : | \end{enumerate} | ||
| 847 : | |||
| 848 : | \subsection{Showing that broadcast traffic is unrestricted with a basic switch setup} | ||
| 849 : | |||
| 850 : | \begin{enumerate} | ||
| 851 : | \item Connect a third PC to the switch and make sure that you can ping it, | ||
| 852 : | \item You might need to set a static route to each PC in order to be able to ping between arbitrary PCs. | ||
| 853 : | \item Show that you can see the packets on all PCs if you ping to 222.45.3.255 (i.e. the broadcast address) | ||
| 854 : | (Note that older versions of tcpdump do not show ICMP traffic) | ||
| 855 : | All of these tasks so far are using the default: vlan 0. | ||
| 856 : | To make more virtual LANs we must create some logical networks in the router module. | ||
| 857 : | |||
| 858 : | To log onto the router from the switch supervisor engine, type | ||
| 859 : | \ex | ||
| 860 : | > session 7 | ||
| 861 : | \eex | ||
| 862 : | since the routing module is on slot 7. We then look to see what virtual interfaces are | ||
| 863 : | defined on the routing module. On a regular router, there would be an Ethernet-IP mapping | ||
| 864 : | for each interface. In the routing module, we have such a pair for each {\em virtual interface}. | ||
| 865 : | \sex | ||
| 866 : | Router> | ||
| 867 : | Router> | ||
| 868 : | Router>en | ||
| 869 : | Router#show ip arp | ||
| 870 : | Protocol Address Age (min) Hardware Addr Type Interface | ||
| 871 : | Internet 10.10.43.1 - 00d0.d3bf.cc00 ARPA Vlan43 | ||
| 872 : | Internet 10.10.44.1 - 00d0.d3bf.cc00 ARPA Vlan44 | ||
| 873 : | Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0 | ||
| 874 : | Internet 192.16.20.60 - 00d0.d3bf.cc00 ARPA Vlan1 | ||
| 875 : | \esex | ||
| 876 : | Now get rid of vlan1 | ||
| 877 : | |||
| 878 : | \sex | ||
| 879 : | Router#config t | ||
| 880 : | Enter configuration commands, one per line. End with CNTL/Z. | ||
| 881 : | Router(config)#no interface vlan1 | ||
| 882 : | Router(config)#no interface vlan43 | ||
| 883 : | Router(config)#no interface vlan44 | ||
| 884 : | CTRL-Z | ||
| 885 : | \esex | ||
| 886 : | Now we have only the default vlan0 | ||
| 887 : | \sex | ||
| 888 : | Router#show ip arp | ||
| 889 : | Protocol Address Age (min) Hardware Addr Type Interface | ||
| 890 : | Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0 | ||
| 891 : | \esex | ||
| 892 : | We cannot remove this vlan - it is like having no VLANs at all. i.e. we are now using the switch | ||
| 893 : | as a "smart hub" with all ports as a single LAN. | ||
| 894 : | |||
| 895 : | \end{enumerate} | ||
| 896 : | |||
| 897 : | NOTE: when creating VLANs in the Catalyst switch, you need to define the | ||
| 898 : | VLAN first in the switch before you can use them as virtual interfaces in the | ||
| 899 : | router module. | ||
| 900 : | |||
| 901 : | \subsection{Splitting our 3 PCs into 2 connected VLANs} | ||
| 902 : | |||
| 903 : | |||
| 904 : | We will now place 2 of the three PCs on one vlan and the third on the | ||
| 905 : | other. Once this is done we will have separated the broadcast domains | ||
| 906 : | so that a broadcast on one VLAN does not reach the PC on the other | ||
| 907 : | Vlan. | ||
| 908 : | |||
| 909 : | A router is needed to connect together the VLANs. We configure one | ||
| 910 : | virtual interface on the router for each separate vlan. These have | ||
| 911 : | device names vlan1 vlan2 ... vlan1023. We must also configure an IP | ||
| 912 : | address for the router on each virtual interface. | ||
| 913 : | |||
| 914 : | \noindent Note: the following does not work: | ||
| 915 : | |||
| 916 : | \sex | ||
| 917 : | Router(config-if)#ip address 222.45.3.1 | ||
| 918 : | \% Incomplete command. | ||
| 919 : | Router(config-if)#ip address 222.45.3.1 255.255.255.0 | ||
| 920 : | Router(config-if)#interface vlan2 | ||
| 921 : | Router(config-if)# | ||
| 922 : | \%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed state to d 0 | ||
| 923 : | Router(config-if)#ip address 222.45.3.2 255.255.255.0 | ||
| 924 : | 222.45.3.0 overlaps with Vlan1 | ||
| 925 : | Router(config-if)# | ||
| 926 : | \esex | ||
| 927 : | This is not allowed because the VLANs have to be on different | ||
| 928 : | subnets. This is because the router administers the separation between | ||
| 929 : | the VLANs, and its software is designed to separate traffic on subnet | ||
| 930 : | boundaries. | ||
| 931 : | |||
| 932 : | \begin{question} | ||
| 933 : | If a router can only make VLANs out of different subnets, what is the | ||
| 934 : | point of VLANs? i.e. if the different VLANs are really different | ||
| 935 : | subnets, what is the point of having a new concept for VLANs? Hint: | ||
| 936 : | how many switches and router interfaces do you need to make separate | ||
| 937 : | subnets without vlan technology? Is there new functionality? Is there | ||
| 938 : | a cost saving? | ||
| 939 : | \end{question} | ||
| 940 : | |||
| 941 : | \noindent Here is an example where we create two non-overlapping subnets on VLAN channels | ||
| 942 : | 1 and 3.\footnote{Notice that we change addresses to a class B base | ||
| 943 : | network (120.45.x.x). The router software did not allow us to split a | ||
| 944 : | class C network into two subnets!} | ||
| 945 : | \sex | ||
| 946 : | Router>en | ||
| 947 : | Router#conf t | ||
| 948 : | Enter configuration commands, one per line. End with CNTL/Z. | ||
| 949 : | |||
| 950 : | Router(config)#interface vlan3 | ||
| 951 : | Router(config-if)# | ||
| 952 : | \%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3, changed state to down | ||
| 953 : | Router(config-if)# | ||
| 954 : | Router(config-if)#ip address 120.45.3.129 255.255.255.128 | ||
| 955 : | 120.45.3.128 overlaps with Vlan2 | ||
| 956 : | Router(config-if)#exit | ||
| 957 : | |||
| 958 : | Router(config)#no interface vlan2 | ||
| 959 : | Router(config)#ip address 120.45.3.129 255.255.255.128 | ||
| 960 : | \%LINK-5-CHANGED: Interface Vlan2, | ||
| 961 : | Router(config)# | ||
| 962 : | |||
| 963 : | Router(config)#interface vlan3 | ||
| 964 : | Router(config-if)#ip address 120.45.3.129 255.255.255.128 | ||
| 965 : | Router(config-if)#exit | ||
| 966 : | Router(config)#exit | ||
| 967 : | Router# | ||
| 968 : | \%SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.2) | ||
| 969 : | Router#sh ip arp | ||
| 970 : | Protocol Address Age (min) Hardware Addr Type Interface | ||
| 971 : | Internet 120.45.3.1 - 00d0.d3bf.cc00 ARPA Vlan1 | ||
| 972 : | Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0 | ||
| 973 : | Internet 120.45.3.129 - 00d0.d3bf.cc00 ARPA Vlan3 | ||
| 974 : | \esex | ||
| 975 : | |||
| 976 : | Remember to make sure that the new virtual interfaces are | ||
| 977 : | administratively "up", by typing "no shutdown" in the router | ||
| 978 : | configuration. The command "show ip interface brief" is also useful | ||
| 979 : | for a quick summary. | ||
| 980 : | |||
| 981 : | Now connect the PCs to the switch ports, and configure them. On the | ||
| 982 : | lower subnet: | ||
| 983 : | \sex | ||
| 984 : | ifconfig eth0 120.45.3.8 netmask 255.255.255.128 broadcast 120.45.3.127 | ||
| 985 : | \eex | ||
| 986 : | and on the higher subnet: | ||
| 987 : | \sex | ||
| 988 : | ifconfig eth0 120.45.3.130 netmask 255.255.255.128 broadcast 120.45.3.255 | ||
| 989 : | \eex | ||
| 990 : | |||
| 991 : | After it works, you should see something like this: | ||
| 992 : | |||
| 993 : | \sex | ||
| 994 : | router#sh ip arp | ||
| 995 : | Protocol Address Age (min) Hardware Addr Type Interface | ||
| 996 : | Internet 120.45.3.1 - 00d0.d3bf.cc00 ARPA Vlan1 | ||
| 997 : | Internet 120.45.3.8 0 0060.085b.65bd ARPA Vlan1 | ||
| 998 : | Internet 120.45.3.9 2 000b.db4b.3e08 ARPA Vlan1 | ||
| 999 : | Internet 127.0.0.2 - 00d0.97e9.93ff ARPA Vlan0 | ||
| 1000 : | Internet 120.45.3.129 - 00d0.d3bf.cc00 ARPA Vlan3 | ||
| 1001 : | router# ping 120.45.3.8 | ||
| 1002 : | |||
| 1003 : | Type escape sequence to abort. | ||
| 1004 : | Sending 5, 100-byte ICMP Echos to 120.45.3.8, timeout is 2 seconds: | ||
| 1005 : | !!!!! | ||
| 1006 : | Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms | ||
| 1007 : | |||
| 1008 : | router# ping 120.45.3.9 | ||
| 1009 : | |||
| 1010 : | Type escape sequence to abort. | ||
| 1011 : | Sending 5, 100-byte ICMP Echos to 120.45.3.9, timeout is 2 seconds: | ||
| 1012 : | !!!!! | ||
| 1013 : | \esex | ||
| 1014 : | |||
| 1015 : | \section{Security features} | ||
| 1016 : | |||
| 1017 : | Find out about how to restrict MAC addresses that can connect to a port. | ||
| 1018 : | |||
| 1019 : | \section{Remote connectivity} | ||
| 1020 : | |||
| 1021 : | To configure the in-band Interface (Telnet Connectivity) | ||
| 1022 : | |||
| 1023 : | \begin{enumerate} | ||
| 1024 : | \item If you are using a local network connection to the console port, set the logical port sc0. | ||
| 1025 : | |||
| 1026 : | Assign the Catalyst 5000 switch IP address to a VLAN | ||
| 1027 : | The switch is assigned to the same VLAN as the one containing its IP address | ||
| 1028 : | \sex | ||
| 1029 : | set interface sc0 up | ||
| 1030 : | set interface sc0 [vlan] [ip_addr [netmask [broadcast]]] | ||
| 1031 : | \esex | ||
| 1032 : | |||
| 1033 : | \item Configure static routes. | ||
| 1034 : | |||
| 1035 : | \sex | ||
| 1036 : | set ip route destination gateway [metric] [primary] | ||
| 1037 : | \esex | ||
| 1038 : | |||
| 1039 : | \item Configure a default route, if desired. | ||
| 1040 : | |||
| 1041 : | \sex | ||
| 1042 : | set ip route default gateway [metric] [primary] | ||
| 1043 : | \esex | ||
| 1044 : | |||
| 1045 : | \item Check the configuration status of the switch. | ||
| 1046 : | |||
| 1047 : | \sex | ||
| 1048 : | show interface | ||
| 1049 : | |||
| 1050 : | \esex | ||
| 1051 : | |||
| 1052 : | |||
| 1053 : | \item Display the route table entries of the configuration. | ||
| 1054 : | |||
| 1055 : | \sex | ||
| 1056 : | show ip route | ||
| 1057 : | |||
| 1058 : | Fragmentation Redirect Unreachable | ||
| 1059 : | ------------- -------- ----------- | ||
| 1060 : | enabled enabled enabled | ||
| 1061 : | |||
| 1062 : | The primary gateway: 192.16.20.1 | ||
| 1063 : | |||
| 1064 : | Destination Gateway RouteMask Flags Use Interface | ||
| 1065 : | --------------- --------------- ---------- ----- -------- --------- | ||
| 1066 : | default 192.16.20.1 0x0 UG 2 sc0 | ||
| 1067 : | 192.16.20.0 192.16.20.50 0xffffff00 U 89751 sc0 | ||
| 1068 : | |||
| 1069 : | Console> (enable) show interface | ||
| 1070 : | Console> (enable) | ||
| 1071 : | \esex | ||
| 1072 : | |||
| 1073 : | After entering the set interface sc0 up command and the set ip route command, you see this display: | ||
| 1074 : | |||
| 1075 : | \sex | ||
| 1076 : | |||
| 1077 : | Console> (enable) set interface sc0 up | ||
| 1078 : | Interface sc0 administratively up. | ||
| 1079 : | Console> (enable) set interface sc0 192.16.20.50 255.255.255.0 | ||
| 1080 : | Interface sc0 IP address and netmask set. | ||
| 1081 : | |||
| 1082 : | Console> (enable) show interface | ||
| 1083 : | Console> (enable) show ip route | ||
| 1084 : | D-Checking Port Capabilities | ||
| 1085 : | \esex | ||
| 1086 : | |||
| 1087 : | |||
| 1088 : | The show port capabilities command allows you to determine the | ||
| 1089 : | capabilities of the modules and ports in a switch. This example shows | ||
| 1090 : | you how to show the port capabilities for module 6, port 1: | ||
| 1091 : | |||
| 1092 : | \sex | ||
| 1093 : | Console> show port capabilities 6/1 | ||
| 1094 : | Model WS-X5225R | ||
| 1095 : | Port 6/1 | ||
| 1096 : | Type 10/100BaseTX | ||
| 1097 : | Speed auto,10,100 | ||
| 1098 : | Duplex half,full | ||
| 1099 : | Trunk encap type 802.1Q,ISL | ||
| 1100 : | Trunk mode on,off,desirable,auto,nonegotiate | ||
| 1101 : | Channel 6/1-2,6/1-4 | ||
| 1102 : | \esex | ||
| 1103 : | |||
| 1104 : | \end{enumerate} | ||
| 1105 : | |||
| 1106 : | %%%%%%%%% | ||
| 1107 : | |||
| 1108 : | \chapter{The Local Area Network} | ||
| 1109 : | |||
| 1110 : | %%%%%%%%% | ||
| 1111 : | \begin{expt} | ||
| 1112 : | |||
| 1113 : | The purpose of this experiment is to become familiar with the Catalyst switches | ||
| 1114 : | that can be used to connect PCs into a local area network. You will have | ||
| 1115 : | need for these tools when building Ethernet networks. | ||
| 1116 : | \begin{itemize} | ||
| 1117 : | \item {\bf Estimated time}: Two weeks | ||
| 1118 : | \item {\bf Preparation}: Experiment 1 | ||
| 1119 : | \item {\bf Equipment}: PCs, routers and switches. | ||
| 1120 : | |||
| 1121 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1122 : | \end{itemize} | ||
| 1123 : | \end{expt} | ||
| 1124 : | |||
| 1125 : | You might wish you begin by reproducing the experiments from the course | ||
| 1126 : | Networking Principles and Technologies (MS003A) from scratch. | ||
| 1127 : | |||
| 1128 : | \section{Virtual LAN or Subnets?} | ||
| 1129 : | |||
| 1130 : | Imagine a small organization with a number of networks. You have two | ||
| 1131 : | possibilities for partitioning the network into different regions, | ||
| 1132 : | with separate broadcast domains: physically separate subnets or | ||
| 1133 : | logically separate subnets (Virtual LAN/VLAN). This experiment is | ||
| 1134 : | about measuring the difference between switched networks, routed | ||
| 1135 : | networks and Virtual LAN networks, both with regard to performance and | ||
| 1136 : | security. | ||
| 1137 : | |||
| 1138 : | Set up a network with at least two different subnets and at least two hosts | ||
| 1139 : | on each subnet. You should set up the network in three different ways, with | ||
| 1140 : | (as far as possible) the same functionality. | ||
| 1141 : | |||
| 1142 : | \begin{enumerate} | ||
| 1143 : | \item All hosts connected to the router by hubs inside their subnet. | ||
| 1144 : | \item All hosts connected to the router by switch inside their subnet. | ||
| 1145 : | \item All hosts connected to the switch with VLAN partitions. | ||
| 1146 : | \end{enumerate} | ||
| 1147 : | When you have constructed each network, as yourself: | ||
| 1148 : | \begin{itemize} | ||
| 1149 : | \item Where are the broadcast domains? | ||
| 1150 : | \item Where are Ethernet frames originating from each host visible? | ||
| 1151 : | \item Estimate the relative cost or burden, in time, of managing and maintaining the network. | ||
| 1152 : | \item Estimate what is the relative financial cost of implementing these solutions for a small company? | ||
| 1153 : | \end{itemize} | ||
| 1154 : | Base you estimates of the cost on traffic predictions. How do the solutions | ||
| 1155 : | scale with increasing traffic? | ||
| 1156 : | |||
| 1157 : | \chapter{Advanced routing} | ||
| 1158 : | |||
| 1159 : | %%%%%%%%% | ||
| 1160 : | \begin{expt} | ||
| 1161 : | |||
| 1162 : | The purpose of this experiment is to develop your experience with | ||
| 1163 : | the simplest distance vector routing protocols. | ||
| 1164 : | |||
| 1165 : | \begin{itemize} | ||
| 1166 : | \item {\bf Estimated time}: Three weeks | ||
| 1167 : | \item {\bf Preparation}: Read about | ||
| 1168 : | \item {\bf Equipment}: PCs routers and switches. | ||
| 1169 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1170 : | \end{itemize} | ||
| 1171 : | \end{expt} | ||
| 1172 : | |||
| 1173 : | |||
| 1174 : | This experiment starts with the scenario described in the preliminary | ||
| 1175 : | course MS003A between routers in Oslo and Paris. You should not | ||
| 1176 : | configure OSPF in this exercise however. | ||
| 1177 : | |||
| 1178 : | \section{RIP V1/V2} | ||
| 1179 : | |||
| 1180 : | The first part of the experiment is about the Routing Internet | ||
| 1181 : | Protocol. In the course MS003A, only the basic version 1 protocol was | ||
| 1182 : | discussed, but several improvements have been made to RIP that make it | ||
| 1183 : | a workable solution for small network clusters. | ||
| 1184 : | |||
| 1185 : | You can use the text book {\em Cisco Cookbook}, chapter 6 to help you with this exercise. | ||
| 1186 : | |||
| 1187 : | \begin{enumerate} | ||
| 1188 : | |||
| 1189 : | \item Configure RIP on Paris, Oslo and Backbone and verify that RIP is up and running | ||
| 1190 : | \sex | ||
| 1191 : | 128.39.0.0/16 is variably subnetted, 2 subnets, 2 masks | ||
| 1192 : | R 128.39.0.0/16 [120/1] via 10.10.43.3, 00:00:03, Ethernet0 | ||
| 1193 : | 10.0.0.0/24 is subnetted, 2 subnets | ||
| 1194 : | |||
| 1195 : | backbone#sh ip route rip | ||
| 1196 : | 128.39.0.0/16 is variably subnetted, 2 subnets, 2 masks | ||
| 1197 : | R 128.39.0.0/16 [120/1] via 10.10.43.3, 00:00:18, FastEthernet0/0 | ||
| 1198 : | \esex | ||
| 1199 : | This shows which route has been learned by the router. | ||
| 1200 : | |||
| 1201 : | RIP is a distance vector protocol which broadcasts its full | ||
| 1202 : | routing table to all routers in the network. The advertised routes are | ||
| 1203 : | received by all the other routers. These routers regularly update their | ||
| 1204 : | forwarding tables. | ||
| 1205 : | |||
| 1206 : | \sex | ||
| 1207 : | 23:19:28: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2) | ||
| 1208 : | 23:19:28: network 222.45.3.0, metric 1 | ||
| 1209 : | 23:19:28: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3) | ||
| 1210 : | 23:19:28: default, metric 1 | ||
| 1211 : | 23:19:28: network 128.39.0.0, metric 2 | ||
| 1212 : | 23:19:28: network 10.0.0.0, metric 1 | ||
| 1213 : | 23:19:34: RIP: received v1 update from 10.10.43.3 on Ethernet0 | ||
| 1214 : | 23:19:34: 128.39.0.0 in 1 hops | ||
| 1215 : | 23:19:56: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2) | ||
| 1216 : | 23:19:56: network 222.45.3.0, metric 1 | ||
| 1217 : | 23:19:56: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3) | ||
| 1218 : | 23:19:56: default, metric 1 | ||
| 1219 : | 23:19:56: network 128.39.0.0, metric 2 | ||
| 1220 : | 23:19:56: network 10.0.0.0, metric 1 | ||
| 1221 : | 23:20:04: RIP: received v1 update from 10.10.43.3 on Ethernet0 | ||
| 1222 : | 23:20:04: 128.39.0.0 in 1 hops | ||
| 1223 : | 23:20:24: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (10.10.43.2) | ||
| 1224 : | 23:20:24: network 222.45.3.0, metric 1 | ||
| 1225 : | 23:20:24: RIP: sending v1 update to 255.255.255.255 via FastEthernet0 (222.45.3) | ||
| 1226 : | 23:20:24: default, metric 1 | ||
| 1227 : | 23:20:24: network 128.39.0.0, metric 2 | ||
| 1228 : | 23:20:24: network 10.0.0.0, metric 1 | ||
| 1229 : | 23:24:57: RIP: received v1 update from 10.10.43.4 on Ethernet0 | ||
| 1230 : | 23:24:57: 0.0.0.0 in 1 hops | ||
| 1231 : | 23:24:57: 198.18.1.0 in 1 hops | ||
| 1232 : | 23:24:57: 199.19.1.0 in 1 hops | ||
| 1233 : | \esex | ||
| 1234 : | |||
| 1235 : | \item There's a number of techniques that are used to reduce the complexity and the | ||
| 1236 : | issue of large periodic broadcasting. By reading in the course texts, find out what these are and | ||
| 1237 : | use them to: | ||
| 1238 : | \begin{itemize} | ||
| 1239 : | \item Speed up the convergence time. | ||
| 1240 : | \item Reduce the bandwidth utilization on the network. | ||
| 1241 : | \item Manage the network in general: i.e. specify routes, filter routes and summarize routes. | ||
| 1242 : | \end{itemize} | ||
| 1243 : | |||
| 1244 : | |||
| 1245 : | % Timers for update, route maps, filtering, triggered updates, interface-passive command, RIP authentication? | ||
| 1246 : | |||
| 1247 : | \item Add a loopback interface on the network with the same network as the Oslo network but a different subnet | ||
| 1248 : | Show the routing summary output from RIP and explain the result you get. What is happening? | ||
| 1249 : | |||
| 1250 : | \item Try to prevent the updating on an interface by using a {\tt passive-interface} command. | ||
| 1251 : | |||
| 1252 : | \end{enumerate} | ||
| 1253 : | |||
| 1254 : | |||
| 1255 : | \section{EIGRP - an improved RIP?} | ||
| 1256 : | |||
| 1257 : | You can use the text book {\em Cisco Cookbook}, chapter 7 to help you with this exercise. | ||
| 1258 : | |||
| 1259 : | \begin{enumerate} | ||
| 1260 : | |||
| 1261 : | \item Configure basic EIGRP on the network now and compare it with RIP | ||
| 1262 : | Can you use the same techniques as with RIP? What is the advantage of using EIGRP instead of RIP? | ||
| 1263 : | Which one would you recommend to your customer (explain your answer)? | ||
| 1264 : | |||
| 1265 : | \item Load balancing is the capability of a router to distribute traffic over all its network ports | ||
| 1266 : | that are the same distance from the destination address. Load balancing increases | ||
| 1267 : | the utilization of network segments. This means that it increases the network | ||
| 1268 : | capacity. There are two types of load balancing: {\em equal cost path} and {\em unequal | ||
| 1269 : | cost path}. | ||
| 1270 : | |||
| 1271 : | Do some reading so that you will understand how unequal cost path load | ||
| 1272 : | balancing works in the Enhanced Interior Gateway Routing Protocol (EIGRP). | ||
| 1273 : | Test out the flow of traffic on balanced routes, explaining what | ||
| 1274 : | tools you use to make measurements. | ||
| 1275 : | \end{enumerate} | ||
| 1276 : | |||
| 1277 : | \section{Routing loops} | ||
| 1278 : | |||
| 1279 : | Recall the problem of routing loops and counting to infinity. | ||
| 1280 : | Several methods and techniques exist for preventing these problems: | ||
| 1281 : | \begin{itemize} | ||
| 1282 : | \item Split horizon: never advertise a route out of the interface through which you learned it. | ||
| 1283 : | \item Poison reverse: once you learn of a route through an interface, advertise it as unreachable back through that same interface. | ||
| 1284 : | \end{itemize} | ||
| 1285 : | If you have time, learn about these methods and test them out. | ||
| 1286 : | |||
| 1287 : | |||
| 1288 : | \chapter{BGP Policies and Virtual Tunnels} | ||
| 1289 : | |||
| 1290 : | %%%%%%%%% | ||
| 1291 : | \begin{expt} | ||
| 1292 : | The purpose of this experiment is to become more familiar with the | ||
| 1293 : | BGP routing system and with concepts such as peering. | ||
| 1294 : | \begin{itemize} | ||
| 1295 : | \item {\bf Estimated time}: Three weeks | ||
| 1296 : | \item {\bf Preparation}: Read about BGP and Virtual Tunnels. | ||
| 1297 : | \item {\bf Equipment}: PCs routers and switches. | ||
| 1298 : | |||
| 1299 : | |||
| 1300 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1301 : | \end{itemize} | ||
| 1302 : | \end{expt} | ||
| 1303 : | |||
| 1304 : | |||
| 1305 : | |||
| 1306 : | In this experiment you must set up a network consisting of three | ||
| 1307 : | autonomous systems. The underlying routing can be configured by | ||
| 1308 : | any suitable method. | ||
| 1309 : | |||
| 1310 : | \section{Autonomous systems} | ||
| 1311 : | |||
| 1312 : | \begin{figure}[ht] | ||
| 1313 : | \psfig{file=bgp.eps,width=12cm} | ||
| 1314 : | \caption{A fragment of AS1 tunnels though AS2 in order to be contiguous with its larger parent network region.} | ||
| 1315 : | \end{figure} | ||
| 1316 : | |||
| 1317 : | Use 2 routers in AS2 and 1 router in all the other domain fragments | ||
| 1318 : | above. The two routers in AS2 should communicate with iBGP and there | ||
| 1319 : | should be eBGP communication between the ASs. | ||
| 1320 : | |||
| 1321 : | The question in this exercise is: what happens to the smaller fragment of | ||
| 1322 : | AS1 on the left hand side of the figure? Suppose that this is a branch office of | ||
| 1323 : | a larger company that is geographically separate from the | ||
| 1324 : | main centre. Formally, one would like the entire company to be | ||
| 1325 : | identified with AS1, but the BGP believes that the routing | ||
| 1326 : | domain is a convex region with a definite boundary. | ||
| 1327 : | |||
| 1328 : | The way one normally handles this is to create a point to point link that | ||
| 1329 : | makes the two sub-regions into a convex one. This can be done by one of two methods: | ||
| 1330 : | \begin{itemize} | ||
| 1331 : | \item A physical point-to-point connection from the sub-region to the main region. | ||
| 1332 : | \item A virtual ``tunnel'' from the sub-region to the main region. | ||
| 1333 : | \end{itemize} | ||
| 1334 : | Virtual tunnels are a part of the IPSec functionality, for instance. | ||
| 1335 : | |||
| 1336 : | Create a secure tunnel from the fragment of AS1 to the main region | ||
| 1337 : | and tie them together with the underlying routing protocol. | ||
| 1338 : | |||
| 1339 : | \section{Peering} | ||
| 1340 : | |||
| 1341 : | Add a direct connection between AS1 and AS3 and | ||
| 1342 : | create a peer group between AS1 and AS2 so that they share policy. | ||
| 1343 : | Describe the filtering policies that you implement. | ||
| 1344 : | |||
| 1345 : | |||
| 1346 : | \section{Configuration errors} | ||
| 1347 : | |||
| 1348 : | One of the problems with policy based management is that there is | ||
| 1349 : | no one policing the consistency of the rules at different parts of | ||
| 1350 : | the network. What happens if two ASs advertise the same routes as being | ||
| 1351 : | local to themselves? | ||
| 1352 : | |||
| 1353 : | Use the routers to create a "black hole" in which one of the ASs | ||
| 1354 : | advertises a network that it does not have. Show how this causes a | ||
| 1355 : | problem for the inter-AS routing. | ||
| 1356 : | |||
| 1357 : | \section{Equilibration} | ||
| 1358 : | |||
| 1359 : | Measure how long it takes for a consistent configuration to emerge in | ||
| 1360 : | the BGP network above when a change is made. | ||
| 1361 : | |||
| 1362 : | \chapter{Traffic Shaping and Quality of Service} | ||
| 1363 : | |||
| 1364 : | %%%%%%%%% | ||
| 1365 : | \begin{expt} | ||
| 1366 : | |||
| 1367 : | The purpose of this experiment is to perform a scientific study of | ||
| 1368 : | network performance under varying load. You will need to study methods | ||
| 1369 : | of measurement and inquiry and plan how to proceed. You must present your | ||
| 1370 : | report detailing the method, results and conclusions of your study. | ||
| 1371 : | \begin{itemize} | ||
| 1372 : | \item {\bf Estimated time}: Four to five weeks | ||
| 1373 : | \item {\bf Preparation}: Read about measurement and scientific method. Recall exercises on frame relay. Read about traffic shaping and Quality of Service. | ||
| 1374 : | \item {\bf Equipment}: PCs, routers and switches. | ||
| 1375 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1376 : | \end{itemize} | ||
| 1377 : | \end{expt} | ||
| 1378 : | |||
| 1379 : | \begin{figure}[ht] | ||
| 1380 : | \psfig{file=shaping.eps,width=11cm} | ||
| 1381 : | \end{figure} | ||
| 1382 : | |||
| 1383 : | You can use the course book {\em Cisco Cookbook}, chapter 10.1 and 10.4 etc. | ||
| 1384 : | to help you here. | ||
| 1385 : | |||
| 1386 : | \section{Scenario 1} | ||
| 1387 : | |||
| 1388 : | Imagine a small group of organizations that share a connection to the | ||
| 1389 : | Internet by a leased line. In this experiment you will measure the | ||
| 1390 : | performance (under varying loads) of a router with multiple hosts. Set up | ||
| 1391 : | a scenario for sharing the bandwidth of a trunk line that will be shared | ||
| 1392 : | equally between several end hosts. Various functionality exists in IOS: | ||
| 1393 : | |||
| 1394 : | |||
| 1395 : | \begin{itemize} | ||
| 1396 : | \item Bandwidth management through rate limiting - Allows you to control the maximum rate of traffic sent or received on an interface. | ||
| 1397 : | \item Traffic policing is often configured on interfaces at the edge of a network to limit traffic into or out of the network. | ||
| 1398 : | \item Traffic that falls within the rate parameters is sent, whereas traffic that exceeds the parameters is dropped, or sent with a different priority. | ||
| 1399 : | \item Packet marking through IP precedence, QoS group and so on. | ||
| 1400 : | \end{itemize} | ||
| 1401 : | |||
| 1402 : | The idea of this experiment is to pick a protocol with Quality of | ||
| 1403 : | Service (QoS)/traffic shaping support and compare this to a | ||
| 1404 : | competitively shared medium like Ethernet. Determine how these | ||
| 1405 : | different strategies compare in performance when traffic is low/high and when the | ||
| 1406 : | number of users sharing the link is low/high? | ||
| 1407 : | |||
| 1408 : | Referring to the figure above, you might choose to create 4 virtual | ||
| 1409 : | sub-interfaces on the left hand side, with four different virtual | ||
| 1410 : | circuits between end nodes and the right hand side. You would then compare | ||
| 1411 : | this to four Ethernet nodes connected directly by a hub or LAN switch on the | ||
| 1412 : | left. | ||
| 1413 : | |||
| 1414 : | When planning this experiment, think of the following points: | ||
| 1415 : | \begin{enumerate} | ||
| 1416 : | \item You should think about the problem above and interpret it in terms of the equipment | ||
| 1417 : | you have available. | ||
| 1418 : | \item What protocols and data rates will you use? (10MB Ethernet, 100MB Ethernet? 56kB Frame Relay?) | ||
| 1419 : | You will want to address questions like: | ||
| 1420 : | |||
| 1421 : | \begin{itemize} | ||
| 1422 : | \item How much of the prioritized bandwidth is idle under different loads? | ||
| 1423 : | \item At which points in the network will you monitor the flows of traffic? | ||
| 1424 : | \item What will you use to monitor the flows? (ttcpd? show interface etc.) | ||
| 1425 : | \item What will you use to generate the flows? (ttcpd, private program etc) | ||
| 1426 : | \end{itemize} | ||
| 1427 : | |||
| 1428 : | \item You are asked, below, to find the change in behaviour of the system | ||
| 1429 : | when you vary just one of many parameters that could be changed. | ||
| 1430 : | Explain how you will isolate these independent channels of cause-effect. | ||
| 1431 : | \end{enumerate} | ||
| 1432 : | |||
| 1433 : | You can not simulate the huge amounts of data that would be used in a | ||
| 1434 : | real organization, so you will have to scale your experiment down to | ||
| 1435 : | simulate a realistic case in the lab. Be sure to explain carefully how | ||
| 1436 : | you do this. | ||
| 1437 : | |||
| 1438 : | In order to compare the performance of different sharing policies, | ||
| 1439 : | you will have to do some thinking. We do not have an Ethernet and | ||
| 1440 : | a Frame Relay connection with the same channel capacity, so you will have | ||
| 1441 : | to measure the efficiencies and compare them by scaling or dividing by the | ||
| 1442 : | maximum for that medium. | ||
| 1443 : | |||
| 1444 : | \section{Measurements} | ||
| 1445 : | |||
| 1446 : | Once you have designed your experiment and the system is working: | ||
| 1447 : | |||
| 1448 : | \begin{enumerate} | ||
| 1449 : | \item Define a measure of performance for each protocol: how much of the | ||
| 1450 : | potential channel capacity is being used, e.g. | ||
| 1451 : | |||
| 1452 : | If the total channel capacity is $C$ and we split it into 3 shares, then it should be possible | ||
| 1453 : | to insert $C/3$ from each end host without problems. How much of this traffic actually arrives | ||
| 1454 : | however? What happens if you try to send more than $C/3$? | ||
| 1455 : | |||
| 1456 : | \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. | ||
| 1457 : | |||
| 1458 : | \item How does the performance of total transmission vary with the number of users? | ||
| 1459 : | \item How does the performance of each customer's transmission vary with the number of users, assuming an equal share to all? | ||
| 1460 : | \end{enumerate} | ||
| 1461 : | |||
| 1462 : | What data will you have to record to find answers to the questions above? | ||
| 1463 : | How many times must you repeat the experiments to obtain a sensible answer? | ||
| 1464 : | Use elementary statistics to show how reliable your estimates are. | ||
| 1465 : | |||
| 1466 : | |||
| 1467 : | \section{Scenario 2} | ||
| 1468 : | |||
| 1469 : | Frame-relay traffic shaping can also be applied to multi-service links. Find out, for instance, | ||
| 1470 : | how to do Voice over IP by connecting an analogue telephone to the FX ports (on those routers | ||
| 1471 : | that have them). | ||
| 1472 : | \begin{enumerate} | ||
| 1473 : | \item Start with configuring a frame-relay network with point to point sub-interfaces | ||
| 1474 : | |||
| 1475 : | \item After checking that the frame-relay is active use QoS to enable traffic shaping on the network | ||
| 1476 : | |||
| 1477 : | Here's a sample that show a traffic shaping configuration | ||
| 1478 : | |||
| 1479 : | \sex | ||
| 1480 : | policy-map mypolicy | ||
| 1481 : | class voice | ||
| 1482 : | priority 16 | ||
| 1483 : | class priority-data | ||
| 1484 : | bandwidth 16 | ||
| 1485 : | class other-data | ||
| 1486 : | priority 5 | ||
| 1487 : | |||
| 1488 : | !--- Create a policy-map and apply the bandwidth | ||
| 1489 : | !--- command to a class. | ||
| 1490 : | |||
| 1491 : | ! | ||
| 1492 : | int s0/1 | ||
| 1493 : | encapsulation frame-relay IETF | ||
| 1494 : | load-interval 30 | ||
| 1495 : | frame-relay traffic-shaping | ||
| 1496 : | |||
| 1497 : | !--- Enable Frame Relay TS. | ||
| 1498 : | |||
| 1499 : | ! | ||
| 1500 : | interface Serial0/0.1 point-to-point | ||
| 1501 : | frame-relay interface-dlci 160 | ||
| 1502 : | class frclass | ||
| 1503 : | |||
| 1504 : | !--- Apply the map-class to the Frame Relay PVC. | ||
| 1505 : | |||
| 1506 : | ! | ||
| 1507 : | map-class frame-relay frclass | ||
| 1508 : | service-policy output mypolicy | ||
| 1509 : | frame-relay cir 64000 | ||
| 1510 : | frame-relay bc 640 | ||
| 1511 : | |||
| 1512 : | !--- Apply the service-policy inside the map-class | ||
| 1513 : | |||
| 1514 : | \esex | ||
| 1515 : | |||
| 1516 : | \end{enumerate} | ||
| 1517 : | |||
| 1518 : | |||
| 1519 : | |||
| 1520 : | |||
| 1521 : | |||
| 1522 : | |||
| 1523 : | |||
| 1524 : | |||
| 1525 : | |||
| 1526 : | \chapter{Wireless Networking} | ||
| 1527 : | |||
| 1528 : | %%%%%%%%% | ||
| 1529 : | \begin{expt} | ||
| 1530 : | |||
| 1531 : | The purpose of this experiment is to perform a scientific study of | ||
| 1532 : | wireless network performance. | ||
| 1533 : | \begin{itemize} | ||
| 1534 : | \item {\bf Estimated time}: Two weeks | ||
| 1535 : | \item {\bf Preparation}: Read about wireless transmission and security. | ||
| 1536 : | \item {\bf Equipment}: PCs, routers and switches. Wireless sender. | ||
| 1537 : | |||
| 1538 : | |||
| 1539 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1540 : | \end{itemize} | ||
| 1541 : | \end{expt} | ||
| 1542 : | |||
| 1543 : | Imagine creating a wireless network for a small business or home. | ||
| 1544 : | Set up a wireless transmitted/receiver, connected to a LAN switch and | ||
| 1545 : | use a PC connected to the LAN to send and receive traffic to a mobile | ||
| 1546 : | laptop PC with a network card. | ||
| 1547 : | |||
| 1548 : | In this exercise you will be asked to test out the physical properties | ||
| 1549 : | of wireless communication. You will need to find a way to measure data | ||
| 1550 : | dates and signal strength and estimate the uncertainty in your measurements. | ||
| 1551 : | |||
| 1552 : | \begin{itemize} | ||
| 1553 : | \item Measure how far away from the source you can be. | ||
| 1554 : | \item What materials shield the signal from the sender? | ||
| 1555 : | \item Integrate the wireless network with the VLANs. | ||
| 1556 : | \end{itemize} | ||
| 1557 : | |||
| 1558 : | You can investigate anything that you like, but you should at least investigate the following | ||
| 1559 : | and collect data for analysis: | ||
| 1560 : | \begin{enumerate} | ||
| 1561 : | \item Test the wireless network by line of sight (with no walls etc in between). | ||
| 1562 : | \begin{enumerate} | ||
| 1563 : | \item Plot the signal strength $S$ against the inverse distance $1/d$ and its square $1/d^2$. | ||
| 1564 : | \item Plot the maximum data rate against the inverse distance $1/d$ and its square $1/d^2$. | ||
| 1565 : | \end{enumerate} | ||
| 1566 : | Comment on the graphs that you have obtained. | ||
| 1567 : | |||
| 1568 : | \item Test two or three substances (walls, metals, clothing etc) for their signal shielding properties. | ||
| 1569 : | Find a substance that will block transmission. Does it matter whether there are holes in the | ||
| 1570 : | material? What thickness of your chosen materials will stop the signal completely (so that it | ||
| 1571 : | is indistinguishable from noise)? | ||
| 1572 : | |||
| 1573 : | For example, try to get hold of some `chicken wire' or garden | ||
| 1574 : | fencing and see whether it shields the signal from the wireless transmitter. | ||
| 1575 : | \end{enumerate} | ||
| 1576 : | |||
| 1577 : | |||
| 1578 : | |||
| 1579 : | |||
| 1580 : | |||
| 1581 : | \chapter{VPN and IPSec} | ||
| 1582 : | |||
| 1583 : | %%%%%%%%% | ||
| 1584 : | \begin{expt} | ||
| 1585 : | |||
| 1586 : | The purpose of this experiment is to explore possibilities inherent in | ||
| 1587 : | IPSec and virtual tunnelling technologies. | ||
| 1588 : | \begin{itemize} | ||
| 1589 : | \item {\bf Estimated time}: Four weeks | ||
| 1590 : | \item {\bf Preparation}: Read about security. | ||
| 1591 : | \item {\bf Equipment}: PCs, routers with sufficient memory and CPU. | ||
| 1592 : | |||
| 1593 : | |||
| 1594 : | \item {\bf How to leave the lab after session}: No configurations must be stored. | ||
| 1595 : | \end{itemize} | ||
| 1596 : | \end{expt} | ||
| 1597 : | |||
| 1598 : | |||
| 1599 : | |||
| 1600 : | \begin{itemize} | ||
| 1601 : | |||
| 1602 : | \item Software encryption: | ||
| 1603 : | \begin{itemize} | ||
| 1604 : | \item Cisco IOS Release 12.1(3)XI or later. | ||
| 1605 : | \end{itemize} | ||
| 1606 : | \item Hardware encryption. | ||
| 1607 : | For the 3600 series routers, you will need | ||
| 1608 : | \begin{itemize} | ||
| 1609 : | \item Data encryption Advanced Integration Module (AIM) | ||
| 1610 : | \item Network Module (NM) provide hardware-based encryption. | ||
| 1611 : | \end{itemize} | ||
| 1612 : | 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. | ||
| 1613 : | \end{itemize} | ||
| 1614 : | |||
| 1615 : | IPSEC commands on a 3660 router: | ||
| 1616 : | \sex | ||
| 1617 : | crypto isakmp policy 10 | ||
| 1618 : | hash md5 | ||
| 1619 : | authentication pre-share | ||
| 1620 : | crypto isakmp key cisco123 address X.X.X.X | ||
| 1621 : | ! | ||
| 1622 : | crypto ipsec transform-set myset esp-des esp-md5-hmac | ||
| 1623 : | ! | ||
| 1624 : | crypto map mymap local-address FastEthernet0/0 | ||
| 1625 : | crypto map mymap 10 ipsec-isakmp | ||
| 1626 : | set peer X.X.X.X | ||
| 1627 : | set transform-set myset | ||
| 1628 : | match address 101 | ||
| 1629 : | ! | ||
| 1630 : | interface Tunnel0 | ||
| 1631 : | ip address X.X.X.X 255.X.X.X | ||
| 1632 : | no ip directed-broadcast | ||
| 1633 : | ipx network BB | ||
| 1634 : | tunnel source FastEthernet0/1 | ||
| 1635 : | tunnel destination X.X.X.X | ||
| 1636 : | crypto map mymap | ||
| 1637 : | \esex | ||
| 1638 : | |||
| 1639 : | |||
| 1640 : | |||
| 1641 : | \chapter{Virtual machines and large installation configuration} | ||
| 1642 : | |||
| 1643 : | \begin{expt} | ||
| 1644 : | |||
| 1645 : | The purpose of this experiment is to investigate the problem of managing | ||
| 1646 : | a large number of computers that are networked together. Since we do not | ||
| 1647 : | have a large number of computers, you will simulate them using virtual machines. | ||
| 1648 : | |||
| 1649 : | \begin{itemize} | ||
| 1650 : | \item {\bf Estimated time}: Three weeks | ||
| 1651 : | \item {\bf Preparation}: Read about User-Mode Linux and test it out. Read about getting started with cfengine. | ||
| 1652 : | \item {\bf Equipment}: hosts netlab1-netlab4. | ||
| 1653 : | |||
| 1654 : | |||
| 1655 : | \item {\bf How to leave the lab after session}: simulations can run if there are sufficient | ||
| 1656 : | resources. | ||
| 1657 : | \end{itemize} | ||
| 1658 : | \end{expt} | ||
| 1659 : | |||
| 1660 : | \section{Virtual networks} | ||
| 1661 : | |||
| 1662 : | You should spend a week learning how to configure User Mode Linux and designing a network | ||
| 1663 : | structure, with two subnets. | ||
| 1664 : | |||
| 1665 : | \section{Managing the network} | ||
| 1666 : | |||
| 1667 : | Once you are familiar with how to create a virtual network simulation: | ||
| 1668 : | \begin{enumerate} | ||
| 1669 : | \item Using User-Mode Linux, design and set up a network consisting of two different subnets | ||
| 1670 : | and about fifty machines. Give your subnets different subnet masks. | ||
| 1671 : | |||
| 1672 : | \item Set up E-mail services, several web servers and use cfengine to manage the hosts. | ||
| 1673 : | |||
| 1674 : | \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 | ||
| 1675 : | web downloads. | ||
| 1676 : | |||
| 1677 : | \item You should set up cfengine to report to you as system administrator by E-mail. | ||
| 1678 : | Investigate how well the cfengine management scales with numbers of machines, especially | ||
| 1679 : | when files are being distributed from a central origin. | ||
| 1680 : | |||
| 1681 : | \item Can you make your network run on IPv6? | ||
| 1682 : | \end{enumerate} | ||
| 1683 : | |||
| 1684 : | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| 1685 : | |||
| 1686 : | \chapter{High availability web services} | ||
| 1687 : | |||
| 1688 : | |||
| 1689 : | |||
| 1690 : | \begin{expt} | ||
| 1691 : | |||
| 1692 : | The purpose of this experiment is to investigate strategies for redundant, high-volume | ||
| 1693 : | network services. | ||
| 1694 : | |||
| 1695 : | \begin{itemize} | ||
| 1696 : | \item {\bf Estimated time}: Three weeks | ||
| 1697 : | \item {\bf Preparation}: Read about User-Mode Linux and test it out. Read about getting started with cfengine. | ||
| 1698 : | \item {\bf Equipment}: hosts netlab1-netlab4. | ||
| 1699 : | |||
| 1700 : | |||
| 1701 : | \item {\bf How to leave the lab after session}: simulations can run if there are sufficient | ||
| 1702 : | resources. | ||
| 1703 : | \end{itemize} | ||
| 1704 : | \end{expt} | ||
| 1705 : | |||
| 1706 : | \begin{enumerate} | ||
| 1707 : | \item Set up a GNU/Linux Apache web server on a relatively old (slow) PC and test its ability | ||
| 1708 : | to serve files. | ||
| 1709 : | |||
| 1710 : | \item Investigate how the performance of the server varies with the number of pre-forked | ||
| 1711 : | processes and the configuration parameter that governs the maximum number of servers. | ||
| 1712 : | Measure the latency (average time to wait) and the average data rate, using tools of your own choice. | ||
| 1713 : | |||
| 1714 : | \item Create a load balancer that allows you to connect two PCs in parallel. How does the performance | ||
| 1715 : | f this parallel configuration compare to the performance of a single machine as the same parameters | ||
| 1716 : | are varied as above. | ||
| 1717 : | |||
| 1718 : | \item Install a Microsoft Windows 2000 Internet Information Server (IIS) and compare its | ||
| 1719 : | performance with a single Apache server on Linux, on the same hardware. Compare the performance | ||
| 1720 : | of the servers, the latency and the scalability of these two solutions. Can you say whether one or the | ||
| 1721 : | other is ``better''? | ||
| 1722 : | |||
| 1723 : | \item Suggest a design for a high volume server. | ||
| 1724 : | \end{enumerate} | ||
| 1725 : | |||
| 1726 : | |||
| 1727 : | |||
| 1728 : | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| 1729 : | |||
| 1730 : | \chapter{Disk performance} | ||
| 1731 : | |||
| 1732 : | |||
| 1733 : | \begin{expt} | ||
| 1734 : | |||
| 1735 : | The purpose of this experiment is to investigate the performance of ATA (IDE) and | ||
| 1736 : | SCSI disks under different loads. You should design an experiment to stress test these | ||
| 1737 : | technologies under single and multi-user access. | ||
| 1738 : | |||
| 1739 : | \begin{itemize} | ||
| 1740 : | \item {\bf Estimated time}: Two to three weeks | ||
| 1741 : | \item {\bf Preparation}: Read about ATA (IDE) and SCSI disks, their strengths and weaknesses. | ||
| 1742 : | \item {\bf Equipment}: Anything you can get your hands on! | ||
| 1743 : | |||
| 1744 : | \item {\bf How to leave the lab after session}: Equipment should be tidied but may be labelled | ||
| 1745 : | or reserved for the group. | ||
| 1746 : | \end{itemize} | ||
| 1747 : | \end{expt} | ||
| 1748 : | |||
| 1749 : | Design your own experiment to measure the performance of a disk. | ||
| 1750 : | \begin{itemize} | ||
| 1751 : | \item Consider what it is that you will measure. | ||
| 1752 : | \item What tools will you use? | ||
| 1753 : | \item What hypotheses will you form and test? | ||
| 1754 : | \item How will you organize and analyze your data? | ||
| 1755 : | \item How will you arrange to test the disks to their limits? | ||
| 1756 : | \item How does performance change as load increases? Using current prices, work out the | ||
| 1757 : | performance of each disk per price/MB. | ||
| 1758 : | |||
| 1759 : | \item Using any tools that you can find, format a new disk (filesystem) and write some | ||
| 1760 : | recognizable data to it. Then delete all of the files. Using tools of your choice, | ||
| 1761 : | see how much of the data you are able to recover from the disk. | ||
| 1762 : | \end{itemize} | ||
| 1763 : | |||
| 1764 : | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| 1765 : | |||
| 1766 : | \chapter{SNMP} | ||
| 1767 : | |||
| 1768 : | The Simple Network Management Protocol is an important technology for network | ||
| 1769 : | devices. This experiment asks you to learn about its use. | ||
| 1770 : | \begin{expt} | ||
| 1771 : | |||
| 1772 : | The purpose of this experiment is to investigate investigate some of the characteristics | ||
| 1773 : | of the Simple Network Management Protocol. | ||
| 1774 : | |||
| 1775 : | \begin{itemize} | ||
| 1776 : | \item {\bf Estimated time}: One to two weeks | ||
| 1777 : | \item {\bf Preparation}: Read about SNMP and monitoring on the web. | ||
| 1778 : | \item {\bf Equipment}: Any. | ||
| 1779 : | |||
| 1780 : | |||
| 1781 : | \item {\bf How to leave the lab after session}: software etc. must be removed once | ||
| 1782 : | the experiment is over. | ||
| 1783 : | |||
| 1784 : | \end{itemize} | ||
| 1785 : | \end{expt} | ||
| 1786 : | |||
| 1787 : | When using the SNMP tools below, use a program like {\tt tcpdump} to show the | ||
| 1788 : | traffic that passes between your console and the devices. In your final report, | ||
| 1789 : | you should comment on the overhead incurred by SNMP. | ||
| 1790 : | |||
| 1791 : | \begin{enumerate} | ||
| 1792 : | \item Find out whether you need to enable SNMP services on routers and switches. | ||
| 1793 : | \item Write a PHP or Perl script that queries SNMP data from a printer. | ||
| 1794 : | \item Locate, download and compile the {\tt scli} tool. | ||
| 1795 : | \item Locate MRTG noting that this might be already installed on the machine | ||
| 1796 : | you are using. Install it and get it running. Show how it generates plots of traffic activity. | ||
| 1797 : | \item Investigate using the {\tt scli} tool to configure routers and switches. | ||
| 1798 : | \end{enumerate} | ||
| 1799 : | |||
| 1800 : | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| 1801 : | |||
| 1802 : | \chapter{Pick'n'mix (max 4 toppings)} | ||
| 1803 : | |||
| 1804 : | |||
| 1805 : | \begin{expt} | ||
| 1806 : | |||
| 1807 : | The purpose of this experiment is to investigate your own projects. | ||
| 1808 : | |||
| 1809 : | \begin{itemize} | ||
| 1810 : | \item {\bf Estimated time}: Three-five weeks | ||
| 1811 : | \item {\bf Preparation}: Plan out your proposal and submit it in writing to the course instructors. | ||
| 1812 : | \item {\bf Equipment}: | ||
| 1813 : | |||
| 1814 : | |||
| 1815 : | \item {\bf How to leave the lab after session}: simulations can run if there are sufficient | ||
| 1816 : | resources. | ||
| 1817 : | \end{itemize} | ||
| 1818 : | \end{expt} | ||
| 1819 : | |||
| 1820 : | You are free to suggest your own experiments for the laboratory. | ||
| 1821 : | You will gain course credit as long as the course instructors have approved | ||
| 1822 : | the plan. An experiment should start by asking a question and should contain | ||
| 1823 : | a degree of analysis. | ||
| 1824 : | \begin{itemize} | ||
| 1825 : | \item What is your hypothesis? | ||
| 1826 : | \item How will you test it critically? (You should not set out to prove a hypothesis, bust rather to disprove it!) | ||
| 1827 : | \end{itemize} | ||
| 1828 : | Suggested topics: | ||
| 1829 : | \begin{itemize} | ||
| 1830 : | \item Novell/Windows integration. | ||
| 1831 : | \item Cfengine on windows. | ||
| 1832 : | \item Compare OSPF routing with IS-IS routing. | ||
| 1833 : | \item Dialup services. | ||
| 1834 : | \item Compare difference operating systems. | ||
| 1835 : | \item IP Telephony. | ||
| 1836 : | \end{itemize} | ||
| 1837 : | |||
| 1838 : | \bibliography{LISAbib} | ||
| 1839 : | |||
| 1840 : | \end{document} |
| Administrator | ViewVC Help |
| Powered by ViewVC 1.0.3 |