Changes between Version 6 and Version 7 of GENIExperimenter/Tutorials/OpenFlowOVS/HW/DesignSetup


Ignore:
Timestamp:
02/28/17 14:05:38 (7 years ago)
Author:
pjayanth@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/OpenFlowOVS/HW/DesignSetup

    v6 v7  
    1 = [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow Tutorial (Hardware Switch)] =
    2 {{{
    3 #!html
     1This page provides a guide on how to do the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight OpenFlowOVS tutorial] using the Hardware OpenFlow switches present at the IG racks. This can server as a general guide on how to use the HW switches.
    42
    5 <div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;">
    6 <img id="Image-Maps_5201305222028436" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Setup.jpg?format=raw" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" />
    7 <map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436">
    8 <area shape="rect" coords="18,18,135,110" href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/OpenFlowOVS/HW/DesignSetup" alt="" title=""    />
    9 <area shape="rect" coords="180,18,297,111" href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/OpenFlowOVS/Execute" alt="" title=""    />
    10 <area shape="rect" coords="344,17,460,110" href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/OpenFlowOVS/Finish" alt="" title=""    />
    11 <area shape="rect" coords="493,136,495,138" href="http://www.image-maps.com/index.php?aff=mapped_users_5201305222028436" alt="Image Map" title="Image Map" />
    12 </map>
    13 <!-- Image map text links - End - -->
    14 
    15 </div>
    16 }}}
    173[[PageOutline]]
    184== Step 1.  Obtain resources ==
    195
    20    * The topology used in this experiment is the same as the one used in the  [wiki:GENIExperimenter/Tutorials/OpenFlowOVS/DesignSetup OpenFlow using OVS] part of this tutorial: Three virtual machines (VMs) connected by an !OpenFlow switch. However this tutorial uses the hardware !OpenFlow switch on the rack instead of a software OVS switch.
    21    * If you have not reserved a controller yet, make sure to create a slice that will run the !OpenFlow controller by reserving a VM running the controller using the request RSpec [http://www.gpolab.bbn.com/exp/OpenFlowOVS/xen-openflow-controller-rspec.xml].  This RSpec is available at the Portal and is called ''XEN !OpenFlow Controller''''''''.
     6   * The topology used in this experiment is the same as the one used in the  [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup OpenFlow using OVS] part of this tutorial: Three virtual machines (VMs) connected by an !OpenFlow switch. However this tutorial uses the hardware !OpenFlow switch on the rack instead of a software OVS switch.
     7   * If you have not reserved a controller yet, make sure to create a slice that will run the !OpenFlow controller by reserving a VM running the controller using the request RSpec [https://raw.githubusercontent.com/GENI-NSF/geni-tutorials/master/OVSFloodLight/ControllerCustom_request_rspec.xml] .
    228
    239[[Image(GENIExperimenter/Graphics:SimpleHardwareOpenFlow.jpg,40%)]]
    … …  
    2511
    2612'''About GENI !OpenFlow switches''' [[BR]]
    27 GENI  offers access to hardware !OpenFlow switches. Each !OpenFlow switch, in most cases, can support only one controller.  There are two ways of slicing the controller flowspace:
    28    1. By VLAN id.  This is used when each slice has its own VLANs.   
    29    2. By IP addresses or by Ethernet type.  This is used when multiple slices share the same VLAN.  For example, the Mesoscale VLAN 1750 that has been set up as a shared VLAN on all GENI racks.
    30 Both approaches to slicing are covered in this tutorial.
     13GENI  offers access to hardware !OpenFlow switches. Each !OpenFlow switch, in most cases, can support only one controller.  On the IG racks the switch is sliced based on VLANs, so each VLAN is its own virtual datapath.
    3114
    3215To force the  links between the VMs to go through the rack !OpenFlow switch, the three VMs must be on separate physical hosts on the rack.  Our experiment will:
    … …  
    6952=== 2a. Configure the Controller for the Hardware Switch: Useful Tips ===
    7053==== Which port is connected to which host ====
    71 Run the learning pox controller with debug on ''(--verbose)'' (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:
    72 {{{
    73 DEBUG:forwarding.l2_learning:installing flow for 02:b4:88:6d:83:f7.1 -> 02:36:8d:c2:b0:14.8
    74 }}}
    7554
    76 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`.
     55To learn about the ports on which the Hosts are connected to the HW Switch, you need to run the Controller and execute a curl command.
    7756
    78 ==== Configuration files of controllers ====
    79 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.
     57=== 2b. Run your controller. ===
    8058
    81 Next run your controller as you did in the `OVS` experiment.
    82 
    83 ----
    84 = [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Introduction] =
    85 = [wiki:GENIExperimenter/Tutorials/OpenFlowOVS/Execute Next:  Execute] =
     59To get started with the Tutorial, follow the steps listed on the page [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute Running the Floodlight Controller]