Hi Ben,
Can ovs-vswitchd talk to a controller though (i'm not seeing how from the
--help)?
I believe that at one point ovs-openflowd was able to fail open when I was
using
openvswitch-1.1.0pre2 ?
Thanks,
Aaron
arosen@rackserver:~$ ovs-vswitchd --help
ovs-vswitchd: Open vSwitch daemon
usage: ovs-vswitchd [OPTIONS] DATABASE
where DATABASE is a socket on which ovsdb-server is listening.
Active DATABASE connection methods:
tcp:IP:PORT PORT at remote IP
unix:FILE Unix domain socket named FILE
Daemon options:
--detach run in background as daemon
--no-chdir do not chdir to '/'
--pidfile[=FILE] create pidfile (default:
/usr/local/var/run/openvswitch/ovs-vswitchd.pid)
--overwrite-pidfile with --pidfile, start even if already running
Logging options:
-v, --verbose=MODULE[:FACILITY[:LEVEL]] set logging levels
-v, --verbose set maximum verbosity level
--log-file[=FILE] enable logging to specified FILE
(default:
/usr/local/var/log/openvswitch/ovs-vswitchd.log)
Other options:
-h, --help display this help message
-V, --version display version information
--check-leaks=FILE log malloc and free calls to FILE
On Mon, Jun 6, 2011 at 3:53 PM, Ben Pfaff <[email protected]> wrote:
> On Mon, Jun 06, 2011 at 03:43:07PM -0400, Aaron Rosen wrote:
> > I would like my openflow switches to fail open but they don't seem to be.
> > When I add --fail=open I see the same behavior. I'm unable to ping into
> my
> > VM's. When I fire up a controller that works as a learning switch I can
> ping
> > my vm's again. Any idea what's going wrong? below is some output from
> > ovs-openflowd.
>
> I don't think ovs-openflowd is going to do this properly. Use
> ovs-vswitchd instead and it should be fine.
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
