Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead

[Florian Engelmann <mailinglist@xxxxxxxx>]

> > Hi,
> > I just installed a clean debian etch 4.0r1 with LVM on our 
> > Dell PowerEdge 2900. The system has 2 Broadcom onboard NICs 
> > and I also installed 2 Intel Pro 1000 NICs. I installed all 
> > needed pakages and also dev86.
> >     
> [...]
>   
> > The kernel booted also without any errors an i got my login 
> > prompt. I tried to login with ssh from my workstation but 
> > that did not work. So i tried to ping my Server what also 
> > failed. An ifconfig gives me an eth0 device with my local IP 
> > 192.168.1.6 a lo device a peth0 device a vif0.0 device and a 
> > xenbr0 device without any IP. I did not modify the 
> > /etc/xen/xend-config.sxp and my /etc/network/interfaces looks 
> > like this:
> > iface eth0 inet static
> >         address 192.168.1.7
> >         netmask 255.255.255.0
> >         #network 192.168.1.0
> >         #broadcast 192.168.1.255
> >         gateway 192.168.1.201
> >         # dns-* options are implemented by the resolvconf 
> > package, if installed
> >         #dns-nameservers 192.168.1.210
> >         #dns-search manntech.local
> >
> > auto eth3
> > iface eth3 inet static
> >         address 192.168.99.7
> >         netmask 255.255.255.0
> >         network 192.168.99.0
> >         broadcast 192.168.99.255
> >
> >
> >     
> Did you try to run any tracing tools (like Ethereal) to see if you
> receive packets on any interfaces? Also, does "brctl show" display all
> interfaces properly connected to the bridge? Does your routing table (ip
> r) show correct entries?
>   
I tried tcpdump and there was no single incoming packet when i tried to 
ping 192.168.1.6 (1st cluster node).
brctl show gives me:
xen1:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                       peth0

route:
xen1:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
localnet        *               255.255.255.0   U     0      0        0 eth0
192.168.99.0    *               255.255.255.0   U     0      0        0 eth3
default         192.168.1.201 0.0.0.0         UG    0      0        0 eth0

ifconfig:
xen1:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:19:B9:D8:F4:88
         inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::219:b9ff:fed8:f488/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:18994 errors:0 dropped:0 overruns:0 frame:0
         TX packets:7129 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:17246682 (16.4 MiB)  TX bytes:618804 (604.3 KiB)
         Interrupt:16 Memory:f4000000-f4011100

eth3      Link encap:Ethernet  HWaddr 00:1B:21:07:6A:C7
         inet addr:192.168.99.6  Bcast:192.168.99.255  Mask:255.255.255.0
         inet6 addr: fe80::21b:21ff:fe07:6ac7/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3614 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3573 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:750819 (733.2 KiB)  TX bytes:739891 (722.5 KiB)
         Base address:0xecc0 Memory:f3ee0000-f3f00000

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:31 errors:0 dropped:0 overruns:0 frame:0
         TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:3172 (3.0 KiB)  TX bytes:3172 (3.0 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 NOARP  MTU:1500  Metric:1
         RX packets:9880 errors:0 dropped:0 overruns:0 frame:0
         TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1483035 (1.4 MiB)  TX bytes:3254 (3.1 KiB)
         Interrupt:16 Memory:f8000000-f8011100

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:48 errors:0 dropped:0 overruns:0 frame:0
         TX packets:8609 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:2296 (2.2 KiB)  TX bytes:1365379 (1.3 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:8627 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1245441 (1.1 MiB)  TX bytes:90 (90.0 b)

iptables -L
xen1:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


I also changed my network setup to be sure no other problems are causing 
this error. I connected the 2 nodes to their own switch.
At the moment I connected eth0 and eth1 (Broadcom) to the switch, eth3 
ist a crossover connection (gigabit) and eth2 has no cable connected.
A ping 192.168.1.7 (2nd node) gives me "Destination Host Unreachable"
>  
>   
> > While eth0 is my default LAN interface and eth3 is my 
> > crossover interface to the 2nd clusternode. If I change
> > (network-script network-bridge)
> > to
> > (network-script 'network-bridge netdev=eth1')
> >
> > my eth0 works fine but any DomU I start does not get any 
> > network connection.
> >     
> Do you have both eth0 and eth1 configured and active with static IP
> addresses? How does your ifconfig output look like when you run a DomU?
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
>   

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users