[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Network Problem after DomU migration

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: shreyas pandya <pandyashreyas1@xxxxxxxxx>
  • Date: Wed, 01 Jun 2011 15:09:31 +0530
  • Delivery-date: Wed, 01 Jun 2011 02:41:46 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=MejaFSY5iH4crWVA1u4tlkxX72DpYK8D+PziL7AskGbEVZUoM3/U1yNyboRpWftlWa MV6nrRfhN/QMfbubSwpBMvpDz7CP5xICCXjGSCtslNQTo6jcZxF/jDfEIS/ini+eoxJV mlFp7Jg2PU9C4gcfrDTgtmLXYfyRZdfscqlZA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Tuesday 31 May 2011 08:13 PM, Simon Hobson wrote:
ml ml wrote:

i have two nodes on two switches. When i do a live migration then my
DomU is not reachable anymore.
If i start a ping manually from the DomU console, then its reachable
again. Looks like i need to create traffic so that the Dom0 Network
Stack knows that there is now a DomU running :)

By "reachable" i mean icmp pings to that IP Address.

More likely it's a MAC table caching issue. Each switch (and that includes the virtual switch (bridge) in your Dom0) caches the MAC-port mappings required to forward packets. When you move a device, then the table need to update.

Generating traffic from the DomU will generally cause the switches to update their tables - though some seem to take longer than others, I've seen HP switches take 5 minutes to expire the old mappings.
why are you using two switches?should not one switch suffice for two nodes?
i guess if you use one switch instead of two then the information about migrated vm will propagate to switches quickly

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.