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

Timestamp:

Jul 16, 2009, 4:42:50 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/SandBoxSetup

@@ -40 +40 @@
 Eth1 should be down because it compromises the routing table.    
 
-=== Making Console VLAN aware(7/15) ===
-The console was connected to a trunk port for use as the controller for the OpenFlow switch, For this, it had to be VLAN aware. [[BR]]
-The site refrenced: http://ubuntuforums.org/showthread.php?t=703387
+== Making the controller from the OpenFlow Reference System Code. (7/15) ==
+The !OpenFlow reference system contains code for a controller that makes an !OpenFlow switch into a learning switch. This was built (but not installed) on the Console by following instructions on the !OpenFlow site: http://www.openflowswitch.org/wk/index.php/Ubuntu_Install 
 
- 
+The console was then configured to be VLAN aware for VLANs 27,28, and 100. The site referenced: http://ubuntuforums.org/showthread.php?t=703387
+
+The interfaces, according to /etc/network/interfaces
+{{{
+# The primary network interface 
+auto eth0 eth1
+iface eth0 inet dhcp
+
+iface eth1 inet static
+address 192.168.100.28
+netmask 255.255.255.0 
+#  address 10.19.0.10
+#  netmask 255.255.0.0
+
+#auto eth1.27
+iface eth1.27 inet static
+address 10.19.0.10
+netmask 255.255.0.0
+
+#auto eth1.28
+iface eth1.28 inet static
+address 192.168.1.28
+netmask 255.255.255.0
+
+#auto eth1.100
+iface eth1.100 inet static
+address 172.16.100.1
+netmask 255.255.255.0
+}}} 
+
+Eth1 was then connected to a reconfigured trunk port that allowed VLANs 27,28, and 100. The commands used for re-configuring trunk port 0/37:
+
+{{{
+sw-sb09(config)# sh int gi 0/37 
+interface gigabitethernet 0/37
+  switchport mode trunk
+  switchport trunk allowed vlan 1,3,27-28
+  switchport trunk native vlan 1
+!
+sw-sb09(config)# int gi 0/37           
+sw-sb09(config-if)# no switchport trunk native vlan 1
+!sw-sb09(config-if)# exit                 
+!sw-sb09(config)# vlan 100
+!sw-sb09(config-vlan)# exit
+!sw-sb09(config)# interface vlan 100
+!sw-sb09(config-if)# ip address 172.16.100.10 255.255.255.0
+!sw-sb09(config-if)# interface gigabitethernet 0/37
+!sw-sb09(config-if)# switchport trunk native vlan 100
+!sw-sb09(config-if)# switchport trunk allowed vlan remove 1
+!sw-sb09(config-if)# switchport trunk allowed vlan remove 3
+!sw-sb09(config-if)# switchport trunk allowed vlan add 100
+!sw-sb09(config-if)# save
+}}}
+
+We later realized that VLAN interfaces for VLANs 27 and 28 also need to be assigned Ip addresses in order for the switch to be able to ping the controller's VLAN interfaces.
+{{{
+sw-sb09(config-if)# interface vlan 27
+!sw-sb09(config-if)# ip address 10.19.0.20 255.255.0.0
+!sw-sb09(config-if)# interface vlan 28 
+!sw-sb09(config-if)# ip address 192.168.1.20 255.255.255.0
+!sw-sb09(config-if)# save
+sw-sb09(config-if)# exit
+sw-sb09(config)# exit
+}}}
+
+pinging the interfaces...success. 
+{{{
+sw-sb09# ping 10.19.0.10
+PING 10.19.0.10 (10.19.0.10): 56 data bytes
+64 bytes from 10.19.0.10: icmp_seq=0 ttl=64 time=2.095 ms
+64 bytes from 10.19.0.10: icmp_s^C
+----10.19.0.10 PING Statistics----
+2 packets transmitted, 2 packets received, 0.0% packet loss
+round-trip min/avg/max = 1.097/1.596/2.095 ms
+sw-sb09# ping 192.168.1.28
+PING 192.168.1.28 (192.168.1.28): 56 data bytes
+64 bytes from 192.168.1.28: icmp_seq=0 ttl=64 time=2.100 ms
+64 bytes from 192.168.1.28: icmp_seq=1 ttl=64 time=1.013 ms
+^C
+----192.168.1.28 PING Statistics----
+2 packets transmitted, 2 packets received, 0.0% packet loss
+round-trip min/avg/max = 1.013/1.556/2.100 ms
+}}} 
+
+=== establishing switch-controller connections ===
+The code for the controller is found intuitively in the controller directory. Using `ptcp:[port]` as the connection method seems to work. 
+we also wanted an output and log of everything, so the full command was this (from the controller's directory) :
+
+./controller ptcp:6633 -v --log-file=test.log
+
+the first part of the output - you can see the OFPT_HELLO messages, negotiation of the !OpenFlow verison, the OFPT_FEATURES_REQUEST, and the switch's OFPT_FEATURES_REPLY: 
+{{{
+Jul 16 12:25:43|00001|vlog|WARN|opened log file test.log
+Jul 16 12:25:53|00002|rconn|DBG|tcp: entering ACTIVE
+Jul 16 12:25:53|00003|vconn|DBG|tcp:172.16.100.10:58499: sent (Success): hello (xid=0xacec814):
+
+Jul 16 12:25:53|00004|vconn|DBG|tcp:172.16.100.10:58499: received: hello (xid=0x9a45bcaf):
+
+Jul 16 12:25:53|00005|vconn|DBG|tcp:172.16.100.10:58499: negotiated OpenFlow version 0x97 (we support versions 0x97 to 0x97 inclusive, peer no later than version 0x97)
+Jul 16 12:25:53|00006|vconn|DBG|tcp:172.16.100.10:58499: sent (Success): features_request (xid=0x9eebe16b):
+
+Jul 16 12:25:53|00007|vconn|DBG|tcp:172.16.100.10:58499: sent (Success): set_config (xid=0xff52f51d): (sending flow expirations) miss_send_len=128
+
+Jul 16 12:25:53|00008|vconn|DBG|tcp:172.16.100.10:58499: received: features_reply (xid=0x9eebe16b): ver:0x97, dpid:12345678987
+n_tables:2, n_buffers:256
+features: capabilities:0x17, actions:0x3ff
+ 0(25): addr:00:12:e2:c8:1f:b5, config: 0, state:0x1
+ 1(26): addr:00:12:e2:c8:1f:b6, config: 0, state:0x1
+ 2(27): addr:00:12:e2:c8:1f:b7, config: 0, state:0x1
+ 3(28): addr:00:12:e2:c8:1f:b8, config: 0, state:0x1
+ 4(29): addr:00:12:e2:c8:1f:b9, config: 0, state:0x1
+ 5(30): addr:00:12:e2:c8:1f:ba, config: 0, state:0x1
+ 6(31): addr:00:12:e2:c8:1f:bb, config: 0, state:0x1
+ 7(32): addr:00:12:e2:c8:1f:bc, config: 0, state:0x1
+ 8(33): addr:00:12:e2:c8:1f:bd, config: 0, state:0x1
+ 9(34): addr:00:12:e2:c8:1f:be, config: 0, state:0x1
+ 10(35): addr:00:12:e2:c8:1f:bf, config: 0, state:0x1
+ 11(36): addr:00:12:e2:c8:1f:c0, config: 0, state:0x1
+}}}
+
+    
  
 
 
+
+[[BR]] 
+[[BR]]
+[[BR]]
 [wiki:Documentation/OpenFlow/ go back to OpenFlow index]