Changes between Version 7 and Version 8 of Internal/OpenFlow/ofTopology

Timestamp:

Jun 8, 2012, 5:20:08 AM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/ofTopology

@@ -26 +26 @@
   2.1 [#OVS OpenvSwitch] [[BR]]
   2.2 [#nfpga NetFPGA OpenFlow switch]
+ [#extra Extras] - With Mininet
+
 !OpenFlow is rather layer-agnostic, defining traffic rules based on a combination of any of the 12 packet header fields that may be used for matching under the !OpenFlow standard. These fields correspond to layers 1~4.    
 
@@ -231 +233 @@
 As for !OpenFlow switching, OVS nodes controlled by a BSN controller is the flexible, least-hassle choice for this task.  
 
+= Extras = #extra
+[http://yuba.stanford.edu/foswiki/bin/view/OpenFlow/Mininet Mininet], a SDN prototyping platform, is a great tool for proof-of-concept SDN experiments where you don't have physical SDN networks to experiment with, or setup of actual hardware is too cumbersome. The following setup was built with two VMs on external3:
+ 
+ * VM1(10.50.250.2): 3-switch, 3-host Mininet topology pointed to external controller in VM2:
+{{{
+# mn --topo=linear,3 --controller=remote --ip=10.50.250.17 --port=6633
+}}}   
+ * VM2(10.50.250.17): Flowvisor on port 6633, with a slice to point two switches to Floodlight instance on 6634
+
+ !FlowVisor configuration:
+ {{{
+# fvctl addFlowSpace 00:00:00:00:00:00:00:02 any "Slice:fl-1=7"
+# fvctl addFlowSpace 00:00:00:00:00:00:00:02 1000 any "Slice:fl-1=7"
+# fvctl addFlowSpace 00:00:00:00:00:00:00:01 1000 any "Slice:fl-1=7"
+ }}} 
+ Floodlight config alteration (in src/main/resources/config.properties):
+ {{{
+net.floodlightcontroller.core.FloodlightProvider.openflowport = 6634
+ }}}
 [[BR]]
 [[BR]]