| | 21 | |
| | 22 | Now that you have reserved your resources, you are ready to run your first GENI experiment. For the purpose of this tutorial we are going to do a simple layer 2 experiment. |
| | 23 | |
| | 24 | === 9. Login to nodes === |
| | 25 | {{{ |
| | 26 | #!html |
| | 27 | <table border="0"> |
| | 28 | <tr> |
| | 29 | |
| | 30 | <td > |
| | 31 | <ol> |
| | 32 | <li>Open a new terminal window. Type the login command for <i>Utah InstaGENI</i> into that terminal window. You have now logged into your VM.</li> |
| | 33 | <li><FONT COLOR="black">Repeat the previous step for <i>GPO InstaGENI</i> in a second terminal window.</font></li> |
| | 34 | |
| | 35 | |
| | 36 | <table id="Table_03" border="0" cellpadding="5" cellspacing="0"> |
| | 37 | <tr> |
| | 38 | <td> |
| | 39 | <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Symbols-Tips-icon.png?format=raw" width="50" height="50" alt="Tip"> |
| | 40 | </td> |
| | 41 | <td> |
| | 42 | To find the login information again, go to the Slice page and press the <b>Details</b> button in the appropriate row of the slice table. |
| | 43 | </tr> |
| | 44 | </table> |
| | 45 | |
| | 46 | |
| | 47 | <li>(Optionally) If your neighbor added you to their slice, login to your neighbor's slice. You will find your login information on the slice page for your neighbor's slice.</li> |
| | 48 | </ol> |
| | 49 | </td> |
| | 50 | <td> |
| | 51 | <img border="0" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/GREESC13/PortalSimpleLayer2Example/Graphics/log_in_v1.png?format=raw" alt="Login information for a VM" height="200" title="Login information for a VM" /> |
| | 52 | <br /> |
| | 53 | <b>Figure 9-1</b> <i>The </i>Details<i> page at </i>Utah InstaGENI</i>.</i> |
| | 54 | </td> |
| | 55 | </tr> |
| | 56 | </table> |
| | 57 | }}} |
| | 58 | |
| | 61 | |
| | 62 | |
| | 63 | === 10. Run your experiment === |
| | 64 | 1. '''Send IP traffic''' The first simple experiment that we will run is to verify the IP connectivity between our hosts. |
| | 65 | i. Check the interfaces of your nodes. In the terminal type: |
| | 66 | {{{ |
| | 67 | /sbin/ifconfig |
| | 68 | }}} |
| | 69 | You should see at least two interfaces: |
| | 70 | * The '''control interface'''. This is the interface you use to access the node, e.g. ssh into your host. The control interface is mainly used for control traffic, i.e. traffic for controlling the node and the experiment. The control interface usually has a publicly routable IP. |
| | 71 | * The '''data interface'''. This is the interface that is used for sending experimental traffic. This is the interface that connects to the other hosts of your experiment through GENI. The links between these interfaces are the ones that allow you to run non-IP experiments. The data interface is the one that has an IP that starts with 10. |
| | 72 | i. Fill in the worksheet, noting the name and IP address of the control and of the data interfaces for each node. |
| | 73 | {{{ |
| | 74 | #!html |
| | 75 | |
| | 76 | <table id="Table_02" border="0" cellpadding="5" cellspacing="0"> |
| | 77 | <tr> |
| | 78 | <td> |
| | 79 | <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/4NotesIcon_512x512.JPG?format=raw" width="50" height="50" alt="Note"> |
| | 80 | </td> |
| | 81 | <td> |
| | 82 | The "client" is the node in Utah and the "server" is the node at the GPO (in Massachusetts). The command prompt on each node says "client" or "server" respectively. |
| | 83 | </td> |
| | 84 | </tr> |
| | 85 | </table> |
| | 86 | }}} |
| | 87 | i. When we reserved the resources, we did not specify the IP address for the data interfaces. Instead, do this now. Configure the IP address on the data interface of each node using the desired data IP address from the worksheet : |
| | 88 | {{{ |
| | 89 | sudo /sbin/ifconfig <data i/f name> <desired data IP addr>/24 |
| | 90 | }}} |
| | 91 | For example: |
| | 92 | {{{ |
| | 93 | sudo /sbin/ifconfig eth3742 10.17.1.1/24 |
| | 94 | }}} |
| | 95 | i. Use `/sbin/ifconfig` to confirm the new IP address and mask for each node. The IP address should match what you set it to and the mask should be `255.255.255.0`. |
| | 96 | i. From the client, ping the server. From the terminal window that is logged in to the client type : |
| | 97 | {{{ |
| | 98 | ping <server data IP addr> -c 5 |
| | 99 | }}} |
| | 100 | For example: |
| | 101 | {{{ |
| | 102 | ping 10.17.1.2 -c 5 |
| | 103 | }}} |
| | 104 | An example output should look like : |
| | 105 | {{{ |
| | 106 | |
| | 107 | [sedwards@client ~]$ ping 10.17.1.2 -c 5 |
| | 108 | PING 10.17.1.2 (10.17.1.2) 56(84) bytes of data. |
| | 109 | 64 bytes from 10.17.1.2: icmp_req=1 ttl=64 time=183 ms |
| | 110 | 64 bytes from 10.17.1.2: icmp_req=2 ttl=64 time=91.2 ms |
| | 111 | 64 bytes from 10.17.1.2: icmp_req=3 ttl=64 time=91.1 ms |
| | 112 | 64 bytes from 10.17.1.2: icmp_req=4 ttl=64 time=91.1 ms |
| | 113 | 64 bytes from 10.17.1.2: icmp_req=5 ttl=64 time=91.2 ms |
| | 114 | |
| | 115 | --- 10.17.1.2 ping statistics --- |
| | 116 | 5 packets transmitted, 5 received, 0% packet loss, time 4004ms |
| | 117 | rtt min/avg/max/mdev = 91.156/109.579/183.129/36.775 ms |
| | 118 | }}} |
| | 119 | |
| | 120 | 2. '''Send non-IP traffic'''. GENI provides the capability of running non-IP experiments, since you can connect your hosts at Layer 2. For the purpose of this tutorial we have installed in all the hosts a very simple Layer 2 ping program that sends packets using a custom ethernet type. |
| | 121 | i. Disable the IP on your nodes (being careful to disable IP on the data interface NOT the control interface). In each of the terminals type: |
| | 122 | {{{ |
| | 123 | sudo /sbin/ifconfig <data i/f name> 0.0.0.0 |
| | 124 | }}} |
| | 125 | {{{ |
| | 126 | #!html |
| | 127 | |
| | 128 | <table id="Table_01" border="0" cellpadding="5" cellspacing="0"> |
| | 129 | <tr> |
| | 130 | <td> |
| | 131 | <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/warning-icon-hi.png?format=raw" width="50" height="50" alt="Warning"> |
| | 132 | </td> |
| | 133 | <td> |
| | 134 | Be extra careful to bring down the IP on the data interface, bringing down the IP on the control interface means that you will lose connectivity to your host. |
| | 135 | </td> |
| | 136 | </tr> |
| | 137 | </table> |
| | 138 | }}} |
| | 139 | i. Try again to ping from the client to the server. In the terminal window of the client type: |
| | 140 | {{{ |
| | 141 | ping <server data IP addr> -c 5 |
| | 142 | }}} |
| | 143 | For example: |
| | 144 | {{{ |
| | 145 | ping 10.17.1.2 -c 5 |
| | 146 | }}} |
| | 147 | This time the ping should timeout. |
| | 148 | i. Start the Layer 2 ping server: In the server terminal window, type: |
| | 149 | {{{ |
| | 150 | sudo /usr/local/bin/pingPlusListener <EtherType from worksheet> |
| | 151 | }}} |
| | 152 | i. From the client try to ping the server at layer 2. You will need the mac address of the data interface of the server, the name of the data interface of the client, and the !EtherType from your worksheet. In the terminal window of the client, type: |
| | 153 | {{{ |
| | 154 | sudo /usr/local/bin/pingPlus <server mac> <client i/f name> <Eth> |
| | 155 | |
| | 156 | where <server mac> is the server's data interface's MAC address, |
| | 157 | <client i/f name> is the client data interface' name, and |
| | 158 | <Eth> is the EtherType from the worksheet. |
| | 159 | }}} |
| | 160 | The result should look like : |
| | 161 | {{{ |
| | 162 | $ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 eth3742 10001 |
| | 163 | RQ:'5582+2067' to 2:0:9b:48:3e:20. |
| | 164 | RQ:5582+2067 from 2:0:3e:15:6c:ab. |
| | 165 | }}} |
| | 166 | |
| | 167 | |
| | 168 | |
| | 169 | |
