82 | | <h3><u> Step 3: View Results: </u></h3> |
83 | | For this example experiment we used the install script facility to automatically install the necessary software and kick-off the experiment. In this very simple setup, we have installed and launched a |
84 | | <a href="[http://en.wikipedia.org/wiki/Web_server" target="_blank"> web server </a> as well as an <a href="http://en.wikipedia.org/wiki/Iperf" target="_blank"> iperf server</a>, on the server host. On the client, we have started some processes to test both of these services. To view the results of this experiment: |
85 | | <table border="0"> |
86 | | <tr> |
87 | | <td > |
88 | | <ol type="a"> |
89 | | <li> After the background of your slice turns green, press the (i) button that is on the server node icon.</li> |
90 | | <li> In the information tab that came up, press the <b>Visit</b> button. A new tab should come up that looks like the picture on the side. </li> |
91 | | <li> Click the <b>Web Server Statistics</b> link to look at statistics. Refresh the page a couple of times to see how the statistics change as the client requests documents.</li> |
92 | | <li> Click the <b>Logs from the iperf Server</b> link to see the statistics from the iperf transfers.</li> |
93 | | </ol> |
94 | | </td> |
95 | | |
96 | | </tr> |
97 | | </table> |
98 | | <h3><u> Optional Step 4: Manually generate traffic: </u></h3> |
99 | | While conducting experiments in GENI, you will often want to run commands directly on the nodes. In this optional step, you will log in to a node and issue commands directly to it. |
100 | | <ol type="a"> |
101 | | <li> Follow <a href="http://groups.geni.net/geni/wiki/HowTo/LoginToNodes" target="_blank"> these instructions</a> and log in to the client node </li> |
102 | | <li> When you have successfully logged in, run this command:<br> |
103 | | <code> |
104 | | iperf -c server -P 2 |
105 | | </code> <br> |
106 | | This task shouldn't take more than 30 seconds. Change the number after the ` -P ` argument and watch how the performance is affected while you change the number of parallel TCP connections. |
107 | | </li> |
108 | | <li> Scroll all the way down the server iperf log, and look at the logs for your transfers </li> |
109 | | </ol> |
110 | | |
| 82 | The goal of this exercise is to setup the routing as indicated in Figure 1; i.e. packets from A send to IP address 192.168.2.12 on node C should be routed via node B. The default behavior between your nodes is different. |
| 83 | === Question 2 === |
| 84 | ''Verify the default routing behavior using the [http://en.wikipedia.org/wiki/Traceroute traceroute] linux command.'' |
| 85 | |
| 86 | ''Hand in'': Screenshots with the output of the traceroutes commands. |
| 87 | |
| 88 | === Question 3 === |
| 89 | ''Use the linux [http://www.hscripts.com/tutorials/linux-commands/route.html route command] to create static routes that match the routing behavior of the diagram.'' |
| 90 | |
| 91 | ''Hand in:''The routing commands your ran. The final route configuration. |
| 92 | |
| 93 | === Question 4 === |
| 94 | ''Verify that you have created the intended routing behavior using traceroute.'' |
| 95 | |
| 96 | ''Hand in:'' Screenshots from node A that shows traceroutes for both IP addresses of node C. |
| 97 | [[BR]][[BR]] |
| 98 | |
| 99 | <h3><u> 3. Setup the routing </u></h3> |
| 100 | The goal of this exercise is to setup the routing as indicated in Figure 1; i.e. packets from A send to IP address 192.168.2.12 on node C should be routed via node B. In order to create this routing behavior you will need to modify the routing tables in your nodes using the linux <a href ="http://www.hscripts.com/tutorials/linux-commands/route.html> route command </a> |
| 101 | |
156 | | The goal of this exercise is to setup the routing as indicated in Figure 1; i.e. packets from A send to IP address 192.168.2.12 on node C should be routed via node B. The default behavior between your nodes is different. |
157 | | === Question 2 === |
158 | | ''Verify the default routing behavior using the [http://en.wikipedia.org/wiki/Traceroute traceroute] linux command.'' |
159 | | |
160 | | ''Hand in'': Screenshots with the output of the traceroutes commands. |
161 | | |
162 | | === Question 3 === |
163 | | ''Use the linux [http://www.hscripts.com/tutorials/linux-commands/route.html route command] to create static routes that match the routing behavior of the diagram.'' |
164 | | |
165 | | ''Hand in:''The routing commands your ran. The final route configuration. |
166 | | |
167 | | === Question 4 === |
168 | | ''Verify that you have created the intended routing behavior using traceroute.'' |
169 | | |
170 | | ''Hand in:'' Screenshots from node A that shows traceroutes for both IP addresses of node C. |
171 | | [[BR]][[BR]] |