There is no need to use ovs-dpctl with ovs-vswitchd. ovs-vswitchd manages the datapath itself. You can manage a bridge, and create and destroy bridges, with ovs-vsctl alone.
On Sat, Sep 10, 2011 at 01:43:56PM -0300, Lucas Henrique Mauricio wrote: > Ok, I see. But if I have 2 VMs and I want them to connect to each other > directly? I need to create a bridge with ovs-vsctl and use the > set-controller? Or I can use a datapath with ovs-dpctl? > > Using a bridge and setting the controller on each VM I could ping, but using > a datapath I couldn't. > > In previous versions of openvswitch I used to create a datapath an the its > controller with ovs-openflowd. Now I don't know how to do this. If a use > ovs-vsctl set-controller with a datapath (DP), the command returns "no > bridged named dp0" > > Thanks in advance. > > 2011/9/8 Ben Pfaff <[email protected]> > > > With ovs-vswitchd, starting the switch daemon and configuring the > > switch are two different steps. Once you've started the switch, the > > "ovs-vsctl set-controller" command configures the controller. > > > > If you have multiple bridges (datapaths) and you want all of them to > > connect to a controller, then yes you do need to configure each of > > them separately to connect to that controller using a similar command. > > > > On Thu, Sep 08, 2011 at 04:56:13PM -0300, Lucas Henrique Mauricio wrote: > > > So the command that substitutes ovs-openflowd <dp> tcp:<ip>:<port> is > > > ovs-vsctl set-controller br0 tcp:<ip of controller>:<port>? > > > > > > Another question, I used to tell every dp to the controller.. Is it > > > still necessary? Do I use the same command you told me? > > > > > > Best regards, > > > > > > 2011/9/8 Ben Pfaff <[email protected]>: > > > > On Thu, Sep 08, 2011 at 04:26:27PM -0300, Lucas Henrique Mauricio > > wrote: > > > >> I have the NOX (Zaku) controller installed in my host and an > > > >> openvswitch (v1.2.1) running as openflow switch in a virtual machine > > > >> created with VirtualBox. The virtual machine has an interface (eth1) > > > >> connected to the host. Before setting datapaths, the vm can reach the > > > >> host, but when I set a datapath, the vm can't. When I used openvswitch > > > >> (v1.1.0) and NOX (v0.5) in the same machine, I just had to do > > > >> ovs-openflowd dp# tcp:<ip of controller>:<port> to connect the switch > > > >> to the controller. > > > >> > > > >> What can I do to solve this? I don't even know the command that > > > >> substitutes ovs-openflowd in the openvswitch v1.2.1.. =( Is it > > > >> ovs-ofctl? How can I use it? > > > > > > > > Please set up OVS according to INSTALL.Linux. ?After that, to > > > > configure a controller on br0: > > > > ? ? ? ?ovs-vsctl set-controller br0 tcp:<ip of controller>:<port> > > > > > > > > > > > > > > > > -- > > > Lucas Henrique Mauricio > > > > > > Brasil > > > Universidade Federal do Rio de Janeiro > > > Escola Polit?cnica > > > Engenharia Eletr?nica e de Computa??o > > > > > > -- > Lucas Henrique Mauricio > > Universidade Federal do Rio de Janeiro > Escola Polit?cnica > Engenharia Eletr?nica e de Computa??o _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
