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

Re: [Xen-users] Re: Dom0 network restart required

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Re: Dom0 network restart required
From: Tanuj Bansal <bansal.tanuj83@xxxxxxxxx>
Date: Wed, 16 Dec 2009 03:56:27 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Dec 2009 14:27:09 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=io4hePuSC3iZUalwRT8cRrjc2YUjrgeIdaOZ8A3Yg/c=; b=xwfZNg5CBZFBEmSNdOJh6aFr3xfAJhv1kS1G9e298wcSEJPFQXqVBw/fefgHowy2X6 DgKXy2oNvZBDv6mcEkdo0k8VyPYSHqd5pVfxhdfwJWJnkkykzYypfh7I9axGKARxtgcV 2y6tPtWHW4DebaDS9PoOYBafVVQszezsgyNU0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lu8tukZA6mPh/gW6OaMwFTFTOfFuvZCrS90EGfWHLx4w+CQgY6zhXyY/Dcvw8/zbmu mcuTMbBzT8W+A251yad16ifR17fF2OBH/C3HsKY9bd/uFibkDdHOeN4bf7wRNW+c6K+z BZxI8/V3kY4GLeC718OEnsCUn9oRX8S7LAeVI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0912050421n53922636m869a1be4804fd119@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: <95bff5630912032137sb372b75xeb9223a330f590f1@xxxxxxxxxxxxxx> <95bff5630912032227m46d9086eo67d94c03489a3de1@xxxxxxxxxxxxxx> <95bff5630912042201v461f6611kf8b014ffc26957c7@xxxxxxxxxxxxxx> <7207d96f0912050421n53922636m869a1be4804fd119@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
1. it is using static IP
2. we use routing to reach the server.
3.
 
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0
xenbr1          8000.feffffffffff       no              peth1
                                                        vif0.1
xenbr2          8000.feffffffffff       no              vif4.0
                                                        vif3.0
                                                        peth2
                                                        vif0.2
xenbr3          8000.feffffffffff       no              vif4.1
                                                        vif3.1
                                                        peth3
                                                        vif0.3
xenbr4          8000.feffffffffff       no              peth4
                                                        vif0.4
xenbr5          8000.feffffffffff       no              peth5
                                                        vif0.5
xenbr6          8000.000000000000       no
xenbr7          8000.000000000000       no
xenbr8          8000.000000000000       no
xenbr9          8000.000000000000       no
 
4. yes, dom0 ping the gateway
5. yes, domU ping the gateway
 
My all domU are fine and accessible thoughout.
 
when I use arping -b -I eth0 gateway  on dom0, server became accesible.
 
so where may be issue, network team says no issue there side.

On Sat, Dec 5, 2009 at 5:51 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Sat, Dec 5, 2009 at 1:01 PM, Tanuj Bansal <bansal.tanuj83@xxxxxxxxx> wrote:
> anyone please help here?

You're being to vague, asking for help but not providing any
additional info. Like the simple ones:
- do you use static IP or DHCP
- which networking setup you use, bridged or routing
- what does your bridge setup looks like (output of "brctl show")
- can dom0 ping the gateway
- can domU ping the gateway

etc, etc. ...

However my guess is your switch/router/gateway simply don't cache your
dom0's arp entry. Next time this happens, try using arping from dom0.
So if your dom0 interface is on eth0, and your gateway is 192.168.10.1
(just an example), you can try running (as root)

arping -b -I eth0 192.168.10.1

--
Fajar

>
>
> On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@xxxxxxxxx>
> wrote:
>>
>> I am using Xen on Para virtualization and sometimes my dom0 having network
>> issue while at the same moment I am able to access all DomU from network.
>>
>> to fix the issue I always restart Dom0 Network and it fixes the issue.
>>
>> Can anyone please let me know the cause of this?

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