WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: Bridging on the blink with greater than 2 xen domains

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Bridging on the blink with greater than 2 xen domains
From: NewXenUser <newxenuser@xxxxxxxxx>
Date: Thu, 25 Oct 2007 17:32:46 -0600
Delivery-date: Thu, 25 Oct 2007 16:33:33 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Vl4g7JCUzC8vJa15mlrH0u6+WR6I8K1+234dKldIYWI=; b=oLGegaeC3Gs3b7Hhn4SWLm43i9kJYjmIAUP9xWujSiULgap1yZj2RYzp/wP+finH/mNSD0yA7lnnugm9jcrabCX3K0PrS8ymzZmXjwyhoVRqxAqa9KqaRrl+7YjPbxE5eoNTiFSYRPhxwEOTbFENhSuhjwj5F40jjbzMAdDZY8w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=b3GhAWiADWWza3e/QT0aiOucOJpJdTSnYiDDHb7NiVw6VfPhwbPgmmivAm9/SHnI6CbllYHY1UoyhS/vRl20uhnDSifT1cFUkc8RtYqxs9Bo9TIJeiFDMrbH/q2NyzecwnaQMbAi81lxRdf2Jcrt9qI+ovpc7mQipiv9uKYzdN8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <e564a3bd0710241637g24e8fd3axcd09b2c19509661a@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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <e564a3bd0710241637g24e8fd3axcd09b2c19509661a@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Ok.  I restarted all three domains (mail, wiki, pbx) and for about 15
minutes the bridge networking worked.  Then it dropped back to just
two working.  From the failed domain, I can still ping Dom0, I just
can't ping outside Dom0!

Any suggestions?
Thanks


On 10/24/07, NewXenUser <newxenuser@xxxxxxxxx> wrote:
> Hi,
>
> My bridging stops when I start a third Xen domain !?!?
>
> I have a few domains  setup (mail, wiki, pbx).  If I start two domains
> bridge networking works great.  But if I start a third, either the new
> domains does not work or one of the other DomUs stops working!  By
> stop working I mean I can't route traffic outside of Dom0.  I have
> been looking at this on and off for a couple of weeks.  Any insight or
> things I should look at would be greatly appreciated.
>
> I don't want to bombard this email with 10,000 dumps.  I will gladly
> post any information needed to figure this one out.
>
> Basic network is a 10.20.10.X network.
> Gateway is 10.20.10.1
>
> Xen Dom0 IP is 10.20.10.125
> Xen Mail domain is 10.20.10.150
> Xen PBX domain is 10.20.10.152
> Xen wiki domain is 10.20.10.153
>
> [root@abc ~]# rpm -qa | grep xen
> kernel-xen-2.6.20-2925.13.fc7
> kernel-xen-2.6.20-2936.fc7
> xen-libs-3.1.0-6.fc7
> xen-3.1.0-6.fc7
>
> *************** Below.... 2 work fine *******************
>
> [root@abc ~]# for i in wiki mail; do echo "# $i"; ssh $i arp; ssh $i
> "ping -c 4 4.2.2.2"; done
> # wiki
> Address                  HWtype  HWaddress           Flags Mask            
> Iface
> 10.20.10.125             ether   00:19:B9:D7:FB:4B   C                     
> eth0
> 10.20.10.199             ether   00:07:E9:82:60:33   C                     
> eth0
> PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
> From 10.20.10.125: icmp_seq=1 Redirect Host(New nexthop: 10.20.10.1)
> 64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=37.1 ms
> From 10.20.10.125: icmp_seq=2 Redirect Host(New nexthop: 10.20.10.1)
> 64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=32.3 ms
> 64 bytes from 4.2.2.2: icmp_seq=3 ttl=56 time=30.8 ms
> 64 bytes from 4.2.2.2: icmp_seq=4 ttl=56 time=29.9 ms
>
> --- 4.2.2.2 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3000ms
> rtt min/avg/max/mdev = 29.954/32.570/37.142/2.781 ms
> # mail
> Address                  HWtype  HWaddress           Flags Mask            
> Iface
> 10.20.10.125             ether   00:19:B9:D7:FB:4B   C                     
> eth0
> 10.20.10.1               ether   00:14:1C:5D:B6:BB   C                     
> eth0
> PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
> From 10.20.10.125: icmp_seq=1 Redirect Host(New nexthop: 10.20.10.1)
> 64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=38.1 ms
> 64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=27.1 ms
> 64 bytes from 4.2.2.2: icmp_seq=3 ttl=56 time=31.3 ms
> 64 bytes from 4.2.2.2: icmp_seq=4 ttl=56 time=28.8 ms
>
> --- 4.2.2.2 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3009ms
> rtt min/avg/max/mdev = 27.144/31.359/38.120/4.180 ms
> [root@abc ~]#
>
> ***************** Here we start the third xen domain, "pbx"  ************
>
> [root@abc ~]# xm start pbx
> [root@abc ~]#
>
>
> *****************  Initially WIKI works and PBX does not work *********
> *****************  WAIT 5 MINUTES AND THE PBX WORKS, WIKI DOES NOT *******
>
>
> [root@abc~]# for i in wiki mail pbx; do echo "# $i"; ssh $i arp; ssh
> $i "ping -c 4 4.2.2.2"; done
> # wiki
> Address                  HWtype  HWaddress           Flags Mask            
> Iface
> 10.20.10.125             ether   00:19:B9:D7:FB:4B   C                     
> eth0
> 10.20.10.1               ether   00:14:1C:5D:B6:BB   C                     
> eth0
> PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
>
> --- 4.2.2.2 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3008ms
>
> # mail
> Address                  HWtype  HWaddress           Flags Mask            
> Iface
> 10.20.10.125             ether   00:19:B9:D7:FB:4B   C                     
> eth0
> 10.20.10.1               ether   00:14:1C:5D:B6:BB   C                     
> eth0
> PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
> From 10.20.10.125: icmp_seq=1 Redirect Host(New nexthop: 10.20.10.1)
> 64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=28.8 ms
> 64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=30.3 ms
> 64 bytes from 4.2.2.2: icmp_seq=3 ttl=56 time=26.8 ms
> 64 bytes from 4.2.2.2: icmp_seq=4 ttl=56 time=26.7 ms
>
> --- 4.2.2.2 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 2997ms
> rtt min/avg/max/mdev = 26.794/28.220/30.383/1.513 ms
> # pbx
> Address                  HWtype  HWaddress           Flags Mask            
> Iface
> 10.20.10.1               ether   00:14:1C:5D:B6:BB   C                     
> eth0
> 10.20.10.125             ether   00:19:B9:D7:FB:4B   C                     
> eth0
> PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
> From 10.20.10.125: icmp_seq=1 Redirect Host(New nexthop: 10.20.10.1)
> 64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=29.5 ms
> 64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=27.9 ms
> 64 bytes from 4.2.2.2: icmp_seq=3 ttl=56 time=28.5 ms
> 64 bytes from 4.2.2.2: icmp_seq=4 ttl=56 time=33.1 ms
>
> --- 4.2.2.2 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3002ms
> rtt min/avg/max/mdev = 27.900/29.783/33.102/2.006 ms
> [root@abc123~]#
>
> *********************************************
>
> Thanks
>

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

<Prev in Thread] Current Thread [Next in Thread>