• Document: Lab Exercise 3 (part A) Introduction to Mininet Objectives: Learn the basic commands in Mininet Learn how to create basic network topologies in Mininet Learn Mininet API Marks: This exerci...
  • Size: 450.33 KB
  • Uploaded: 2021-07-22 17:35:54
  • Status: Successfully converted


Some snippets from your converted document:

Lab Exercise 3 (part A) Introduction to Mininet Objectives: • Learn the basic commands in Mininet • Learn how to create basic network topologies in Mininet • Learn Mininet API Marks: This exercise forms the first part of lab exercise 3. The second part (part B) will be part of next week’s lab. Both parts together will comprise 15 marks. Only selected exercises will be marked. However, students must submit answers for all exercises. Deadline: Before your scheduled lab next week. So you get one week to work on this lab. For example, if you go to the Monday 12 noon lab, then your submission is due before 12 noon on the following Monday. You can submit as many times as you wish before the deadline. A later submission will override the earlier submission, so make sure you submit the correct file. Do not leave until the last moment to submit, as there may be technical or communications error and you will not have time to rectify it. Late Penalty: Late penalty will be applied as follows: • 1 day after deadline: 20% reduction • 2 days after deadline: 40% reduction • 3 days after deadline: 60% reduction • 4 or more days late: NOT accepted Note that the above penalty is applied to your final mark. For example, if you submit your lab work 2 days late and your score on the lab is 8, then your final mark will be 8-3.2 (40% penalty) = 4.8. Submission Instructions: Submit a PDF document lab3a.pdf with answers to all questions for all exercises. Include all supporting documents such as topology files for Questions 5 and 6(*.py). Create a tar archive of all files called lab3a.tar. Submit the archive using give. Click on the submission link at the top of the page. Max file size for submission is 3MB. Original Work Only: You are strongly encouraged to discuss the questions with other students in your lab. However, each student must submit his or her own work. You may refer to the reference material and also conduct your own research to answer the questions. 1 Notation: In the examples below, we have used the $ sign to represent Linux commands that should be typed at the shell prompt, mininet> to show Mininet commands that should be typed at Mininet’s CLI (command line interface), and # to show Linux commands that are typed at a root shell prompt. In each case, you should only type the name of the command and then press return. The actual prompt may look very different on your computer (e.g. it may contain the computer's hostname, or your username, or the current directory name). The commands that you are supposed to type are in this bold font. Part 1: Basic Commands in Mininet In the first step, we start a simple network topology by running the following command: $ sudo mn The above command creates the default topology in Mininet (known as the minimal topology), which includes one OpenFlow1 kernel switch connected to two hosts, plus the OpenFlow reference. This topology could also be mentioned on the command line using option --topo=minimal with the mn command. Once you run the above command, all four entities (two hosts, one switch, and one controller) are running in the VM and the Mininet CLI comes up. You can run the help command to see the list of commands in the CLI. In the rest of this section, you will practice the basic commands in Mininet. Display nodes: mininet> nodes For more detailed information about the nodes in the network, use dump. Display topology: mininet> net Simple commands within a node: If the first string typed into the Mininet CLI is a host, switch or controller name, the corresponding command is executed on that node. For example, run the following command on host h1 to show its network interfaces. mininet> h1 ifconfig -a 1 OpenFlow is communication protocol between switches and controllers. We do not need to know the details of the OpenFlow protocol in this course. 2 In the above command, you can replace h1 with s1 to see the details of the switch’s interfaces. Also, for a list of processes in a host you can run h1 ps –a. Note that a switch is a layer 2 packet switch

Recently converted files (publicly available):