[ovs-discuss] Connect switch to controller

Sat Sep 10 17:54:29 UTC 2011

I don't think you are listening.  As I said before, create only one
bridge.

Please don't reply again until you actually try what I suggest.

On Sat, Sep 10, 2011 at 02:20:29PM -0300, Lucas Henrique Mauricio wrote:
> Every bridge that I create and set a controller to it, NOX GUI shows me 1
> node. So, if I create 10 bridges in a single switch and set a controller for
> each of them, NOX is going to show me 10 nodes. But I think that the
> "normal" is to have only one node for each switch instead of a node for each
> bridge in the switch. Am I wrong? Maybe the "problem" is with NOX, not with
> OpenvSwitch..
> 
> 2011/9/10 Ben Pfaff <blp at nicira.com>
> 
> > I really don't understand now.  If you create a single bridge and put
> > both VMs on it, why is there more than one bridge?  And, if you do have
> > more than one bridge, why is it a burden to set the controller for each
> > one?
> >
> > On Sat, Sep 10, 2011 at 02:11:15PM -0300, Lucas Henrique Mauricio wrote:
> > > The hard part is that I don't want to set the controller for every
> > bridge.
> > > Is there a way to tell the controller about the whole switch? That way
> > the
> > > controller would know every flow that passes through a switch without
> > > telling him about every bridge.
> > >
> > > 2011/9/10 Ben Pfaff <blp at nicira.com>
> > >
> > > > Create a single bridge and put both VMs on it.  What's the hard part?
> > > >
> > > > On Sat, Sep 10, 2011 at 02:01:08PM -0300, Lucas Henrique Mauricio
> > wrote:
> > > > > But I'm using the NOX Zaku GUI and when I create a br0 to connect the
> > VM1
> > > > > with the host PC with NOX and a br1 to connect the VM1 with VM2, the
> > GUI
> > > > > shows 2 "switches". That way, for each VM I would have to dots in the
> > NOX
> > > > > GUI. Besides this, it doesn't show a link connecting the two VMs...
> > Do I
> > > > > need these two bridges?
> > > > >
> > > > > Can I set a bridge to connect the two VMs (like br1) and use it
> > without
> > > > > setting a controller for it? I think it doesn't work..
> > > > >
> > > > > Best regards
> > > > >
> > > > > 2011/9/10 Ben Pfaff <blp at nicira.com>
> > > > >
> > > > > > 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 <blp at nicira.com>
> > > > > > >
> > > > > > > > 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 <blp at nicira.com>:
> > > > > > > > > > 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
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Lucas Henrique Mauricio
> > > > >
> > > > > 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
> >
> 
> 
> 
> -- 
> Lucas Henrique Mauricio
> 
> Universidade Federal do Rio de Janeiro
> Escola Polit?cnica
> Engenharia Eletr?nica e de Computa??o