Changes between Version 59 and Version 60 of GENIExperimenter/Tutorials/ClickExample/Execute


Ignore:
Timestamp:
07/16/14 15:24:25 (5 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/ClickExample/Execute

    v59 v60  
    155155== 1c. Turn off internet protocol ==
    156156
    157 At this point, your network is still running IP. You can check by running a ping.
    158 
     157 i. At this point, your network is still running IP. You can check by running a ping.
     158 i. In your '''hostA''' terminal window, run this command:
    159159{{{
    160160#!div style="background: #ddf; border: 2px ridge; width: 685px; "
    161 In your '''hostA''' terminal window, run this command:
    162161{{{
    163162ping -c 3 hostB
     
    175174}}}
    176175}}}
    177 
    178 Since our experiment doesn't want IP, let's turn it off :
    179   i. On a local terminal run the following command four times, each time substituting the `<router_name>` with one of `top`, `bottom`, `left`, `right`:
    180 {{{
    181 #!div style="background: #ffd; border: 2px ridge; width: 685px; margin-left:50px;"
    182   {{{
     176 i. Since our experiment doesn't want IP, let's turn it off.
     177 i. On a local terminal run the following command four times, each time substituting the `<router_name>` with one of `top`, `bottom`, `left`, `right`:
     178{{{
     179#!div style="background: #ffd; border: 2px ridge; width: 685px;"
     180{{{
    183181remote-execute --useSliceAggregates <slicename> -m "sh ./stopIP.sh" \
    184182                                 --host <router_name>
    185183}}}
    186 
    187   You'll get output like this (the interface names may be different):
    188   {{{
     184You'll get output like this (the interface names may be different):
     185{{{
    189186Disabling IP on interface mv10.9
    190187Disabling IP on interface mv10.10
    191188}}}
    192189}}}
    193   i. Verify that IP is really off, try another ping.
     190 i. Verify that IP is really off, try another ping. On '''hostA''':
    194191{{{
    195192#!div style="background: #ddf; border: 2px ridge; width: 685px; "
    196 On '''hostA''':
    197193  {{{
    198194ping -c 3 hostb
    199195}}}
    200   The command should take twelve seconds to time out, then fail with output like this:
    201   {{{
     196The command should take twelve seconds to time out, then fail with output like this:
     197{{{
    202198PING hostB-link-B (10.10.6.2) 56(84) bytes of data.
    203199
     
    206202}}}
    207203}}}
     204
    208205= 2. Execute Experiment: Use custom routing to forward traffic over multi-path topology   =
    209206