Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt

[Sri Gundavelli <[e-mail]>]

Hi Brian,

Thanks for your response.



On 9/7/11 1:36 PM, "Brian Haley" <[e-mail]> wrote:

> Hi Sri,
> 
> Yes, it's been a while, I tend to only lurk on the MLs these days...
> 
> More inline.
> 
> On 09/07/2011 12:09 AM, Sri Gundavelli wrote:

> 
> I can understand the abstraction, and why you would want to send some messages
> on all the underlying interfaces.
> 
> The Linux bonding driver typically isn't used in this way though, it's more of
> an HA mechanism to attach a system to a switch, or set of switches, via
> multiple
> paths.  Usually just a group of ports on the top-of-rack switch, for example
> in
> 802.3ad mode.  All physical interfaces need to be in the same network.
> 
> I've never seen it used where there are multiple types of physical interfaces
> in
> different networks in the bond, not even sure if that's supported...
> 
> The failure in question is that in some operating modes you can see broadcasts
> sent from other members of the bond (not 802.3ad of course), and that causes
> problems, so we create workarounds by trapping them and only transmitting on
> one
> of the interfaces.  That probably isn't going to happen in your scenario.
> 
> Maybe the easiest solution is to just remove the Linux reference, I probably
> wouldn't have noticed otherwise :)
> 

Thanks for the info about the issue with that usage. I understand what you
are saying. We will try to remove the bonding driver example and leave it
with the requirement, expected external behavior, independent of the
specific approach/OS.


Regards
Sri