<div>Hey Felix,</div><div><br></div><div>Unfortunately, basically no it seems... XenServer manages interfaces as bridges by default, and this setup is the one recommended by Linbit.</div><div><br></div><div>That said, right certainly the alternative would be to just setup the interface manually on the dom0 which would avoid the whole issue to begin with, and admit, might be a better solution over-all. Just till now I've been sticking with the official instructions as much as I could and trying to avoid under the covers changes to XS when possible.</div>
<div><br></div><div>Something like what this guy did to setup the interface:</div><div><a href="http://www.reidmartin.ca/tech-corner/xenserver-dedicated-interfaces/">http://www.reidmartin.ca/tech-corner/xenserver-dedicated-interfaces/</a></div>
<div><br></div><div>Definitely a better solution if someone wants to keep OVS as well.</div><div><br></div><div>Cheers,</div><div>Andrew</div><div><br></div><br><div class="gmail_quote">On Sun, Oct 7, 2012 at 1:08 PM, Felix Frank <span dir="ltr"><<a href="mailto:ff@mpexnet.de" target="_blank">ff@mpexnet.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<div><br>
<br>
On 10/07/2012 05:46 PM, Andrew Eross wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I can change from open vswitch to normal linux bridging with<br>
"xe-switch-network-backend bridge" on XenServer, so what the heck let's<br>
see if that does some magic here.<br>
</blockquote>
<br></div>
meh, that seems a little exaggerated to me.<br>
<br>
Doesn't Xenserver allow you to un-bridge eth1 for good? I assume it's a dedicated DRBD NIC, so there is no point in adding it to *any* bridge, vanilla or ovs. (I went on a limb here of course - I just assume that eth1 is the one device in xenbr1.)<br>
<br>
Glad that worked for you, though.<br>
<br>
Cheers,<br>
Felix<br>
</blockquote></div><br>