[Xen-users] Xen 3.2 and bridged network problem

["--[ UxBoD ]--" <uxbod@xxxxxxxxxxxx>]

Hi,

Having a bit of a strange problem in that I have three domains running and 
frequently their IP addresses no longer respond to a ping.  If I try and ping 
from Dom0 all is good, but it is when I try from another workstation on the 
LAN.  Here is my setup :-

[root@xen ~]# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   512     1     r-----    295.2
asterisk                                     4  1024     1     -b----     15.1
mailscanner                                  5  1536     1     -b----    140.9
zimbra                                       6  2048     1     r-----    156.8

[root@xen ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.001b2fc9d99e       no              vif6.0
                                                        vif5.0
                                                        vif4.0
                                                        peth0
virbr0          8000.000000000000       no


[root@xen ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1B:2F:C9:D9:9E  
          inet addr:192.168.1.99  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:2fff:fec9:d99e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9530 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8417 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1019720 (995.8 KiB)  TX bytes:1994541 (1.9 MiB)

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

peth0     Link encap:Ethernet  HWaddr 00:1B:2F:C9:D9:9E  
          inet6 addr: fe80::21b:2fff:fec9:d99e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22262 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23000 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4388537 (4.1 MiB)  TX bytes:7769470 (7.4 MiB)
          Interrupt:19 Base address:0xac00 

vif4.0    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:169 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1390 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:38248 (37.3 KiB)  TX bytes:275159 (268.7 KiB)

vif5.0    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:3636 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3699 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:589378 (575.5 KiB)  TX bytes:1481190 (1.4 MiB)

vif6.0    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:662 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1406 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:484182 (472.8 KiB)  TX bytes:354572 (346.2 KiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:7332 (7.1 KiB)

[root@xen ~]# grep vif /etc/xen/zimbra 
vif = [ 'mac=00:16:3e:c6:e3:47,ip=192.168.1.100' ]
[root@xen ~]# grep vif /etc/xen/mailscanner 
vif=['mac=00:16:3e:e5:bd:92,ip=192.168.1.101']
[root@xen ~]# grep vif /etc/xen/asterisk
vif=['mac=00:16:3e:e2:5d:c0,ip=192.168.1.102']

The MAC addresses match to what is defined in 
/etc/sysconfig/networking/devices/ifcfg-eth0, and if run a arp -a from my 
workstation I can see them just fine.  Arping also works without a problem.  
Yet if I try ping'ing them all, perhaps two will respond but not the other one. 
 If I connect to the domain and restart its virtual NIC it then starts to reply 
to pings, but then one of the others fails.

Has anybody else seen this at all ?

Regards,

-- 
--[ UxBoD ]--
// PGP Key: "curl -s http://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: F57A 0CBD DD19 79E9 1FCC A612 CB36 D89D 2C5A 3A84
// Keyserver: www.keyserver.net Key-ID: 0x2C5A3A84
// Phone: +44 845 869 2749 SIP Phone: uxbod@xxxxxxxxxxxxxxxx

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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