This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Re: mgmt socket for xapiX bridges

To: George Shuklin <public-george.shuklin-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxx>
Subject: [Xen-API] Re: mgmt socket for xapiX bridges
From: blp@xxxxxxxxxxxxxxx (Ben Pfaff)
Date: Tue, 20 Sep 2011 11:50:26 -0700
Cc: public-xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@xxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Sep 2011 20:21:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1316511347.1929.2.camel@X220> (George Shuklin's message of "Tue, 20 Sep 2011 13:35:47 +0400")
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <1316511347.1929.2.camel@X220>
Reply-to: blp@xxxxxxxxxxxxxxx
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

George Shuklin <george.shuklin-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>

> Found that xapiX (xapi0, xapi1, etc bridges have no management socket
> in /var/run/openvswitch), so ovs-ofctl reject to do dump-flows (and
> other) commands.

Those bridges are "VLAN bridges" actually part of larger bridges.
You can use ovs-dpctl to find the name of the top-level bridge.

The ovs-vsctl manpage explains further:

Linux VLAN Bridging Compatibility
    The ovs-vsctl program supports the model of  a  bridge  implemented  by
    Open  vSwitch,  in  which  a  single  bridge supports ports on multiple
    VLANs.  In this model, each port on a bridge is  either  a  trunk  port
    that  potentially passes packets tagged with 802.1Q headers that desig-
    nate VLANs or it is assigned a  single  implicit  VLAN  that  is  never
    tagged with an 802.1Q header.

    For   compatibility  with  software  designed  for  the  Linux  bridge,
    ovs-vsctl also supports a model in  which  traffic  associated  with  a
    given 802.1Q VLAN is segregated into a separate bridge.  A special form
    of the add-br command (see below) creates a ``fake bridge''  within  an
    Open  vSwitch  bridge  to  simulate  this behavior.  When such a ``fake
    bridge'' is active, ovs-vsctl will treat it much like a bridge separate
    from  its  ``parent  bridge,''  but  the  actual implementation in Open
    vSwitch uses only a single  bridge,  with  ports  on  the  fake  bridge
    assigned  the  implicit  VLAN of the fake bridge of which they are mem-

Ben Pfaff 

xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>