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


Ignore:
Timestamp:
Mar 14, 2010, 9:32:00 PM (14 years ago)
Author:
ssugrim
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/m0SDN/cTutorial2

    v2 v3  
    44on the orbit sandbox that was created specfically for the purposes of evaluating and testing openflow, we will run through a simple expirment.
    55
    6 In the Openflow model, traffic can be seperated along may diffrent boundaries. In this particular example we're going to sperate bittorrent traffic
    7 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 logical setup should look like:[[BR]]
     6In 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]]
    87
    98[[Image(setup.jpg)]]
     
    7675=== The SNAC controller Web interface ===
    7776
    78 The web interface for snac is accessible externally at http://sb9.orbit-lab.org (default credentials).
     77The 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]]
     78[[Image(snac.jpg)]]
     79
     80=== Inter-node traffic ===
     81
     82==== FIXME probably this will be a script detail ====
     83
     84Once the data interfaces are brought up on each of the 4 nodes, they should be discovered by SNAC. Assuming we place them all in the same IP subnet, it should be possible to ping each node from every other node. A simple test can be done as follows:
     85{{{
     86for node1-i:
     87
     88ssh root@node1-i
     89ifconfig eth0 up
     90ifconfig eth0 192.168.1.i
     91ping 192.168.1.(i-1)
     92
     93where i runs from 1 to 4.
     94}}}
     95
     96This 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.
     97
     98==