Changes between Version 4 and Version 5 of HowTo/ShareALanOnAHWSwitch

Timestamp:

07/29/14 10:12:44 (10 years ago)

Author:

sedwards@bbn.com

Comment:

--

HowTo/ShareALanOnAHWSwitch

@@ -20 +20 @@
 }}}
  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:
+   a) Make a file called `lan_options.json` containing the text below. (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))
 {{{
 {
@@ -27 +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)):
-   b) 
+   b) Run `poa` at each aggregate you should like to share the VLAN at: 
 {{{
 omni -V 3 -a stanford-ig poa MYSLICE2 geni_sharelan --optionsfile lan_options.json 
+omni -V 3 -a max-ig poa MYSLICE2 geni_sharelan --optionsfile lan_options.json 
 }}}
  4) Reserve a third VM (`host3`) on the shared VLAN:
@@ -41 +41 @@
 }}}
 
-You should have a controller running at an aggregate of your choice and controlling the hardware switch connecting the three VMs (two VMs at Stanford IG and one VM at MAX IG) which are all on the same shared VLAN.
+You should now have a controller running at an aggregate of your choice and controlling the hardware switch connecting the four VMs (two VMs at Stanford IG and two VM at MAX IG) which are all on the same shared VLAN.
 
 You should now be able to complete the exercise as described in [1].