Changes between Version 32 and Version 33 of GENIExperimenter/Tutorials/ClickExample/Execute


Ignore:
Timestamp:
07/16/14 10:51:41 (5 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

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

    v32 v33  
    6060  i. In one terminal type
    6161  {{{
    62   ssh -A hostA
     62ssh -A hostA
    6363  }}}
    6464  and in the other
    6565  {{{
    66   ssh -A hostB
     66ssh -A hostB
    6767  }}}
    6868
     
    9696== 1b. Configure your routers ==
    9797We are going to use remote execution to configure our routers. For this specific command we will use ssh directly.
    98   i. On a local terminal run the following command four times, each time substituting the <router_name> with one of the top, bottom, left, right:
    99   {{{
    100    ssh -A <router_name> "/local/click-example/extractClickConfig.py "
     98  i. On a local terminal run the following command four times, each time substituting the `<router_name>` with one of `top`, `bottom`, `left`, `right`:
     99  {{{
     100ssh -A <router_name> "/local/click-example/extractClickConfig.py"
    101101  }}}
    102102  You'll get output something like this:
     
    111111Done.
    112112}}}
    113   (If you are prompted for a password, check to make sure that you provided the -A switch in your ssh command above.)
    114 
    115   i. The extractClickConfig script produces router configurations for your experiment. It also creates a diagram of your experiment. Get a copy locally from one of the routers, by typing in a local terminal:
    116   {{{
    117  scp top:myslice.png ./
     113  (If you are prompted for a password, check to make sure that you provided the `-A` switch in your ssh command above.)
     114
     115  i. The `extractClickConfig` script produces router configurations for your experiment. It also creates a diagram of your experiment. Get a copy locally from one of the routers, by typing in a local terminal:
     116  {{{
     117scp top:myslice.png ./
    118118}}}
    119119  i. Open the diagram in your browser or your favorite image viewing program.
    120120
    121   Your slice will look something like the one below. The overall configuration should be the same, with two end hosts, named hostA and hostB, and four routers (top, left, right, bottom) in a diamond configuration. The host names, interface names, and MAC addresses will be different, depending on the actual resources assigned to your slice.
     121  Your slice will look something like the one below. The overall configuration should be the same, with two end hosts, named `hostA` and `hostB`, and four routers (`top`, `left`, `right`, `bottom`) in a diamond configuration. The host names, interface names, and MAC addresses will be different, depending on the actual resources assigned to your slice.
    122122
    123123[[Image(GENIExperimenter/Graphics:clickexample_myslice.png, 25%)]]
     
    161161  i. Verify that IP is really off, try another ping. On '''hostA''':
    162162  {{{
    163   ping -c 3 hostb
     163ping -c 3 hostb
    164164}}}
    165165  The command should take twelve seconds to time out, then fail with output like this:
     
    269269The '''left''' router configuration is much simpler.  In a local terminal type:
    270270{{{
    271  ssh -A left "cat left.click"
     271ssh -A left "cat left.click"
    272272}}}
    273273  The output will look like :
     
    297297  i. In a local terminal type:
    298298  {{{
    299   ssh -A top "tail -f /tmp/click.log"
     299ssh -A top "tail -f /tmp/click.log"
    300300}}}
    301301  i. Go to your window for hostA, where your '''nc''' command is still running. Type a message into this window. You should see a log message in three of your four router windows. In this example, you might see: