Changes between Version 11 and Version 12 of Internal/OpenFlow/OFIntro

Timestamp:

Aug 1, 2013, 9:20:54 PM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/OFIntro

@@ -21 +21 @@
  * [http://www.projectfloodlight.org/floodlight/ Floodlight] : A development-friendly controller platform 
  * [http://mininet.org/ mininet] : !OpenFlow network prototyping tool/emulation
+ * [https://bitbucket.org/barnstorm/of-dissector Wireshark+OF dissector] : Wireshark with a plugin for !OpenFlow messages
  * [http://docs.projectfloodlight.org/display/floodlightcontroller/Cbench+(New) cbench] : Controller benchmarking tool 
  * [http://www.openflow.org/wk/index.php/Liboftrace liboftrace] : !OpenFlow message parser/analyzer for pcap files   
- * [https://bitbucket.org/barnstorm/of-dissector Wireshark+OF dissector] : Wireshark with a plugin for !OpenFlow messages
+ * [http://onlab.us/flowvisor.html FlowVisor] : A network hypervisor  
 
 This makes things easy since you can image multiple nodes with the same image, and pick and choose what to run where. 
@@ -147 +148 @@
 If each controller is running on its own host (machine, VM, etc.), there is little to change; if you have hosts A,B, and C, and Floodlight instances running on each, switches can be pointed to targets A:6633, B:6633, C:6633, or any combination thereof (switches can be pointed to multiple controllers).  
 
-=== 2.1.2 On the same host === #2_1_2
+=== 2.1.2 On the same host === #s2_1_2
 ==== The Floodlight configuration file ====
 Multiple instances of Floodlight may be run on the same host, as long as each controller listens on a separate set of sockets. In this case, all controllers would be on the same IP address(es), so you must change the ports they are listening on. These ports include the !OpenFlow control port (TCP 6633), REST API (TCP 8080), and debug (TCP 6655). 
@@ -218 +219 @@
 This should launch three backgrounded instances of Floodlight. 
 
-== 2.2 With !FlowVisor (Network virtualization/slicing) == #fv
+== 2.2 Network virtualization/slicing == #fv
 A more typical case you might encounter is a network that is sliced, or virtualized. 
 
@@ -266 +267 @@
 
 === 2.2.3 On the same host ===
-As with the case of multiple controllers on the same VM/host, you must be careful that neither !FlowVisor nor the controllers listen on the same sets of ports. For the multiple controllers, this can be avoided as described in [#2_1_2 Section 2.1.2]. !FlowVisor and Floodlight conflict on ports 6633 and 8080.     
+As with the case of multiple controllers on the same VM/host, you must be careful that neither !FlowVisor nor the controllers listen on the same sets of ports. For the multiple controllers, this can be avoided as described in [#s2_1_2 Section 2.1.2]. !FlowVisor and Floodlight conflict on ports 6633 and 8080.     
 
 ----
@@ -278 +279 @@
  [#loft 3.4 liboftrace] [[BR]]
  [#ws 3.5 Wireshark] [[BR]]
+ [#fvisor 3.6 FlowVisor] [[BR]]
 
 Note, the following examples are for Ubuntu, since that's what is used at WINLAB. A quick search will often bring up hints/steps for CentOS/RHEL and OSX, but for the most part, you will have to experiment a bit. 
@@ -478 +480 @@
 make install
 }}}
+Where OF_PATH is where you had cloned the !OpenFlow repository to. 
 
 === run ===
@@ -633 +636 @@
 
 You should see openflow.so in the list of plugins if you go to Help > About Wireshark > plugins. 
+
+=== 3.6 FlowVisor === #fvisor
+website: http://onlab.us/flowvisor.html