CS 410/595 IP Routing (and Network Management) Jim Binkley Winter 2010 Course Title: IP Routing and Network Management Syllabus -------- Class time: T/Th, 4:40-6:30 Classroom: PSU Distance Learning Center Urban Building 303 classroom. Class is recorded. Office hours: Th 2:00-4:00 or before/after class or by appointment OR send email to make an appointment OR just ask questions. Office hours will be held in the netlab, FAB 86-04 PSU Office: FAB 120-14 Email: jrb@cs.pdx.edu Class Page: http://www.cs.pdx.edu/~jrb/route.html Mailing list: Join as soon as possible (this list address is now correct) on the web at: https://mailhost.cecs.pdx.edu/mailman/listinfo/cs595 Note: Tue Dec 29 09:45:01 PST 2009, was initialized. If you put yourself in before then, please do it again. mailman list - use the web to add yourself netlab: fab86-04 (lower basement, near CS tutors) card key access Text: Routing in the Internet. Christian Huitema. Prentice Hall. 1999. ISBN: 0-13-022647-5 2nd edition. Text: SNMP, SNMPv3, and RMON 1 and 2: Practical Network Management, Third Edition. William Stallings, Addison Wesley. 1998. ISBN 0-201-48534-6 Students must have PSU ID cards and be able to easily go to the network lab which is currently in the FAB basement area (the secret location will be revealed in class, well ok, it's FAB 86-04). Home page: Note that various class-related documents will be available from the class home page. Students should make themselves familiar with it. Students should also join the class mailing list. Please feel free to participate in class-related discussion on that mailing list. Prerequisites ------------- Students must... In general, this class assumes that a student has networking background equivalent to what is taught in the TCP/IP CS 594 course or any graduate "intro to networking/communications" course. However that said, CS 594 is not a strict requirement. We will have a review the 1st week and it is hoped that any student can catch up. Also it should be pointed out that the lab assignments should make this class fun. Students should understand how an IP "best effort" datagram network works, be familiar with TCP and UDP as transports, and understand the mechanics of at least one link-layer network; e.g., Ethernet. Programming will not be required. However there will be at least 4 graded lab assignments done in teams. An optional network management assignment may be done as well. Goals ----- We have two goals in this class. One is to study Layer 3 routing as used in the IETF TCP/IP suite of protocols. The other is to study network management, in particular Ethernet switches and the SNMP protocol and related tools. We will study routing theory and routing protocols as used in the Internet including interior routing protocols like RIPv2, OSPF, and exterior routing protocols like BGP. In addition, as time permits, we will take a look at multicast routing, and crazy ideas like Mobile-IP. In the second half of the course, we will first look at network design in terms of modern Ethernet-based switches, and related protocols including CDP, STP, and VLANS. We will then look at SNMP v1, v1 MIBS, RMON v1/v2, and related monitoring tools. We will also take a quick look at SNMP v2, and SNMPv3. As we go along we will explore various useful network management tools like MRTG-based systems (cricket/cacti and the like), as well as sniffers, and other tools. The class has a hand-ons portion. It is expected that students will be able to physically come to PSU and work in the netlab. There will be four assignments for teams of 2-3 students apiece. If a student for some reason, cannot work in the netlab (fully employed at an outside job, and can't make it into PSU), that student may negotiate a term-paper to be done on a suitable network management project, or routing research area. Students should expect to take 1 or more training classes on friday mornings or as arranged with the instructor. Class Design ------------ There will be six grading events for students including: 1&2. a midterm and final. 3. 4 team assignments due at two week intervals (in general). The netlab team projects may be replaced with a term paper, but only for a student who cannot make it to PSU to do the labs. Students will also be graded on classroom participation including attendance. The labs are not hard and should be fun. Any student who wants to "improve" their test scores can do an additional lab on network management -- talk to the instructor. Rough Calendar (may slip as needed) ----------------------------------- dates of interest: classes start week of Jan 4, tuesday is Jan 5 for 1st class finals week: march 15-20. 2010 January February March S M Tu W Th F S S M Tu W Th F S S M Tu W Th F S 1 2 1 2 3 4 5 6 1 2 3 4 5 6 3 4 5 6 7 8 9 7 8 9 10 11 12 13 7 8 9 10 11 12 13 10 11 12 13 14 15 16 14 15 16 17 18 19 20 14 15 16 17 18 19 20 17 18 19 20 21 22 23 21 22 23 24 25 26 27 21 22 23 24 25 26 27 24 25 26 27 28 29 30 28 28 29 30 31 31 When What Assignments ---- ---- ----------- by week (note: class ON tu/th, but week given by monday) Jan 4 syllabus, ip review, lab1 out on thursday special lab session hopefully on friday Jan 11 routing theory overview intro to cisco routers (handouts) Jan 18 RIPv1, v2, Jan 25 OSPF lab 1 due Jan 30 lab 2 out checkpoint#1 due on Jan 30 Feb 1 BGP/CIDR (policy routing if possible) Feb 9/11 Mobile-IP on tuesday lab 2 in, lab 3 out Feb 11 midterm checkpoint #2 for term paper Feb 15 network design/switching SNMP intro, v1 etc. Feb 22 lab 3 in, lab 4 out Mar 3 RMON/tools/flows tools may include ourmon, nedi, nagios, cricket, etc. Mar 8 SNMPv2/v3 student team critiques due Mar 16 final - Tuesday 17:30-19:20 lab 4 in by final term papers in by final Following only applies to term-papers: checkpoint #1: students who are doing term papers must have negotiated a topic with the instructor by this date. checkpoint #2: students turn in via EMAIL a 1-2 page description of term paper (or project if approved by instructor), which includes abstract, outline, and bibliography. instructor must approve and will criticize and return the outline. Note: you may turn this in before this deadline. (It could happen ...). checkpoint #3: student turns in printed term paper. No email submissions please. Term Paper ---------- This is only for students doing term papers. About the time of the midterm, each student will turn in a 1-2 abstract of a term paper to be turned in at the close of the quarter. The abstract must be approved by the instructor before the term paper is written. It should contain a short overview (abstract) of the topic, a proposed outline (in detail), and a bibliography. It is not expected that students will do original research, but it is expected that they will analyze a given routing-oriented subarea and produce a written analysis of that area. A student might choose to do a area overview; e.g., students could analyze a broader area like mobile ad hoc routing or BGP in depth, or mobile multicast routing, and compare and contrast various routing protocols. It is required that the topic here be *different* from the lecture topic. A list of possible topic areas will be provided by the instructor, but if a student has an appropriate idea of her/his own, you may be given permission to pursue that area. Students may not team up on this project without special consent from the instructor. Note there is no reason more than one student cannot work on the same area here. Assignments: We will do four lab assignments (if time permits) and in addition a student or small team may do a network monitoring assignment. In order to participate in the lab students have to get card key access, and must have a valid student ID. Students will be "invited" to attend 1-2 introductory lab sessions run by the instructor, probably on a friday or monday early in the quarter. Missing these is not a good idea. The lab assignments for the most part are aimed at exploration of various routing protocols including static routing, RIP, OSPF, and BGP. One assignment will be devoted to working with switches and SNMP. An advanced assignment will be offered for extra credit. Students will be expected to work in teams of a few students and to use the class mailing list to coordinate lab access. Each assignment will be turned in on paper and emailed to the instructor. PDF, postscript, or ASCII may be used. Note: assignments will be graded with two criteria in mind: 1. were the questions answered satisfactorily (of course)? 2. how well was the answer presented in terms of clarity? Presentation is important. Each team member will be expected to send email during the final week of class to the instructor outlining what they did during the labs, and what others in their teams did in terms of work. Grading ------- Midterm: 100 points Lecture: 100 points Term Paper/Labs: 100 points (each lab is worth 25 points) Class participation 50 points and homework if any ---- Total: 350 points Your final grade for the course is determined by determining the percentage of the points you earn with respect to the total possible. Each letter grade occupies roughly a 10 point spread (A: 90%-100%, B: 80%-90%etc). Minus and plus grades will be awarded too; e.g., A- will be 90-92. B+ will be 88-89.