Between 0x2 Nerds - An Introduction to EVPN Multihoming with ESI

Jeff and Jeff return this week for an introduction to #EVPN #Multihoming with #ESI

[@johnclarkson6120]

great video. thx a lot. I have a question from Cisco implementation that talking about type4 df electiom its called serve carving. but doc didn't give description for some reason. I wanna to understand this

[@flowingwithlife4969]

hi, Many thanks for uploading the video to KZbin. I always watch all uploads. one small doubt i am having about MH_EVPN. taking the figure in your presentation.. as leaf 5 has learnt the MAC of CE ( MAC C) and sent to Leaf 4 via Rt2. this is ok. now, leaf 6 is unaware of this MAC ( due to hahsing from CE side), so when Leaf 4 sends a packet to MAC C, towards Leaf 6 using alisaing label( learned via rt1 per EVI), then how leaf 6 sends that packet towards CE. my understanding is - > leaf 6 has no entry of MAC C in its local MAC table. is there some mechanism that, leaf 6 knows, if i am receiving a packet with alisaling label for mac vrf X( advertised by me), i will send that packet towards CE without DMAC look Up ? BR// Dipankar.

[@patgame]

@Jeff Tantsura Thank you for all the work you put in these past 10 videos! I also had the same question and you answered it pretty well, and that is indeed very clever to hear, but may have been complex to implement! To summarize, the leaf that did NOT actively learn the Server-MAC due to hashing actually learns the MAC from Route-Type-2 and then constructs its forwarding/or/CAM table for Server-MAC pointing out of ESI? correct? When writing this comment, another thing that I did not clearly understand is, even in multi-homing the only way server is going to see one-virtual-leaf is only when both leaf's are in MLAG, correct? so MLAG is still needed on the leaves?

[@shankarvaranasy8404]

Have you looked at vPC Fabric Peering functionality on NX-OS? It doesn't need peer-link and leverages EVPN fabric for that functionality of peer-link

[@jefftantsura9677]

it is proprietary to NX-OS, which defeats the purpose of using an open standard (EVPN)