It's still not working ... :/ After typing ovs-vstl --db=tcp:10.0.0.2:6633 at controller, I get:
[root@localhost Desktop]# ovs-vsctl --db=tcp:10.0.0.2:6633 show 2014-04-02T07:41:40Z|00001|reconnect|WARN|tcp:10.0.0.2:6633: connection attempt failed (No route to host) ovs-vsctl: tcp:10.0.0.2:6633: database connection failed () And like I said ping from controller (10.0.0.1) to switch (10.0.0.2) works... On switch I used: ovs-vsctl set-manager ptcp:6633:10.0.0.2 Log files seems ok: Controller: 2014-04-02T07:34:42Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovsdb-server.log 2014-04-02T07:34:42Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 1.10.0 2014-04-02T07:34:52Z|00003|memory|INFO|1916 kB peak resident set size after 10.0 seconds 2014-04-02T07:34:52Z|00004|memory|INFO|cells:30 monitors:1 sessions:1 Switch: 2014-04-02T07:38:27Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovsdb-server.log 2014-04-02T07:38:27Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 1.10.0 2014-04-02T07:38:37Z|00003|memory|INFO|1684 kB peak resident set size after 10.0 seconds 2014-04-02T07:38:37Z|00004|memory|INFO|cells:136 monitors:1 sessions:1 (Clock isn't set properly on switch, that's why time is different here) Do you have any further instructions for me? Thank you for your help! 2014-04-01 18:33 GMT+02:00 Ben Pfaff <b...@nicira.com>: > On Tue, Apr 01, 2014 at 06:31:01PM +0200, Slavica Tomovic wrote: >> I fixed that syntax mistake, it doesn't work again. I on the OVS >> switch that I want to configure I used: >> >> ovs-vsctl set-manager ptcp:3333:10.0.0.2 >> >> and on the controller: >> >> ovs-vsctl --db=tcp:3333:10.0.0.2 > > You got the order wrong again, this time for the tcp: one. ptcp: and > tcp: use different orders. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
