| 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. |
| | 1 | = !OpenFlow Tutorial 2: Multiple Controllers = |
| | 2 | |
| | 3 | In the !OpenFlow model, traffic can be separated along many different boundaries and flows can be controlled by multiple controllers. In this particular example we will run two separate controllers. The first one will handle the production traffic, and run a commodity controller, SNAC. The second controller will manage the "experimental" bit-torrent traffic, and run a NOX controller. The data interfaces (eth0) of 4 nodes are connected to the OpenFlow switch (in this case NEC IP8800). The OpenFlow switch is pre-configured to speak to a controller at console.sb9.orbit-lab.org:6633. |
