| To: | "Andrew Deagman" <andrew.deagman@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-users] Bonding Issue with Dom0 |
| From: | "Grant McWilliams" <grantmasterflash@xxxxxxxxx> |
| Date: | 2008年12月22日 10:47:56 -0800 |
| Cc: | xen-users@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | 2008年12月22日 10:48:39 -0800 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=r/WJC5cQZdsaQ30wnkFtzqQgzErCh6ha2A882EFWCK0=; b=PFShYCUP9J7G6QWsFD32+x1dZBFfDXb7pdiqyCd+XFS5TNl6jBcA1m4B3QMIRA3Vls HopWKOdXA7VVpgumiWOoVliv8xqsHPDTZgQwgOOu7x9lAcvIwSf3w1tCTTwa9Pl9d+Vu 5eAe0u128xQrMdcF77SA2HGH3wLO+NcDCFA1c= |
| 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=EMo8rrXHIGFCskBRJ7RInqb+rw9O1PfpEmTgz/AvR1wLzeQW2Lc8dnIOx7mbAi6QV6 q6C8APY57pyG6JRN2Y5IQPm9QxzSSf9LqKEBWrUvSwO6Ggc93dwXDtCkRkiHlY6e6KiH iEOeDp5Z4qN1T8UGiUmvKZY/a0y/QPL6QfZjc= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <C57531BF.B1C%andrew.deagman@xxxxxxxxxxxxxx> |
| 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: | <ed123fa30812220852n6f383a68je093eef8fd6f3f73@xxxxxxxxxxxxxx> <C57531BF.B1C%andrew.deagman@xxxxxxxxxxxxxx> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
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
eth1 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1
inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link
UP BROADCAST RUNNING SLAVE 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:1000
RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:73 errors:0 dropped:0 overruns:0 frame:0
TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20915 (20.4 KiB) TX bytes:20915 (20.4 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4572 (4.4 KiB) TX bytes:0 (0.0 b)
veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
badm01::#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
--
Andrew Deagman
System Administrator | Callfinity Inc.
E: andrew.deagman@xxxxxxxxxxxxxx
O: 585-278-1940 x8126
M: 585-703-8621
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-users] 10Gbit ethernet NIC gives slow throughput , Pasi Kärkkäinen |
|---|---|
| Next by Date: | Re: [Xen-users] Bonding Issue with Dom0 , Andrew Deagman |
| Previous by Thread: | Re: [Xen-users] Bonding Issue with Dom0 , Grant McWilliams |
| Next by Thread: | Re: [Xen-users] Bonding Issue with Dom0 , Andrew Deagman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |