Appreciate you sharing thoughts.
On Mon, Mar 2, 2020 at 7:08 PM Robert Raszuk <[email protected]> wrote:
> Hi Gyan,
>
> You are touching subject close to me so let me share my perspective on
> your doubts below ;)
>
> > maybe some advantages of elimination of L2 to the host
>
> Not some but huge !
>
Please name a few benefits of L3 comparing to L2 MLAG & no STP. One
issue is host lacp misconfiguration which as a standard we suspend
individual links to force server folks to fix lacp
>
> > BGP multipath provides flow based uneven load balancing
>
> First Contrail/Tungsten does not use BGP to the hypervisor but XMPP. But
> this is opaque to your concern.
>
Do you know of any vendor or project with a BGP based L3 to host
solution w/ or w/o extending vxlan fabric?
>
> Load balancing and hashing construction is your choice, BGP or XMPP only
> deliver you next hops .. how you spread traffic to them is 100% up to your
> choice. That is the same on hypervisor or on any decent router. LAGs also
> build hash in the way you configure them to do so.
>
Understood. ECMP L3 flow based load balancing has inherently always
had that downside with load balancing compare to per packet Ether bundling
hash are any layer of the network DC, Access, Core etc.
>
> > hypervisor managed by server admins
>
> In any decent network or for that matter even in my lab this is all 100%
> automated. You run one template and execute it. Ansible works pretty well,
> but there are other choices too.
>
> Many thx,
> R.
>
>
Good point as most networks these days have orchestration built into the
solution. Agreed.
>
>
> On Tue, Mar 3, 2020 at 1:00 AM Gyan Mishra <[email protected]> wrote:
>
>>
>> Thanks Robert for the quick response
>>
>> Just thinking out loud - I can see there maybe some advantages of
>> elimination of L2 to the host but the one major disadvantage is that BGP
>> multipath provides flow based uneven load balancing so not as desirable
>> from that standpoint compare to L3 MLAG bundle XOR Src/Dest/Port hash.
>>
>> Other big down side is most enterprises have the hypervisor managed by
>> server admins but if you run BGP now that ends up shifting to network.
>> More complicated.
>>
>> Kind regards
>>
>> Gyan
>>
>> On Mon, Mar 2, 2020 at 6:39 PM Robert Raszuk <[email protected]> wrote:
>>
>>> Hi Gyan,
>>>
>>> Similar architecture has been invented and shipped by Contrail team. Now
>>> that project after they got acquired by Juniper has been renamed to
>>> Tungsten Fabric https://tungsten.io/ while Juniper continued to keep
>>> the original project's name and commercial flavor of it. No guarantees of
>>> any product quality at this point.
>>>
>>> Btw ,,, no need for VXLAN nor BGP to the host. The proposed above
>>> alternative were well thought out and turned to work ways far more
>>> efficient and practical if you zoom into details.
>>>
>>> Best,
>>> Robert.
>>>
>>>
>>> On Tue, Mar 3, 2020 at 12:26 AM Gyan Mishra <[email protected]>
>>> wrote:
>>>
>>>>
>>>> Dear BESS WG
>>>>
>>>> Is anyone aware of any IETF BGP development in the Data Center arena to
>>>> extend BGP VXLAN EVPN to a blade server Hypervisor making the Hypervisor
>>>> part of the vxlan fabric. This could eliminate use of MLAG on the leaf
>>>> switches and eliminate L2 completely from the vxlan fabric thereby
>>>> maximizing stability.
>>>>
>>>> Kind regards,
>>>>
>>>> Gyan
>>>> --
>>>>
>>>> Gyan Mishra
>>>>
>>>> Network Engineering & Technology
>>>>
>>>> Verizon
>>>>
>>>> Silver Spring, MD 20904
>>>>
>>>> Phone: 301 502-1347
>>>>
>>>> Email: [email protected]
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> BESS mailing list
>>>> [email protected]
>>>> https://www.ietf.org/mailman/listinfo/bess
>>>>
>>> --
>>
>> Gyan Mishra
>>
>> Network Engineering & Technology
>>
>> Verizon
>>
>> Silver Spring, MD 20904
>>
>> Phone: 301 502-1347
>>
>> Email: [email protected]
>>
>>
>>
>> --
Gyan Mishra
Network Engineering & Technology
Verizon
Silver Spring, MD 20904
Phone: 301 502-1347
Email: [email protected]
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess
