EVPN/VLXAN uses Local Bias method for MH split horizon, which is specified in RFC 8365.
Extending EVPN to servers don’t require new IETF standards – the servers just need to support existing relevant standards. Having said that, with many servers in the underlay, routing in the underlay needs to be able to scale well. For that you can run BGP in the underlay (RFC 7938), or RIFT (draft-ietf-rift-rift), or LSVR (draft-ietf-lsvr-bgp-spf). Jeffrey From: BESS <[email protected]> On Behalf Of UTTARO, JAMES Sent: Wednesday, March 4, 2020 7:17 AM To: Gyan Mishra <[email protected]>; BESS <[email protected]> Subject: Re: [bess] VXLAN EVPN fabric extension to Hypervisor VM Gyan, One of the big advantages of EVPN is the MLAG capability without the need for proprietary MLAG solutions. We have been actively testing EV-LAG to accomplish this in the WAN for L2 services.. That being said, we use EVPN/MPLS where MH ( EV-LAG ) is conveyed via labels.. My understanding is that when using EVPN/VXLAN proprietary mechanisms are need to make EV-LAG work.. The is no SH label.. Thanks, Jim Uttaro From: BESS <[email protected]<mailto:[email protected]>> On Behalf Of Gyan Mishra Sent: Monday, March 02, 2020 6:26 PM To: BESS <[email protected]<mailto:[email protected]>> Subject: [bess] VXLAN EVPN fabric extension to Hypervisor VM 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]<mailto:[email protected]>
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
