Changes between Version 6 and Version 7 of Internal/OpenFlow/Controllers/FlowVisor

Timestamp:

Sep 16, 2010, 6:56:46 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Controllers/FlowVisor

@@ -59 +59 @@
 the primary means of configuring flowvisor is via ''fvctl''.Unlike older versions of nox, you don't need to create configuration scripts, which is great. Here, we'll describe how to use ''fvctl'' through an example run based on the flowvisor webpage.   
 
-=== A testrun setup ===
+=== The testrun Setup ===
+In this setup, !FlowVisor is started on port 6655, with an instance of nox listening on port 6656. A !FlowVisor slice is created to listen to any controllers using port 6656 (in this case, our test NOX instance). A single virtual switch was made to listen for controllers on port 6655, whereby its control is given to NOX by flowvisor. 
+
  1. ''set up config file.'' Basing it on the default-config.xml file that comes with the flowvisor install:
 {{{
@@ -114 +116 @@
 }}} 
 The datapath should come up as "connected" under ''showswitch''.
+
+== Moving controllers to slices ==
+
+ 1. ''edit default port for snac/noxcore.'' The default settings for snac (e.g. what port it uses, ect) is found in /etc/default/noxcore. Edit the port it uses for the control channel from 6633 to the new port:
+{{{
+ OF_LISTEN="-i ptcp:6634"
+}}}
+
+ 2. start flowvisor and set up slices:
+{{{
+ flowvisor config.xml 6633 &
+ fvctl createSlice orbit-snac tcp:172.16.0.4:6634 foo@domain.com
+ fvctl addFlowSpace all 10000 any "Slice:orbit-snac=7"
+}}}
+
+ 3. restart snac:
+{{{
+ /etc/init.d/noxcore restart
+}}}
+
+!FlowVisor should now be managing the slice for SNAC.