Changes between Version 2 and Version 3 of GENIExperimenter/Tutorials/NSDI13/PortalSimpleLayer2Example/ExecuteExperiment


Ignore:
Timestamp:
04/01/13 09:44:02 (11 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/NSDI13/PortalSimpleLayer2Example/ExecuteExperiment

    v2 v3  
    8787    You should see at least two interfaces:
    8888      * 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.
    89       * 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.
    90     i. Fill in the worksheet, noting the name and  IP address of the control and of the data interfaces for each node. The data interface is the one that has an IP that starts with 10.
     89      * 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.
     90    i. Fill in the worksheet, noting the name and  IP address of the control and of the data interfaces for each node.
    9191    '''Note''': 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.
    9292    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 :
    … …  
    9898    sudo /sbin/ifconfig mv7.90 10.10.1.1/24
    9999}}}
    100     i. Use `/sbin/ifconfig` to confirm the new IP address and mask for each node.
    101     i. From the client, ping the server. From the xterm that is logged in to the client type :
     100    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`.
     101    i. From the client, ping the server. From the terminal window that is logged in to the client type :
    102102{{{
    103103    ping <server data IP addr> -c 5
    … …  
    124124
    125125  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.
    126     i. Disable the IP in your nodes. First of all we are going to completely disable IP on our nodes. In each of the terminals type:
     126    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:
    127127    {{{
    128128  sudo /sbin/ifconfig <data i/f name> 0.0.0.0
    129129  }}}
    130     '''Note''': 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.
    131     i. Try again to ping from the client to the server. In the xterm of the client type:
     130     '''Note''': 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.
     131    i. Try again to ping from the client to the server. In the terminal window of the client type:
    132132{{{
    133133    ping <server data IP addr> -c 5
    … …  
    138138}}}
    139139    This time the ping should timeout.
    140     i. Start the Layer 2 ping server: In the server xterm, type:
     140    i. Start the Layer 2 ping server: In the server terminal window, type:
    141141    {{{
    142142  sudo /usr/local/bin/pingPlusListener <EtherType from worksheet>
    143143  }}}
    144     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 xterm of the client, type:
     144    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:
    145145    {{{
    146   sudo /usr/local/bin/pingPlus <server data mac addr> <client data i/f name> <EtherType from worksheet>
     146sudo /usr/local/bin/pingPlus <server mac> <client i/f name> <Eth>
     147
     148where <server mac> is the server's data interface's MAC address,
     149<client i/f name> is the client data interface' name, and
     150<Eth> is the EtherType from the worksheet.
    147151  }}}
    148152    The result should look like :
    149153    {{{
    150 [uncusr20@client ~]$ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 mv1.1 10001
     154$ sudo /usr/local/bin/pingPlus 02:00:9B:48:3E:20 mv1.1 10001
    151155RQ:'5582+2067' to 2:0:9b:48:3e:20.
    152156RQ:5582+2067 from 2:0:3e:15:6c:ab.
    … …  
    161165Congratulations you have run a Layer 2 experiment in GENI!
    162166
    163 
    164167= [wiki:GENIExperimenter/Tutorials/NSDI13/PortalSimpleLayer2Example/TeardownExperiment Next: Teardown Experiment] =