Changes between Version 12 and Version 13 of Internal/OpenFlow/Notes

Timestamp:

Aug 11, 2009, 2:53:17 AM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Notes

@@ -38 +38 @@
 
  * can a virtual switch be loaded with a default flow table that would allow it to function, at least until its table times out?
+
+=== when openflow.conf gets messed up (6/22) ===
+One method to rewrite the !OpenFlow configuration is to delete openflow.conf directly through the switch, then use the `setvsi` command to set the new virtual switches up. This should be unnecessary, but it happened to be effective when old configurations did not seem to go away despite editing the .conf file using a PC. 
+
+{{{
+> cd /mnt/
+> rm openflow.conf 
+remove 'openflow.conf'? y
+> setvsi 1 1,3,5,7,9,11,13,15,2.1 tcp 172.16.4.224 dpid 0x0123456789ab
+> setvsi 2 17,19,21,23,25,27,29,31,2.2 tcp 172.16.4.180 dpid 0x012345678abc
+> setvsi 3 33,35,37,39,41,43,45,47,2.3 tcp 172.16.4.64 dpid 0x01234567abcd
+> showswitch
+vlan    ports                                           secure channel      
+----    -----                                           --------------      
+1       1, 3, 5, 7, 9, 11, 13, 15, 2.1                  disconnected        
+2       17, 19, 21, 23, 25, 27, 29, 31, 2.2             disconnected        
+3       33, 35, 37, 39, 41, 43, 45, 47, 2.3             disconnected        
+}}}
+
+
+However, it seems like it is not possible to set `double-wide-mode`, or `no-save` through the CLI. These have to be added by editing openflow.conf using the PC. 
+
 
 === SSL setup, things to know for the next day. (7/13) ===
@@ -223 +245 @@
 Whether it is NOX or the !Openflow Regression Suite it is all in lots of C. Trying to make Ruby work with C seemed a bit too messy for our own good, so we sent an email to the NOX developer's mailing list in hopes of some elucidation of how to create a Ruby interface to !OpenFlow, instead of Python (which is what NOX does, as described [http://noxrepo.org/wp/?page_id=2 here]) 
 
-==== some experimentation with Ruby sockets ====
-
-The switch will keep trying to contact a controller, regardless of whether the controller is active. This happens once every 15 seconds or so, and can be seen with a very simple script that listens on TCP 6633 (the default !OpenFlow port) on the console's !OpenFlow VLAN interface, which has the IP address 172.16.100.1: 
-
-{{{
-#!/usr/bin/ruby -w
-require 'socket'
-
-# allow the switch to try to establish a connection
-ofpsock = TCPserver.new("172.16.100.1", 6633)
-
-#listen to see what port the switch is using
-while (session = ofpsock.accept)
-        t = Time.now   # to see interval of messages 
-        peer = session.peeraddr
-        puts "#{peer[1]}  #{peer[2]}    #{t.to_s.split[3]}"
-session.close
-end
-
-
-}}}
-
-You get:
-{{{
-55354   172.16.100.10     20:53:22 
-55353   172.16.100.10     20:53:37 
-55352   172.16.100.10     20:53:52 
-55351   172.16.100.10     20:54:07 
-...
-
-from a later experiment
-
-55080   172.16.100.10     22:12:53
-55079   172.16.100.10     22:13:08
-
-actually consistent with bwm-ng logs
-
-}}}
-
-The first column shows the switch's port. 172.16.100.10 is the vlan interface IP address for the Openflow VLAN on the switch, so you know it is the !OpenFlow switch trying to establish a connection with the controller. To be honest it's not clear if the timestamps would reflect the speed of the code or the activity of the switch. 
-
-
- 
-
-
-
-
-
-
-
-
-
-