Hi, ah, ok, thanks for your help! That piece of information wasn't obvious to me from reading through INSTALL.Openflow.
I think it might be useful to add a setence explicitely stating that ovs-vswitchd and ovs-openflowd are mutually exclusive to INSTALL.Openflow (or even add a mutex of some sort to inhibit both daemons from running at the same time?) Thanks and see you tomorrow, Andi Justin Pettit schrieb: > On Oct 19, 2009, at 6:22 PM, Andreas Wundsam wrote: > >> - I am running vswitchd, brcompatd, and openflowd with following >> configuration: >> /usr/local/sbin/ovs-vswitchd --pidfile --detach -vANY:syslog:EMER >> /etc/ovs-vswitchd.conf >> /usr/local/sbin/ovs-brcompatd --pidfile --detach -vANY:syslog:EMER >> /etc/ovs-vswitchd.conf >> ovs-openflowd --out-of-band --datapath-id 000000000003 --fail=closed dp4 >> --listen=ptcp: tcp:172.16.0.10 > > > Ah, ovs-openflowd and ovs-vswitchd are not meant to be run together. > ovs-openflowd is meant to be used as a drop-in replacement for the > OpenFlow reference implementation. It provides the same functionality > as the ofprotocol daemon (originally called secchan). > > ovs-vswitchd is meant to be a more full-featured software-based switch > that can be remotely managed by an OpenFlow controller. To have > ovs-vswitchd connect to an OpenFlow controller, look at the > "mgmt.controller" or "bridge.<bridge_name>.controller" keys in the > ovs-vswitchd.conf man page. If you don't need OpenFlow reference code > compatibility (and I don't imagine you do), I'd recommend using > ovs-vswitchd. > > --Justin > > -- Andreas Wundsam Technische Universität Berlin, Deutsche Telekom Laboratories FG INET, Research Group Anja Feldmann address: Sekr. TEL 16, FG INET, Ernst-Reuter-Platz 7, 10587 Berlin e-mail: [email protected] web: http://www.net.t-labs.tu-berlin.de/people/andi.shtml _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
