Re: xen-netback notify DomU to send ARP.
From: Jason Luan <hidden>
Date: 2013-01-09 15:07:55
Also in:
xen-devel
于 2013年01月09日 20:03, Ian Campbell 写道:
On Wed, 2013-01-09 at 01:07 +0000, Jason Luan wrote:quoted
于 2013年01月09日 00:00, Ian Campbell 写道:quoted
On Tue, 2013-01-08 at 15:40 +0000, jianhai luan wrote:quoted
On 2013-1-8 21:42, Ian Campbell wrote:quoted
On Tue, 2013-01-08 at 13:13 +0000, Jan Beulich wrote:quoted
quoted
quoted
quoted
On 08.01.13 at 12:57, jianhai luan [off-list ref] 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?Sorry, I'm having a bit of trouble parsing the above, but are you asking what the VIF should do when the active slave in the bond changes without the previously active slave actually failing?
sorry for your misunderstanding.
The issue is that traffic will continue to arrive on the now inactive slave, but will be discarded (the expected behaviour for Active/Passive)?
Yes. the traffic will continue to arrive on the switcher's port which connected the inactive slave before, and the switcher's port don't connect (or don't reach) the inactive slave now, so the link will be disconnected before DomU send ARP. After DomU send ARP, the traffic will know how to reach the correct switcher's port which connected with the active slave.
Is this something which happens in practice? Does the active slave change even while it remains a viable path?
Yes, please think the below the scene. PC -- switcher port A -- eth0 --bond0 --xenbr0 -DomU port B -- eth1/ or PC -- switcher A -- eth0 -- bond0 -- xenbr0 -- DomU \- switcher B -- eth1 / If Port A or switcher A wrong, the traffic from PC to DomU will be disconnected before found correct path (port B or Switcher B ).
Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel