| 1 | | = Tutorial on separating traffic on SB9 = |
| 2 | | |
| 3 | | Openflow 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 | | |
| 5 | | In 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]] |
| | 1 | = OpenFlow Tutorial 2: Two Controllers = |
| | 2 | |
| | 3 | In the Openflow model, traffic can be separated along may different boundaries. In this particular example we will run two separate controllers a. 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. |
| | 4 | |
| | 5 | The logical setup should look like:[[BR]] |
