CS 595 IP Routing and Network Management (3 credits) Jim Binkley Winter 2003 Course Title: Routing and Network Management Syllabus -------- Class time: T/Th, 4:00-5:50 Classroom: OCATE, see sign outside OCATE door at Capital Center for the individual class room Office hours: W, 9:00-11:00 or before/after class or by appointment OR send email to make an appointment OR just ask questions. I will attempt to get to OCATE early for questions. PSU Office: FAB 120-14 Phone: please use email until "convergence" :-> Email: jrb@cs.pdx.edu Class Page: http://www.cs.pdx.edu/~jrb/route.html Mailing list: Send message: routing@cs.pdx.edu Join: To: majordomo@cs.pdx.edu ----- subscribe routing 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 optional lab text: Advanced IP Routing in Cisco Networks Terry Slattery, and Bill Burton, McGraw Hill, 2000, ISBN 0-07-212591-8. 2nd edition, Students are limited to a maximum of 24 due to lab exercises in the PSU netlab. Students must have PSU ID cards and be able to easily go to the network lab which is currently in the FAB 100 suite area (off of the UNIX lab, the netlab is 135-02). Excerpts from: Internet RFCs and research papers available on the Internet. You should know how to get them (e.g., anonymous ftp to ftp.isi.edu; cd in-notes for RFCS, cd internet-drafts for drafts). 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 574 course or any graduate "intro to networking/communications" course. For example, 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. This is not an introduction to networking class. Programming will not be required. However there will be at least 4 graded lab assignments. 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, we will take a look at multicast routing, 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, as well as sniffers, and other tools. The class has a hand-ons portion. Even though the lecture is at OCATE 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 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 make several training classes on friday mornings. 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. Students will also be graded on classroom participation including attendance. Calendar (may slip as needed) ----------------------------- dates of interest: classes start week of Jan 5, tuesday is Jan 6 last week to change grading option: 1st week of Feb. final week: march 15-20 When What Assignments ---- ---- ----------- by week (class tu/th) Jan 6/8 syllabus, ip review, routing theory lab1 out friday 9 am session Jan 13/15 multicast routing intro to cisco routers (handouts) Jan 20/22 RIPv1, v2, Jan 27/29 OSPF lab 1 due on 27 lab 2 out on 27 checkpoint#1 due on Jan 29 Feb 3/5 BGP/CIDR (policy routing if possible) Feb 10 Mobile-IP lab 2 in, lab 3 out Feb 12 midterm checkpoint#2 Feb 17/19 network design/switching Feb 24/26 SNMPv1/mibs, etc. lab 3 in, lab 4 out on 24 Mar 2/4 RMON/tools/slippage Mar 9/11 SNMPv2/v3 student team critiques due Mar 11 term paper due (#3) (if not doing labs) lab 4 in on 11 Mar 16 final at OCATE 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 ...). If an abstract is late, one letter grade (-11%) will be removed from the term paper. 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 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. However one student CANNOT present the very same area in the talk and the term paper. Class participation: students are expected to attend class especially during the student lecture part of the course. Students are also expected to make some effort to follow the material in the class and ask questions. Students in lab teams are also expected to do some of the work in their lab teams. Each team member will be expected to send email during the final week of class to the instructor outling 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 ---- Total: 350 points Each assignment and test will weigh the same. 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.