|
|
|
|
|
|
|
|
|
|
xen-api
[Xen-API] Re: mgmt socket for xapiX bridges
George Shuklin <george.shuklin-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
writes:
> 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-
bers.
--
Ben Pfaff
http://benpfaff.org
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
|
|
|
|