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] Problem pinging the xen guest after live migration

To: John Haxby <john.haxby@xxxxxxxxxx>
Subject: Re: [Xen-users] Problem pinging the xen guest after live migration
From: Srija G <srijavg@xxxxxxxxx>
Date: Wed, 7 Jul 2010 11:27:23 -0400
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 07 Jul 2010 08:28:44 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ggAiYxERj8uNLpY/M/vMlJQwXVl2KL3xaLJj9VXGVkc=; b=pXuR3cij/wHzxxySezdI1PS2w7nCiUqgEx+cls0eqEHyGf2nzLyA3LISxoyxVDw5E8 NhJP82eG91rcdPVncpGuAnWa7yUnO5VctRHGemlvPgVaQOVYougBipDxcGpbF97dfrO0 v9Nlo/Hv+WMwdZTtvoQGCrzCcRwmz7M9ejJpc=
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=QE89zXcalinJMSy4WgfXoYZTNkA9wF7mBOx5jOsfcTZhQBzWdogqemVmTXAgJU4lGK XlJR+eVmAos62aGKm54ZapdSnRnhmZjVz1IJyp8sa9PH/QgpVhzlskz7oZYxcV+rLrbX V8dLA2qoS0VmH4non0Rl7KmYxGASynYVtb/rQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C31B310.9030100@xxxxxxxxxx>
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: <AANLkTimKdDBpx_PfzvKjFpN51SE1yw3J0Fk9_gGbGPP7@xxxxxxxxxxxxxx> <5DB0519124BB3D4DBEEB14426D4AC7EA17E925E92F@xxxxxxxxxxxxxxxxxxxxx> <4C31B310.9030100@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thank you so much  to both of you John and Matej.
 
Yes,  both of your  solution,  worked when I am live migrating the guest  from one  dom0 to  another dom0.
 
What i am doing now, 
 
  -    In Host-B  , I am executing the command , 
   
                 ping  Guest-15a
 
   -   In the Host-A   ,  I am executing  the command
 
          xm  migrate --live  Guest-15a    Host-B
 
 The  result:
 
        Live  migration went  very  well,  found  there is  just  1 sec stop in between but I think that is  acceptable.
 
Our network team says  that portfast is already configured at switch .
 
But as  the first option  worked , so  I  hope  I can move on  - right?  If not please  advice....
 
My second question is,  mode=4  , ie  802.2ad ( link  aggregation ) did not work still yet. I wanted to
set  the mode=4 as it is much faster. Found one document  , here is the url
 
 
It is very good .  In this  document  , the first line it is mentioned   :
 
*****   It is important that the native VLANs be identical on both sides of the link
 
What does it mean  VLANs be identical on both sides of the link  ? Sorry for the silly question though.
 
 Would you please explain , do I need to check /configure anything  on the server side?     My configuration is  simple  enough , 
 
In my configuration I have used  eth0 and  eth1 bonded  to bond0, and  for each subnet,  created  the
 
config files,  as   ifcfg-bond0.15, ifcfg-bond0.16,  ifcfg-bond0.17.   Then in the /etc/xen/scripts  , I have created
 
a custom  file where I mentioned all the bridges  for  each  vlan tag.  And this custom file is being called
 
from    /etc/xen/xend-config.sxp...
 
 
Please  advice,  do you need to proceed with aggregation link or  with mode=1, which is now configured  and
you all helped me a work around...
 
Thanks again.
 


 
On Mon, Jul 5, 2010 at 6:25 AM, John Haxby <john.haxby@xxxxxxxxxx> wrote:

On Sat, 2010-07-03 at 17:57 -0400, Srija G wrote:
Hi ,
[snip]

Can anyone please advice , where to check?  Do you think it is the switch configuration issues?

 

It's almost certainly a switch issue: the switch doesn't know that the MAC address for the recently migrated machine is on a different port.

There are two possibilities: you can either ping something (eg the default router) _from_ the guest after it has migrated or you can set portfast on the switch.  The former just informs the switch that the originating MAC address is now on a different port; the latter makes the switch less willing to hold on to the MAC address/port association for a long time and is something that the network people can do.  You might want to try doing both.

jch



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