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


Re: [Xen-users] Re: bonding ethernet and xen 3.2.1 or later.

To: Massimiliano De Ruosi <max.deruosi@xxxxxxxx>
Subject: Re: [Xen-users] Re: bonding ethernet and xen 3.2.1 or later.
From: Ferenc Wagner <wferi@xxxxxxx>
Date: Tue, 25 Nov 2008 00:07:16 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Nov 2008 15:08:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081121184547.s5lz7c9sjk4ssc04@xxxxxxxxxxxxxxxx> (Massimiliano De Ruosi's message of "Fri, 21 Nov 2008 18:45:47 +0100")
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20081119102017.pbc7adxr4gsggkog@xxxxxxxxxxxxxxxx> <8763mjncqe.fsf@xxxxxxxxxxxxx> <20081119172511.tud3nqe44kww0ccg@xxxxxxxxxxxxxxxx> <87zljvipb8.fsf@xxxxxxxxxxxxx> <20081121184547.s5lz7c9sjk4ssc04@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
Massimiliano De Ruosi <max.deruosi@xxxxxxxx> writes:

> I'm not using vlans [...] I tried to simply cut off vlan interfaces
> in /etc/network/interfaces, substituting bond0 to vlanX in bridge
> definition, but it didn't work: dom0 could not ping the gateway. I
> suppose a route issue (any idea?).

You aren't supposed to directly use (like assign an IP address to)
interfaces which are bridge ports, like bond0 in your case.  You have
to assign the address to the bridge interface, exactly as you did.

Notice that in my case bond0 was not a port of any bridge.  The
"physical" bridge ports were the VLAN interfaces over bond0.

> This setup is still suboptimal for me: using bond_miimon is ok to
> detect a nic or a cable failure, but it cannot detect the fail of
> active path if the link doesn't go down. Using  bond_arp_ip_target
> (and bond_arp_interval) should be the solution, but it doesn't work in
> this configuration. I Keep work on it.

I never did it myself, but it really should just work.

Xen-users mailing list

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