Changes between Version 3 and Version 4 of HowTo/ShareALanOnAHWSwitch


Ignore:
Timestamp:
07/29/14 10:06:21 (5 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ShareALanOnAHWSwitch

    v3 v4  
    55Do the steps in the following order:
    66
    7  1) Reserve a VM and start your controller. I don't think it matters much which aggregate you pick for MYAGG. In fact, you don't need a GENI node at all as you could run the controller on your own machine.
     7 1) Reserve a VM for your controller. It does not matter much which aggregate you pick for `MYAGG`. In fact, you don't need a GENI node at all as you could run the controller on your own machine.
    88{{{
    99        omni createsliver MYSLICE http://www.gpolab.bbn.com/exp/OpenFlowOVS/pox-controller.rspec -a MYAGG --useSliceMembers
    1010}}}
    11  2) Edit the attached max-stanford-stitched-flack.rspec to point to the controller.  The controller should be accessed via the public IP of the node from step (1). 
    12  3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be "host1" & "host2":
     11 2) Start your controller.  Log in to the VM from step (1) and run:
     12{{{
     13cd /tmp/pox
     14./pox.py --verbose forwarding.l2_learning
     15}}}
     16 3) Edit the attached `max-stanford-stitched-flack.rspec` to point to the controller.  The controller should be accessed via the public IP of the node from step (1). 
     17 3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be `host1` and `host2`:
    1318{{{
    1419        stitcher createsliver MYSLICE2 max-stanford-stitched-flack.rspec --useSliceMembers
    1520}}}
    16  4) Use performOperationalAction (poa) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
    17    a) Make a file called lan_options.json containing the following text:
     21 4) Use performOperationalAction (`poa`) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
     22   a) Make a file called `lan_options.json` containing the following text:
    1823{{{
    1924{
     
    2227}
    2328}}}
    24 (NOTE: "stitched0" should be the name of the stitched VLAN from the previous step and "ofstitchedlan" should be the name you give the shared VLAN and is used by the RSpec in step (4)):
    25 
     29(NOTE: `stitched0` should be the name of the stitched VLAN from the previous step and `ofstitchedlan` should be the name you give the shared VLAN and is used by the RSpec in step (4)):
    2630   b)
    2731{{{