Changes between Version 4 and Version 5 of Internal/OpenFlow/WimaxOpenV

Timestamp:

Sep 20, 2010, 11:38:40 PM (14 years ago)

Author:

ssugrim

Comment:

—

Internal/OpenFlow/WimaxOpenV

@@ -85 +85 @@
 ----
 
-We can create Virtual interfaces with the IP command [http://linux.die.net/man/8/ip IP manual] Something of the form
+We can create Virtual interfaces with the [http://linux.die.net/man/8/ip ip] command Something of the form
 {{{
 >ip link add type veth
 }}}
+These interfaces are "internal" to the machine and have no-external meaning. They are similar to the named pipes or unix sockets.  The internal virtual switch will communicate with other virtual elements in the machine via these virtual interfaces. 
 
-Once this is created, we can add the virtual interface to the open flow switch with ovs-dpctl.
+Once this is created, we can add the virtual interface to the open flow switch with the [http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities/ovs-dpctl.8 ovs-dpctl].
 {{{
 >ovs-dpctl add-dp dp0
@@ -106 +107 @@
 }}}
 
+There is a separate daemon that manages the virtual open flow switch, In the current config we'll use it in --out-of-band mode. Thus the interface doesn't need an IP of it's own. The daemon can be started with the [http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities/ovs-openflowd.8 ovs-openflowd] command:
+{{{
+ovs-openflowd dp0 tcp:10.0.0.12 --out-of-band --dpid 002320806da5
+}}}