Changes between Version 3 and Version 4 of GEC21Agenda/ScalingUp/Procedure/Execute


Ignore:
Timestamp:
10/17/14 22:32:15 (5 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC21Agenda/ScalingUp/Procedure/Execute

    v3 v4  
    2323
    2424=== 4.1 Login to nodes ===
    25 {{{
    26 #!html
    27 <table border="0">
    28       <tr>
    29 
    30        <td >
    31          <ol type='a'>
    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.
    34 
    35            <ol type='i'>
    36            <li> If you are using FireSSH, in the window that will pop up :
    37                 <ul>
    38                   <li> in the password field type in your passphrase</li>
    39                   <li> for the private key, browse to the file that has your private key
    40                    <li> <b> Press OK </b> </li>
    41                 </ul>
    42              </li>
    43            </ol>
    44            </li>
    45            <li><FONT COLOR="black">Repeat the previous step for the second VM.</font></li>
    46           </ol>
    47 
    48 <table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    49         <tr>
    50                 <td>
    51                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Symbols-Tips-icon.png?format=raw" width="50" height="50" alt="Tip">
    52                </td>
    53                <td>
    54                     To ssh from the command line, do the following (substituting the values shown on the screen):
    55 <pre>
    56 ssh USERNAME@HOSTNAME -p PORT
    57 </pre>
    58         </tr>
    59 </table>
    60 
    61        </td>
    62         <td>
    63         <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="325" title="Login information for a VM" />
    64 <br />
    65          <b>Figure 4-1</b> <i>Login to a VM</i>.</i>
    66        </td>
    67     </tr>
    68  </table>
    69 }}}
     25   a. Log into one of the `host` nodes (e.g. `host-1`) using `ssh`.
    7026
    7127== 5.  Execute Experiment ==
    7228
    73 === 5.1 Send IP traffic ===
    74 The first simple experiment that we will run is to verify the IP connectivity between our hosts.
     29=== 5.1 Test connectivity ===
     30Verify the IP connectivity between our hosts.
    7531 
    76     a. Check the interfaces of your nodes. In the terminal type:
    77     {{{
    78    sudo ifconfig
    79   }}}
    80     You should see at least two interfaces:
    81       * 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.
    82       * 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 address and mask that match what you configured before you reserved your resources.'''
    83     b. Fill in the worksheet, noting the name and  IP address of the control and of the data interfaces for each node. 
    84 {{{
    85 #!html
    8632
    87 <table id="Table_02" border="0" cellpadding="5" cellspacing="0">
    88         <tr>
    89                 <td>
    90                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Symbols-Tips-icon.png?format=raw" width="50" height="50" alt="Tip">
    91                </td>
    92                <td>
    93                     The command prompt on each node says "client" or "server" respectively.
    94                </td>
    95         </tr>
    96 </table>
    97 }}} 
    98     c. From the client, `ping` the server '''data plane interface'''. From the terminal window that is logged in to the client type :
    99 {{{
    100     ping <server data IP addr> -c 5
    101 }}}
    102        For example:
    103 {{{
    104     ping 10.1.1.2 -c 5
    105 }}}
    106     d. Now, `ping` the server '''control plane interface'''. From the terminal window that is logged in to the client type :
    107 {{{
    108     ping <server control IP addr> -c 5
    109 }}}
    110        For example:
    111 {{{
    112     ping 172.17.1.9  -c 5
    113 }}}
    114    
    115 
    116 === 5.2 Install and use `iperf` ===
    117     a. Install the `iperf` software on both nodes, by running the
    118     appropriate command below.
    119 
    120 {{{
    121 #!html
    122 <table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    123         <tr>
    124                 <td>
    125                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/instageni-logo.png?format=raw" width="50" height="50" alt="InstaGENI">
    126                </td>
    127                <td>
    128 If you are using resources at an InstaGENI aggregate do:
    129 <pre>
    130     sudo yum install iperf
    131 </pre>
    132 </td>
    133                    
    134         </tr>
    135 </table>
    136 }}}
    137 
    138 {{{
    139 #!html
    140 <table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    141         <tr>
    142                 <td>
    143                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/exogeni-logo.png?format=raw" width="50" height="50" alt="ExoGENI">
    144                </td>
    145                <td>
    146 If you are using resources at an ExoGENI aggregate do:
    147 <pre>
    148     sudo apt-get install iperf
    149     hash
    150 </pre>
    151 </td>
    152                    
    153         </tr>
    154 </table>
    155 }}}
    156 
    157 
    158     b. Start an `iperf` server on the server node:
    159 {{{
    160     iperf -s
    161 }}}
    162     c. Run an `iperf` client via the data plane:
    163 {{{
    164     iperf -c <server data IP addr>
    165 }}}
    166        For example:
    167 {{{
    168     iperf -c 10.1.1.2
    169 }}}
    170 ''What is the bandwidth of this link?''
    171 
    172 ''Why?''
    173     d. Run an `iperf` client via the control plane:
    174 {{{
    175 iperf -c <server control IP addr>
    176 }}}
    177        For example:
    178 {{{
    179 iperf -c 172.17.2.2
    180 }}}
    181 ''What is the bandwidth of this link?''
    182 
    183 ''Why?''
    184     e. Type `CTRL-C` on the server node to stop the `iperf` server.
    185 
    186 === 5.3 Bring down the server's data interface ===
    187 
    188     a. ExoGENI nodes run a service called "neuca" that managed network interfaces on the node.  To manually adjust the IP address, we must first disable neuca on both nodes.
    189 {{{
    190 sudo service neuca stop
    191 }}}
    192 {{{
    193 #!html
    194 <table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    195         <tr>
    196                 <td>
    197                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/exogeni-logo.png?format=raw" width="50" height="50" alt="ExoGENI">
    198                </td>
    199                <td>The ExoGENI "neuca" service controls a variety of network configuration details.</td>
    200                    
    201         </tr>
    202 </table>
    203 }}}
    204     b. From the client node, start pinging the server '''data plane interface''':
    205 {{{
    206     ping <server data IP addr>
    207 }}}
    208     c. On the server node, bring down the '''data plane interface'''
    209     (being careful to disable the data interface NOT the control interface):
    210 {{{
    211     sudo ifconfig <server data interface name> down
    212 }}}
    213 
    214 ''After you bring down the data interface, the pings should indicate that the destination is
    215 unreachable.''
    216 
    217 ''Why?''
    218 
    219 {{{
    220 #!html
    221 
    222 <table id="Table_01" border="0" cellpadding="5" cellspacing="0">
    223         <tr>
    224                 <td>
    225                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/warning-icon-hi.png?format=raw" width="50" height="50" alt="Warning">
    226                </td>
    227                <td>
    228                     Be extra careful to disable the IP on the data interface, bringing down the IP on the control interface means that you will lose connectivity to your host.
    229                </td>
    230         </tr>
    231 </table>
    232 }}}
    233 
    234 === 5.4 Bring down the server's control interface ===
    235     a. From the client node, start pinging the server '''control plane interface''':
    236 {{{
    237     ping <server control IP addr>
    238 }}}
    239     b. From the server node, bring down the '''control plane interface''' and try to ping it from the client node:
    240 {{{
    241     sudo ifconfig <server control interface name> down
    242 }}}
    243 
    244 ''Your ssh session should immediately hang.''' 
    245 
    246 ''Why?''
    247 
    248 ''After you bring down the control interface, the pings should indicate that the destination is
    249 unreachable.  Why?''
    250 
    251 {{{
    252 #!html
    253 <table id="Table_03" border="0" cellpadding="5" cellspacing="0">
    254         <tr>
    255                 <td>
    256                         <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Symbols-Tips-icon.png?format=raw" width="50" height="50" alt="Tip">
    257                </td>
    258                <td>
    259                     Unfortunately, in order to recover from a situation like this where you've lost the ability to login to your nodes, the only way to recover is to delete your resources and start again.
    260         </tr>
    261 </table>
    262 }}}
    263 
     33   a. Ping various nodes shown in the [picture].
     34   a. Run LabWiki script
     35 
    26436== 6.  Analyze Experiment ==
    26537
     
    26941 * Then type `exit` in your open terminal.
    27042
    271 Congratulations you have run an experiment in GENI!
    272 
    27343----
    27444