| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Bonding Issue with Dom0
On 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
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
Can you show the output of brctl show? You must be using xen 3.1 or older by the way the network is looking.
Also can you show the contents of /proc/net/bonding/bond0
Grant McWilliams
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home