Changes between Version 3 and Version 4 of Tutorials/m0SDN/cTutorial2

Timestamp:

Mar 14, 2010, 9:59:41 PM (14 years ago)

Author:

ssugrim

Comment:

—

Tutorials/m0SDN/cTutorial2

@@ -1 +1 @@
 = Tutorial on seprating traffic on SB9 =
 
-Open flow is a very versatile standard. You can read more about it here. As an example of the capabalities of open, and a tutorial to the setup
-on the orbit sandbox that was created specfically for the purposes of evaluating and testing openflow, we will run through a simple expirment.
+Open flow is a very versatile standard. You can read more about it here. As an example of the capabalities of open flow, and a tutorial on the orbit sandbox that was created specfically for the purposes of evaluating and testing openflow, we will run through a simple experiment.  
 
-In the Openflow model, traffic can be seperated 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 comodity controller, SNAC. The second controller will manage the bit-torrent traffic, and run a configured Nox controller. The data interfaces (eth0) of 4 nodes are connected to the open flow switch. The logical setup should look like:[[BR]]
+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 console.sb9.orbit-lab.org:6633 The logical setup should look like:[[BR]]
 
 [[Image(setup.jpg)]] 
 
+== Controllers ==
 
-== Flowvisor ==
+=== Splitter: Flowvisor - IP port 6633 ===
 
-The flowvisor tool server as an intermediary between controllers. It splits traffic based on predefined rules. For our configuration we're running
-flowvisor on SB9. While it is completely possible to complie your own flowvisor from scratch and install it in your home directory, a precompiled flowvisor 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. For the purposes of this demo we'll be using these files:
+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:
 
 {{{
@@ -71 +70 @@
 }}}
 
+This setup of flowvisor will split along IP port boundaries. If we want to direct more traffic to the experiment, we simply manipulate the flow rules. 
+
+=== Production: SNAC - IP port 6634 ===
+On console.sb9 SNAC is preconfigured to listen to port 6634. For the purposes of this example, SNAC will handle the production traffic and as such is not configured to do anything beyond the scope of a simple learning switch. The web interface for SNAC is accessible externally at http://sb9.orbit-lab.org (default credentials).
+
+=== Experimental: NOX - IP port 6635 ===
+
+For demonstration purposes we will have this controller simply pass traffic. We could manipulate this traffic by configuring NOX to behave differently, or by running a completely different controller that listens on port 6635. Since our model is that "production" traffic is handled by a controller at port 6634 and experimental traffic is handled by a controller at port 6635, it is expected that the states of the port 6635 controller be transient. 
+
+
 == TESTS for connectivity ==
 
 === The SNAC controller Web interface ===
 
-The web interface for SNAC is accessible externally at http://sb9.orbit-lab.org (default credentials). Assuming your flowvisor is passing along high priority traffic to snac,  the this:[[BR]]
+ Assuming your flowvisor is passing along high priority traffic to snac,  the this:[[BR]]
 [[Image(snac.jpg)]]