21 | | == 5b. Send IP traffic == |
22 | | The first simple experiment that we will run is to verify the IP connectivity |
23 | | between our hosts. |
24 | | i. Check the interfaces of your nodes. In the terminal type: |
25 | | {{{ |
26 | | /sbin/ifconfig |
27 | | }}} |
28 | | You should see at least two interfaces: |
29 | | * The '''control interface'''. This is the interface from where you access |
30 | | the node, e.g. ssh into your host. The control interface is mainly used for |
31 | | control traffic, i.e. traffic for controlling the node and the experiment. |
32 | | The control interface usually has a publicly routable IP. |
33 | | * The '''data interface'''. This is the interface that is used for sending |
34 | | experimental traffic. This is the interface that connects to the other hosts |
35 | | of your experiment through GENI. The links between these interfaces are the |
36 | | ones that allow you to run non-IP experiments. |
37 | | i. Note the name and the MAC address of the control and of the data interface for each node. The data interface is the one that has an IP that starts with 10. |
| 21 | == Ping between your hosts == |
| 22 | The first simple experiment that we will run is to verify the IP connectivity between our hosts. |
| 23 | |
60 | | == 5c. Send non-IP traffic == |
61 | | GENI provides the capability of running non-IP experiments, since you can |
62 | | connect your hosts at Layer 2. For the purpose of this tutorial we have |
63 | | installed in all the hosts a very simple Layer 2 ping program that sends packets |
64 | | using a custom ethernet type. |
65 | | i. Disable the IP in your nodes. First of all we are going to completely |
66 | | disable IP on our nodes. In each of the terminals type: |
67 | | {{{ |
68 | | sudo /sbin/ifconfig <data i/f name> 0.0.0.0 |
69 | | }}} |
70 | | '''Note''': Be extra careful to bring down the IP on the data interface, |
71 | | bringing down the IP on the control interface means that you will lose |
72 | | connectivity to your host. |
73 | | ii. Try again to ping from the client to the server. In the xterm of the |
74 | | client type: |
75 | | {{{ |
76 | | ping server -c 5 |
77 | | }}} |
78 | | This time the ping should timeout. |
79 | | iii. Start the Layer 2 ping server: In the server xterm, type: |
80 | | {{{ |
81 | | sudo /usr/local/bin/pingPlusListener 12345 |
82 | | }}} |
83 | | iii. From the client try to ping the server at layer 2. You will need the mac |
84 | | address of the data interface of the server and the name of the data interface |
85 | | of the client. In the xterm of the client, type: |
86 | | {{{ |
87 | | sudo /usr/local/bin/pingPlus <server data mac addr> <client data i/f name> 12345 |
88 | | }}} |
| 46 | == View results == |
| 47 | 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 [http://en.wikipedia.org/wiki/Web_server web server] as well as an [http://en.wikipedia.org/wiki/Iperf iperf server], on the server host. On the client, we have started some processes to test both of these |
| 48 | services. To view the results of this experiment: |
| 49 | |
| 50 | {{{ |
| 51 | #!html |
| 52 | <table border="0"> |
| 53 | |
| 54 | <tr> |
| 55 | <td> <center> |
| 56 | <img border="0" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Graphics/hellogeni-websrv.png?format=raw" alt="Hello GENI index" height="90" title="Hello GENI Web server" /> |
| 57 | </center></td> |
| 58 | <td colspan="2" valign="top"> |
| 59 | <ol start="2"> |
| 60 | <li> <b>Start a web browser</b> and in the location bar type: <code> http://<server_hostname> </code>. </li> |
| 61 | <li> When the page loads, click the <b>webserver statistics</b> link to look at statistics. Refresh the page a couple of times to see how <br>the statistics change as the client requests documents.</li> |
| 62 | <li> Click the <b>iperf logs</b> link to see the statistics from the iperf transfers.</li> |
| 63 | </ol> |
| 64 | </td> |
| 65 | </tr> |