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/
Home Products Support Community News


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 18:28:32 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 16 Dec 2009 04:59:27 -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=G/meT6hEVFQJpNbrTSgQmNDy4M8ueVOYmqEGN2Iz5+Q=; b=j7gS+Z/XOpNFSdSKwL8vHa07Pm+Ts6pfOTLj1zMBtOWjmfMpcT4FaKx60Cq04pXhdg 9J9hwAjs6VVnVM9HxgiiNIgimfuW14sigxRCbLyikIzuwT3pao5hW98S16TCGzCWKTkW tgTV2zLTsCBSUcmmUmbz9G3FTOb7VZG4mdIyI=
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=X3JRemAIsc5xT4qXgVAgC+zPhBK1aUCCojk39kH67YuUsDoe4FXwBArDAwG+zotHcY RqUTzqc5JjahkjOcCgzWYKHfnsRkcfAHemJrN5EIs9qnJX6L02SLMSE8aLzY/5tuapbD +02T7oejtho46HKX5rV8WUbKbZvcaiWHVtn5k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0912151939i281d8c31u27221fb91c519a9b@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> <95bff5630912151426i28bab378ved6981a303161afc@xxxxxxxxxxxxxx> <7207d96f0912151939i281d8c31u27221fb91c519a9b@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Yes, we are using bridges in dom0 for setup domU but routing on network side to reach my dom0 from outside.

btw thanks for the suggestion, your solution really works.

On Wed, Dec 16, 2009 at 9:09 AM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Wed, Dec 16, 2009 at 5:26 AM, Tanuj Bansal <bansal.tanuj83@xxxxxxxxx> wrote:
> 1. it is using static IP
> 2. we use routing to reach the server.

> xenbr3          8000.feffffffffff       no              vif4.1
>                                                         vif3.1
>                                                         peth3
>                                                         vif0.3

Do you know the difference between routing and bridged setup? From
that output it looks like you're using bridged setup.

> when I use arping -b -I eth0 gateway  on dom0, server became accesible.

Then it's just like I said:
>> However my guess is your switch/router/gateway simply don't cache your
>> dom0's arp entry.

> so where may be issue, network team says no issue there side.

When it comes to arp issue, they usually say that :D
Some alternatives:
- try to find out why your gateway/switches can't find your dom0 arp
entry. This can be ... complicated.
- put static arp entry on your gateway. This works, but not really
recommended, plus your network guys may not allow such setup
- setup dom0 to periodically send outgoing packets. A simple ping to
gateway in crontab should be enough. This will ensure that network
devices will keep up to date entry of dom0's MAC address.


Xen-users mailing list