From: Jason Luan <luanjianhai@163•com>
To: Ian Campbell <Ian.Campbell@citrix•com>
Cc: netdev@vger•kernel.org, xen-devel@lists•xensource.com,
konrad.wilk@oracle•com
Subject: Re: xen-netback notify DomU to send ARP.
Date: Wed, 09 Jan 2013 09:07:16 +0800 [thread overview]
Message-ID: <50ECC2C4.5060501@163.com> (raw)
In-Reply-To: <1357660834.12649.103.camel@dagon.hellion.org.uk>
于 2013年01月09日 00:00, Ian Campbell 写道:
> On Tue, 2013-01-08 at 15:40 +0000, jianhai luan wrote:
>> On 2013-1-8 21:42, Ian Campbell wrote:
>>> On Tue, 2013-01-08 at 13:13 +0000, Jan Beulich wrote:
>>>>>>> On 08.01.13 at 12:57, jianhai luan <jianhai.luan@oracle•com>
>>>>>>> wrote:
>>>>> When Xen Dom0's network circumstance changed, DomU
>>>>> should be notified in some special condition. For
>>>>> example the below circumstance:
>>>>> ping from Guest A to DomU:
>>>>> Guest A --> eth0 - bond0 - xenbr0 --VIF(DOMU)
>>>>> eth1 /
>>>>> when eth0 inactive, and eth1 active.
>>> How is eth0 failing? Are you unplugging it, un-enslaving it or
>>> taking
>>> some other sort of administrative action?
>> In my emulation environment, i unplug it or ifdown the interface,
> I expect these would behave rather different, since the affect of ifdown
> looks rather different to an unplug from the PoV of the switch.
>
> Is the ifdown case something which you are trying to solve or just what
> appeared to be a convenient test case? I'd be less inclined to worry
> about explict admin actions such as that.
>
> Unplugging the cable should cause:
>
I do above listed thing to let switch active slave only.
I think that we should put attention on the thing which bond switch
active slave interface in active-backup mode. In network circumstance,
many thing will cause the switch, what do Vif when the event happen?
>>> Doesn't this state change cause the switch to which eth0 and eth1
>>> are
>>> attached to forget the MAC tables associated with the eth0 port,
>>> meaning
>>> that subsequent traffic will be flooded until it learns that eth1 is
>>> the
>>> new port?
> Ian
>
>
>
> _______________________________________________
> Xen-devel mailing list
Thanks,
Jason
> Xen-devel@lists•xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists•xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-09 1:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 11:57 xen-netback notify DomU to send ARP jianhai luan
2013-01-08 13:13 ` [Xen-devel] " Jan Beulich
2013-01-08 13:42 ` Ian Campbell
2013-01-08 15:40 ` jianhai luan
2013-01-08 16:00 ` [Xen-devel] " Ian Campbell
2013-01-09 1:07 ` Jason Luan [this message]
2013-01-09 12:03 ` Ian Campbell
2013-01-09 7:39 ` jianhai luan
2013-01-09 10:06 ` Jan Beulich
2013-01-09 12:28 ` jianhai luan
2013-01-09 13:44 ` Jan Beulich
2013-01-09 15:37 ` Jason Luan
2013-01-09 15:44 ` [Xen-devel] " Jan Beulich
[not found] ` <50ED950A.6010203@163.com>
[not found] ` <50EDA80002000078000B427B@nat28.tlf.novell.com>
[not found] ` <50EDA624.1010008@163.com>
2013-01-10 7:00 ` jianhai luan
[not found] ` <50EF7106.7000302@oracle.com>
[not found] ` <50FCED9F.1050708@oracle.com>
[not found] ` <50FD3AB202000078000B7CD5@nat28.tlf.novell.com>
[not found] ` <1358770987.3279.196.camel@zakaz.uk.xensource.com>
2013-01-21 12:38 ` [V2] " Jason Luan
-- strict thread matches above, loose matches on Subject: below --
2013-01-09 15:07 Jason Luan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50ECC2C4.5060501@163.com \
--to=luanjianhai@163$(echo .)com \
--cc=Ian.Campbell@citrix$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xen-devel@lists$(echo .)xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox