Changes between Version 9 and Version 10 of Tutorials/m0SDN/cTutorial2


Ignore:
Timestamp:
Mar 16, 2010, 5:25:50 AM (15 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Tutorials/m0SDN/cTutorial2

    v9 v10  
    1 = Tutorial on seprating traffic on SB9 =
    2 
    3 Open flow is a very versatile standard. You can read more about it [http://www.openflowswitch.org/ here]. As an example of the capabalities of open flow, and a tutorial on the capabilities of the orbit sandbox that was created specfically for the purposes of evaluating and testing openflow, we will run through a simple experiment. 
    4 
    5 In the Openflow model, traffic can be separated along may diffrent boundaries. In this particular example we're going to sperate bittorrent traffic in highnumbered ports. We will run two sperate controllers. The first will handle the production traffic, and run a commodity controller, SNAC. The second controller will manage the "experimental" bit-torrent traffic, and run a configured Nox controller. The data interfaces (eth0) of 4 nodes are connected to the open flow switch. The openflow switch is pre-configured to speak to a controller at sb9.orbit-lab.org:6633 The logical setup should look like:[[BR]]
     1= Tutorial on separating traffic on SB9 =
     2
     3Openflow is a very versatile standard. You can read more about it [http://www.openflowswitch.org/ here]. As an example of the capabilities of Openflow, and a tutorial on the capabilities of the orbit sandbox that was created specifically for the purposes of evaluating and testing Openflow, we will run through a simple experiment. 
     4
     5In the Openflow model, traffic can be separated along may different boundaries. In this particular example we're going to separate bittorrent traffic in high-numbered ports. We will run two separate controllers. The first will handle the production traffic, and run a commodity controller, SNAC. The second controller will manage the "experimental" bit-torrent traffic, and run a configured NOX controller. The data interfaces (eth0) of 4 nodes are connected to the open flow switch. The Openflow switch is pre-configured to speak to a controller at sb9.orbit-lab.org:6633 The logical setup should look like:[[BR]]
    66
    77[[Image(setup.jpg)]]
    … …  
    1111=== Splitter: Flowvisor - IP port 6633 ===
    1212
    13 The flowvisor tool serves as an intermediary between controllers. It splits traffic based on predefined rules. For this example we're running flowvisor on the SB9 console. While it is completely possible to complie your own flowvisor from scratch and install it in your home directory, a precompiled installation is located in /opt.  In order to properly steer the flowvisor tool, you must populate a flovisor-config.d directory with files that configure the flowvisor behavoir. This directory must be a subdirectory of the current working directory, as flow visor will create statistics files and logs in the current working directory. For the purposes of this demo we'll be using these files:
     13The flowvisor tool serves as an intermediary between controllers. It splits traffic based on predefined rules. For this example we're running flowvisor on the SB9 console. While it is completely possible to compile your own flowvisor from scratch and install it in your home directory, a precompiled installation is located in /opt.  In order to properly steer the flowvisor tool, you must populate a flovisor-config.d directory with files that configure the flowvisor behavior. This directory must be a subdirectory of the current working directory, as flow visor will create statistics files and logs in the current working directory. For the purposes of this demo we'll be using these files:
    1414
    1515{{{
    … …  
    1919}}}
    2020
    21 The defualt file primes the flowvisor and contains only the following lines:
     21The default file primes the flowvisor and contains only the following lines:
    2222
    2323{{{
    … …  
    5353}}}
    5454
    55 Finally the bittorent.guest directs high numbered ip port traffic to a controller on 6635:
     55Finally the bittorent.guest directs high numbered IP port traffic to a controller on 6635:
    5656{{{
    5757Id: 1001
    … …  
    175175}}}
    176176
    177 Finally on the Nox controller we should see events like this:
     177Finally on the NOX controller we should see events like this:
    178178{{{
    179179NOX 0.8.0~full~beta (nox_core), compiled Mar 14 2010 16:21:17
    … …  
    187187== ASIDE: TESTS for connectivity ==
    188188
    189 In case your expirement is failing, here are a few sanity checks.
     189In case your experiment is failing, here are a few sanity checks.
    190190
    191191=== The SNAC controller Web interface ===
    … …  
    208208}}}
    209209
    210 This should be done with independent sessions, as each session will start display traffic information. Once completed SNAC should report an increase in production  traffic, and 4 discovered hosts with the specified ips.
     210This should be done with independent sessions, as each session will start to display traffic information. Once completed SNAC should report an increase in production  traffic, and 4 discovered hosts with the specified IPs.
    211211
    212212=== High Numbered port Test ===
    … …  
    224224}}}
    225225
    226 If the traffic is split properly, your controller should register event similar to this:
     226If the traffic is split properly, your controller should register events similar to this:
    227227
    228228{{{