Changes between Version 8 and Version 9 of GEC17Agenda/GettingStartedWithGENI_I/Procedure/Execute


Ignore:
Timestamp:
07/12/13 18:36:20 (11 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GEC17Agenda/GettingStartedWithGENI_I/Procedure/Execute

    v8 v9  
    1 = [http://groups.geni.net/geni/wiki/GEC17Agenda/GettingStartedWithGENI_I/Procedure Getting Started With GENI - Part I] =
     1= [http://groups.geni.net/geni/wiki/Tutorials/ICDCS2013/GettingStartedWithGENI_I/Procedure Getting Started With GENI - Part I] =
    22{{{
    33#!html
    … …  
    3030       <td >
    3131         <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 
     32            <li>To login to a VM, again click the <b>i</b> in the circle.</li>
     33           <li>Now, click on the ssh link. If you have installed <a target="https://addons.mozilla.org/en-us/firefox/addon/firessh/"> FireSSH </a> a new tab will open up.</li>
     34           <li> In the window that will pop up :
     35                <ul>
     36                  <li> in the password field type in your passphrase</li>
     37                  <li> in the private key, browse to the file that has your private key
     38                   <li> <b> Press OK </b> </li>
     39                </ul>
     40             </li>
     41           <li><FONT COLOR="black">Repeat the previous step for the second VM.</font></li>
     42          </ol>
    3543
    3644<table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    … …  
    4048               </td>
    4149               <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.
     50                    To ssh from the command line, do the following (substituting the values shown on the screen):
     51<pre>
     52ssh USERNAME@HOSTNAME -p PORT
     53</pre>
    4354        </tr>
    4455</table>
    4556
    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>
    4957       </td>
    5058        <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" />
     59        <img border="0" src="http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_I/Graphics/client_ssh_highlight_v1.png?format=raw" alt="Login information for a VM"  height="350" title="Login information for a VM" />
    5260<br />
    53          <b>Figure 9-1</b> <i>The </i>Details<i> page at </i>Utah InstaGENI</i>.</i>
     61         <b>Figure 9-1</b> <i>Login to a VM</i>.</i>
    5462       </td>
    5563    </tr>
    … …  
    5866
    5967=== 4.2 Download and compile experiment software ===
    60   1. Download pingPlus software:
    61      a. Browse to: http://www.gpolab.bbn.com/local-sw/
    62      b. Select `pingPlus-0.2.tar.gz` and then press "Download".
    63      c. The software disclaimer will come up.  Press "Accept".
    64      d. When prompted save the file on your local machine.
    65      e. Upload pingPlus onto each of your nodes.
    66 {{{
    67 scp -P 30010 pingPlus-0.2.tar.gz sedwards@pc1.instageni.gpolab.bbn.com:.
    68 }}}
    69   2. Compile pingPlus
    70 {{{
    71 ssh into node
     68 1. In the first VM, download the pingPlus software:
     69{{{
     70wget http://www.gpolab.bbn.com/experiment-support/Layer2Ping/pingPlus-0.2.tar.gz
     71}}}
     72 2. Decompress the pingPlus software:
     73{{{
    7274tar xvfz pingPlus-0.2.tar.gz
     75}}}
     76 3. Compile the pingPlus software:
     77{{{
    7378cd pingPlus-0.2
    7479make
    7580}}}
     81 4. Your output should look like this:
     82{{{
     83client:~% wget http://www.gpolab.bbn.com/experiment-support/Layer2Ping/pingPlus-0.2.tar.gz
     84--2013-07-05 09:32:26--  http://www.gpolab.bbn.com/experiment-support/Layer2Ping/pingPlus-0.2.tar.gz
     85Resolving www.gpolab.bbn.com (www.gpolab.bbn.com)... 192.1.249.17
     86Connecting to www.gpolab.bbn.com (www.gpolab.bbn.com)|192.1.249.17|:80... connected.
     87HTTP request sent, awaiting response... 200 OK
     88Length: 4726 (4.6K) [application/x-gzip]
     89Saving to: `pingPlus-0.2.tar.gz'
     90
     91100%[================================================================================================================================================================>] 4,726       --.-K/s   in 0.07s
     92
     932013-07-05 09:32:27 (69.1 KB/s) - `pingPlus-0.2.tar.gz' saved [4726/4726]
     94
     95client:~% tar xvfz pingPlus-0.2.tar.gz
     96./._pingPlus-0.2
     97pingPlus-0.2/
     98pingPlus-0.2/._Makefile
     99pingPlus-0.2/Makefile
     100pingPlus-0.2/._packetFunctions.c
     101pingPlus-0.2/packetFunctions.c
     102pingPlus-0.2/._packetFunctions.h
     103pingPlus-0.2/packetFunctions.h
     104pingPlus-0.2/._pingPlus.c
     105pingPlus-0.2/pingPlus.c
     106pingPlus-0.2/._pingPlusListener.c
     107pingPlus-0.2/pingPlusListener.c
     108pingPlus-0.2/._README
     109pingPlus-0.2/README
     110client:~% cd pin
     111pingPlus-0.2/        pingPlus-0.2.tar.gz
     112client:~% cd pingPlus-0.2
     113client:~/pingPlus-0.2% make
     114gcc    -c -o packetFunctions.o packetFunctions.c
     115gcc    -c -o pingPlusListener.o pingPlusListener.c
     116gcc  packetFunctions.o pingPlusListener.o  -o pingPlusListener
     117gcc    -c -o pingPlus.o pingPlus.c
     118gcc  packetFunctions.o pingPlus.o -o pingPlus
     119}}}
     120
     121  5. Repeat the above on the second VM.
    76122
    77123== 5.  Execute Experiment ==
    78124
    79 === 5.1 Run your experiment ===
    80   1. '''Send IP traffic''' The first simple experiment that we will run is to verify the IP connectivity between our hosts.
    81     i. Check the interfaces of your nodes. In the terminal type:
     125=== 5.1 Send IP traffic ===
     126The first simple experiment that we will run is to verify the IP connectivity between our hosts.
     127
     128    1. Check the interfaces of your nodes. In the terminal type:
    82129    {{{
    83130   /sbin/ifconfig
    … …  
    86133      * 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.
    87134      * 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.
    88     i. Fill in the worksheet, noting the name and  IP address of the control and of the data interfaces for each node. 
     135    1. Fill in the worksheet, noting the name and  IP address of the control and of the data interfaces for each node. 
    89136{{{
    90137#!html
    … …  
    93140        <tr>
    94141                <td>
    95                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/4NotesIcon_512x512.JPG?format=raw" width="50" height="50" alt="Note">
     142                        <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/4NotesIcon_512x512.png?format=raw" width="50" height="50" alt="Note">
    96143               </td>
    97144               <td>
    98                     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.
     145                    The command prompt on each node says "client" or "server" respectively.
    99146               </td>
    100147        </tr>
    101148</table>
    102149}}} 
    103     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 :
     150    1. 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 :
    104151{{{
    105152    sudo /sbin/ifconfig <data i/f name> <desired data IP addr>/24
    … …  
    109156    sudo /sbin/ifconfig eth3742 10.17.1.1/24
    110157}}}
    111     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`.
    112     i. From the client, ping the server. From the terminal window that is logged in to the client type :
     158    1. 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`.
     159    1. From the client, ping the server. From the terminal window that is logged in to the client type :
    113160{{{
    114161    ping <server data IP addr> -c 5
    … …  
    134181}}}
    135182
    136   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.
    137     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:
     183
     184=== 5.1 Send non-IP traffic ===
     185
     186GENI provides the capability of running non-IP experiments, since you can connect your hosts at Layer 2. For the purpose of this tutorial we will use a very simple Layer 2 ping program that sends packets using a custom ethernet type.
     187
     188    1. 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:
    138189    {{{
    139190  sudo /sbin/ifconfig <data i/f name> 0.0.0.0
    … …  
    153204</table>
    154205}}}
    155     i. Try again to ping from the client to the server. In the terminal window of the client type:
     206    1. Try again to ping from the client to the server. In the terminal window of the client type:
    156207{{{
    157208    ping <server data IP addr> -c 5
    … …  
    162213}}}
    163214    This time the ping should timeout.
    164     i. Start the Layer 2 ping server: In the server terminal window, type:
    165     {{{
    166   sudo /usr/local/bin/pingPlusListener <EtherType from worksheet>
     215    1. Start the Layer 2 ping server: In the server terminal window, type:
     216    {{{
     217  sudo ~/pingPlus-0.2/pingPlusListener <EtherType from worksheet>
    167218  }}}
    168     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:
    169     {{{
    170 sudo /usr/local/bin/pingPlus <server mac> <client i/f name> <Eth>
     219    1. 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:
     220    {{{
     221sudo ~/pingPlus-0.2/pingPlus <server mac> <client i/f name> <Eth>
    171222
    172223where <server mac> is the server's data interface's MAC address,
    … …  
    176227    The result should look like :
    177228    {{{
    178 $ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 eth3742 10001
     229$ sudo ~/pingPlus-0.2/pingPlus 02:00:9B:48:3E:20 eth3742 10001
    179230RQ:'5582+2067' to 2:0:9b:48:3e:20.
    180231RQ:5582+2067 from 2:0:3e:15:6c:ab.
    181232}}}
    182233
    183 
    184 
    185 
    186234== 6.  Analyze Experiment ==
     235
     236Now is when you would ordinarily analyze the results of your experiment.
    187237
    188238=== 6.1 Logout of your nodes ===
    … …  
    195245----
    196246
    197 = [wiki:GEC17Agenda/GettingStartedWithGENI_I/Procedure Introduction] =
    198 = [wiki:GEC17Agenda/GettingStartedWithGENI_I/Procedure/Finish Next:  Finish] =
     247= [wiki:Tutorials/ICDCS2013/GettingStartedWithGENI_I/Procedure Introduction] =
     248= [wiki:Tutorials/ICDCS2013/GettingStartedWithGENI_I/Procedure/Finish Next:  Finish] =