Changes between Version 2 and Version 3 of Internal/OpenFlow/ofTopology

Timestamp:

Nov 7, 2011, 11:29:08 PM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/ofTopology

@@ -172 +172 @@
 3. Point ovs-vswitchd to the !OpenFlow controller. 
 {{{
- ovs-vsctl set-controller br0 tcp:172.16.0.14:6633
-}}}
-In this example, the OVS process is pointed to a BSN controller (kvm-big) on 172.16.0.14, listening on port 6633^1^. `ovs-vsctl` will spit out a bunch of messages as it attempts to connect to the controller:
-{{{
- ##screencap here 
+ovs-vsctl set-controller br0 tcp:172.16.0.14:6633
+}}}
+In this example, the OVS process is pointed to a BSN controller (kvm-big) on 172.16.0.14, listening on port 6633^1^. With a properly initialized and configured database, `ovs-vswitchd` will spit out a bunch of messages as it attempts to connect to the controller. Its output should look something similar to this:
+{{{
+root@node1-4:/opt/openvswitch-1.2.2# vswitchd/ovs-vswitchd unix:/usr/local/var/run/openvswitch/db.sock --pidfile --detach
+Nov 07 17:37:02|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: connecting...
+Nov 07 17:37:02|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: connected
+Nov 07 17:37:02|00003|bridge|INFO|created port br0 on bridge br0
+Nov 07 17:37:02|00004|bridge|INFO|created port eth0.101 on bridge br0
+Nov 07 17:37:02|00005|bridge|INFO|created port eth0.102 on bridge br0
+Nov 07 17:37:02|00006|ofproto|INFO|using datapath ID 0000002320b91d13
+Nov 07 17:37:02|00007|ofproto|INFO|datapath ID changed to 000002972599b1ca
+Nov 07 17:37:02|00008|rconn|INFO|br0<->tcp:172.16.0.14:6633: connecting...
 }}} 
-Given that you have a controller ready, the node should be usable once the virtual switch(es) connect(s) to the controller. The function of the switch will be determined by the flow matching rules generated by the conteoller. 
+The !OpenvSwitch !OpenFlow switch should be functional as soon as it finds and connects to the controller. As you can see above, a DPID is chosen at random; if a random DPID does not suit your needs, a DPID may be specified manually using ovs-vsctl:
+{{{
+ovs-vsctl set bridge <mybr> other-config:datapath-id=<datapathid>
+}}}  
+Where <datapathid> is a 16-digit hex value. For our network node, this becomes: 
+{{{
+ovs-vsctl set bridge br0 other-config:datapath-id=0000009900113300
+}}} 
+
 == 2.2 NetFPGA !OpenFlow switch == #nfpga