Changes between Version 3 and Version 4 of HowTo/ShareALanOnAHWSwitch

Timestamp:

07/29/14 10:06:21 (10 years ago)

Author:

sedwards@bbn.com

Comment:

--

HowTo/ShareALanOnAHWSwitch

@@ -5 +5 @@
 Do the steps in the following order:
 
- 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.
+ 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.
 {{{
         omni createsliver MYSLICE http://www.gpolab.bbn.com/exp/OpenFlowOVS/pox-controller.rspec -a MYAGG --useSliceMembers
 }}}
- 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).  
- 3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be "host1" & "host2":
+ 2) Start your controller.  Log in to the VM from step (1) and run:
+{{{
+cd /tmp/pox
+./pox.py --verbose forwarding.l2_learning
+}}}
+ 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).  
+ 3) Reserve a VM at Stanford connected to a VM at MAX via a stitched link.  These nodes will be `host1` and `host2`:
 {{{
         stitcher createsliver MYSLICE2 max-stanford-stitched-flack.rspec --useSliceMembers
 }}}
- 4) Use performOperationalAction (poa) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
-   a) Make a file called lan_options.json containing the following text:
+ 4) Use performOperationalAction (`poa`) to share the stitched VLAN at Stanford. (Detailed instructions are in [2].)
+   a) Make a file called `lan_options.json` containing the following text:
 {{{
 {
@@ -22 +27 @@
 }
 }}}
-(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)):
-
+(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)):
    b) 
 {{{