Changes between Version 34 and Version 35 of GENIExperimenter/Tutorials/OpenFlowOVS/Appendix


Ignore:
Timestamp:
07/22/14 10:41:35 (5 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/OpenFlowOVS/Appendix

    v34 v35  
    4444         - NETWORK with the one in your worksheet.  If you are doing this at home, use a network between 10.20.30 - 10.20.49.
    4545
     46
     47
     48==== 1.3 Reserve Resources ===
     49
     50'''If you are using a private VLAN:'''   [[BR]]
     51  * Use your favorite resource reservation tool (Omni, jFed, Portal) to reserve your resources.  For example, if you are using Omni and the MAX aggregate:
     52{{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
     53
     54'''If you are using a shared VLAN:''' You will need to reserve your compute and flowspace resources separately using your favorite resource reservation tool (Omni, jFed, Portal).  For example, [[BR]]
     55{{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve compute resources) [[BR]]
     56{{{ omni -a max-ig-of createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve flowspace resources)
     57
     58
     59
     60== Useful tips ==
     61=== Which port is connected to which host ===
     62Run the learning pox controller with debug on  (use the command from the OVS tutorial) and start a ping from host1 to host2 and host3. Notice that the printout of pox will have lines like:
     63{{{
     64DEBUG:forwarding.l2_learning:installing flow for 02:b4:88:6d:83:f7.1 -> 02:36:8d:c2:b0:14.8
     65}}}
     66
     67The format after `for` and `->` is <MAC>.<PORT> so this way you know which port is connected to which host. To figure out the name for each port then it is simply `A<PORT>` so if host 1 is out of port 8, then the name is `A8`.
     68
     69=== Configuration files of controllers ===
     70For the proxy and the port_forwarding controllers you will need to modify the config files (port_forward.config, proxy.config) to use the appropriate IP dataplane IP addresses of your hosts to correctly configure your controllers.
     71
     72
     73
     74
     75
    4676{{{
    4777#!comment
     
    5686  2. Reserve the OpenFlow resources (for this you will need the controller public IP from the previous step). 
    5787}}}
    58 
    59 === 1.3 Reserve Resources ===
    60 
    61 '''If you are using a private VLAN:'''   [[BR]]
    62   * Use your favorite resource reservation tool (Omni, jFed, Portal) to reserve your resources.  For example, if you are using Omni and the MAX aggregate:
    63 {{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}}
    64 
    65 '''If you are using a shared VLAN:''' You will need to reserve your compute and flowspace resources separately using your favorite resource reservation tool (Omni, jFed, Portal).  For example, [[BR]]
    66 {{{ omni -a max-ig createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve compute resources) [[BR]]
    67 {{{ omni -a max-ig-of createsliver <YOUR_SLICE_NAME> ig-max.rspec }}} (to reserve flowspace resources)
    6888
    6989
     
    94114}}}
    95115
    96 == Useful tips ==
    97 === Which port is connected to which host ===
    98 Run the learning pox controller with debug on  (use the command from the OVS tutorial) and start a ping from host1 to host2 and host3. Notice that the printout of pox will have lines like:
    99 {{{
    100 DEBUG:forwarding.l2_learning:installing flow for 02:b4:88:6d:83:f7.1 -> 02:36:8d:c2:b0:14.8
    101 }}}
    102116
    103 The format after `for` and `->` is <MAC>.<PORT> so this way you know which port is connected to which host. To figure out the name for each port then it is simply `A<PORT>` so if host 1 is out of port 8, then the name is `A8`.
    104117
    105 === Configuration files of controllers ===
    106 For the proxy and the port_forwarding controllers you will need to modify the config files (port_forward.config, proxy.config) to use the appropriate IP dataplane IP addresses of your hosts to correctly configure your controllers.
     118