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

Re: [Xen-devel] xen-netback notify DomU to send ARP.

ä 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@xxxxxxxxxx>
     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
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
attached to forget the MAC tables associated with the eth0 port,
that subsequent traffic will be flooded until it learns that eth1 is
new port?

Xen-devel mailing list

Xen-devel mailing list



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