[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Bonding Issue with Dom0
- To: "Andrew Deagman" <andrew.deagman@xxxxxxxxxxxxxx>
- From: "Grant McWilliams" <grantmasterflash@xxxxxxxxx>
- Date: Mon, 22 Dec 2008 11:21:40 -0800
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 22 Dec 2008 11:22:22 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=mkFH7y9E+JKl5WfkX7yLz5kA2pW+7TFudw9clNI7cCj5CcMKioMpeeF3ZM13TIZEnG Y2bIcmv/q1JpLWlk33x4s0gzkmI8fiK8Evsmwu5IeaZtB2w96tmOdG00kPp+/3/oFvM+ xCBN2lAkiz5AmUIrk21KSbBHF5kvjV8fysk34=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
On Mon, Dec 22, 2008 at 10:53 AM, Andrew Deagman <andrew.deagman@xxxxxxxxxxxxxx> wrote:
I got it working. It was an issue with eth0 being moving out of the way and bonding was not truly working. I added a custom network-bridge script and attached my DomU to a new bridge and every thing is now working. Thanks for the help.
AndrewOn Mon, Dec 22, 2008 at 8:59 AM, Andrew Deagman <andrew.deagman@xxxxxxxxxxxxxx> wrote:
From what I can tell the bond is still working. I can get to the physical server (Dom0). When I login to DomU from the console I can not ping the gateway or get in/out. Here is the output of ifconfig âa
[adeagman@bns1 ~]$ badm01::# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1
inet addr:10.10.8.11 Bcast:10.10.8.255 Mask:255.255.255.0
inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:5385 errors:0 dropped:0 overruns:0 frame:0
TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB)
eth0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
Xen renames eth0 to peth0 and creates a bridge named eth0. Are you sure that your bond is working after xend starts up? Generally you have to rename the actual physical device eth0 or use custom network-scripts to keep this from happ
Quietly implementing RFC 1925 wherever I go....
Thats where I was headed. Glad you got it to work. I use Xen with bonded ethernet devices so I had to do the same thing.
Grant McWilliams
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|