Changes between Version 1 and Version 2 of HowTo/ShareALanOnAHWSwitch


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

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ShareALanOnAHWSwitch

    v1 v2  
    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 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.
    88        omni createsliver MYSLICE http://www.gpolab.bbn.com/exp/OpenFlowOVS/pox-controller.rspec -a MYAGG --useSliceMembers
    9 (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). 
    10 (3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be "host1" & "host2":
     9 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). 
     10 3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be "host1" & "host2":
    1111        stitcher createsliver MYSLICE2 max-stanford-stitched-flack.rspec --useSliceMembers
    12 (3) Use performOperationalAction (poa) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
     12 4) Use performOperationalAction (poa) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
    1313   a) Make a file called lan_options.json containing the following text:
     14{{{
    1415{
    15 "geni_sharelan_lanname": "lan0",
     16"geni_sharelan_lanname": "stitched0",
    1617"geni_sharelan_token": "ofstitchedlan"
    1718}
    18 
    19 (NOTE: "lan0" 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)):
     19}}}
     20(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)):
    2021
    2122   b) omni -V 3 -a stanford-ig poa MYSLICE2 geni_sharelan --optionsfile lan_options.json
    22 (4) Reserve a third VM on the shared VLAN:
     23 4) Reserve a third VM on the shared VLAN:
    2324        omni createsliver MYSLICE3 host3-stanford.rspec -a stanford-ig --useSliceMembers
    2425