as I know. at the begining. your server will send arp to anycast gw. so vtep has server arp information through arp table. then transcode in BGP EVPN afi as type2 information. for type3 when you ask BGP to dealing bum traffic without underlay multicast enable. just using ingress replicarion by using BGP to delivered. BGP will gen type3 to other speaker. so if bum is coming from downstream server. vtep will encap bum to everyone. I know it's sounds not efficient. so BGP EVPN also has enhanced feature called arp nd suppress. cuz in real deployment. your server is alive. if will trigger anycast gw. so both vtep and bgp should have each type2 information. so with arp suppress. if vtep has remote server type2 information. there has no type3 traffic across the fabric. which make sense.
by the way. the workflow that I'm talking about is based on Cisco nexus and cumulus Linux implementaion. but I think the ideas should be the same across diff vendors.
JT seems to be a knowledgeable guy but his THICK ACCENT just kills it. It is so hard to understand coupled with his inability to show route type slides in bigger font just makes me extremely disappointed.
Great podcast, keep it up guy's 👍
Excellent information. Thanks.
why we need mac-only route-type 2 , if we already have all information in mac-ip route-type 2?
Hi...2networking godfather...
of course it's amazing live stream...
keep going..
when ARP Broadcast Received How VTEP knows it should Generate Type 2 Route and Type 3 Route?
as I know.
at the begining.
your server will send arp to anycast gw. so vtep has server arp information through arp table. then transcode in BGP EVPN afi as type2 information.
for type3 when you ask BGP to dealing bum traffic without underlay multicast enable. just using ingress replicarion by using BGP to delivered.
BGP will gen type3 to other speaker.
so if bum is coming from downstream server. vtep will encap bum to everyone. I know it's sounds not efficient. so BGP EVPN also has enhanced feature called arp nd suppress. cuz in real deployment.
your server is alive. if will trigger anycast gw. so both vtep and bgp should have each type2 information.
so with arp suppress. if vtep has remote server type2 information. there has no type3 traffic across the fabric. which make sense.
by the way. the workflow that I'm talking about is based on Cisco nexus and cumulus Linux implementaion.
but I think the ideas should be the same across diff vendors.
JT seems to be a knowledgeable guy but his THICK ACCENT just kills it. It is so hard to understand coupled with his inability to show route type slides in bigger font just makes me extremely disappointed.