By default, OpenFlow runs on port 6633 and OVSDB runs on port 6634. ovs-ofctl uses the OpenFlow protocol, so I'd expect it to use port 6633. What happens if you run ovs-ofctl either without the port specified or using port 6633?
--Justin On Jan 9, 2014, at 10:06 AM, Alex Nelson <[email protected]> wrote: > I run it with the -vvconn option but I don't get much info: > > ovs-ofctl -vvconn dump-aggregate tcp:10.1.5.3:6634 > 2014-01-09T17:54:02Z|00001|vconn|DBG|tcp:10.1.5.3:6634: sent (Success): > OFPT_HELLO (xid=0x1): > ovs-ofctl: connecting to tcp:10.1.5.3:6634 (Connection reset by peer) > > It seems it works fine from the client's side. Do I have to setup the DB at > the OVS in any special way in order to have remote access through a socket? > > I have tried many different ways I found online including the following: > > ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock \ > --remote=db:Open_vSwitch,manager_options \ > --remote=tcp:10.1.5.3:6634 > --pidfile --detach > but nothing... > > > On Thursday, January 9, 2014 8:59 AM, Justin Pettit <[email protected]> > wrote: > > On Jan 9, 2014, at 5:02 AM, Alex Nelson <[email protected]> wrote: > >> I'm trying to get aggregated stats about the installed flows of an OVS. >> >> I'm running: ovs-ofctl dump-aggregate tcp:10.1.5.3:6634 in one machine, >> >> and I get: ovs-ofctl: connecting to tcp:10.1.5.3:6634 (Connection reset by >> peer) > > > By default, OpenFlow runs on port 6633. I'd double-check your port numbers. > If that doesn't work, then try Ben's "-vvconn" suggestion. > > --Justin > > > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
