Thanks very much for the positive feedback. New video coming soon :)
@Thomas-oh6os10 ай бұрын
@@Netcademy you make great Videos woth it and evpn.....i live it
@Thomas-oh6os10 ай бұрын
Love it....wrong table on my phone
@Thomas-oh6os10 ай бұрын
@@Netcademy your Videos ate verlinken good.i understand all what you say.....great again
@Netcademy10 ай бұрын
A few more videos to come on EVPN - VXLAN. Getting onto configuration soon :)@@Thomas-oh6os
@123Amanulhaq6 ай бұрын
Bravo!!! Thanks for making quality content. What I found really helpful was pure focus on concept, explaining intricate terminologies in simplified way without getting into vendor specific demo quickly. Sticking to JUST concepts and explaining them in such simplified manner was fun to watch.
@Netcademy6 ай бұрын
@@123Amanulhaq thanks so much for the kind words, great feedback and your support 👌👍
@onlylettersinname10 ай бұрын
Why is the firewall placed on the spine?? I have read a few places where they say to place the firewall on the leaves
@onlylettersinname10 ай бұрын
Nevermind lol
@Netcademy10 ай бұрын
Yes you’re absolutely correct that a firewall would be placed on a leaf device and might sit within a service block. Obviously it too would have layer 3 capabilities and, maybe, providing some kind of DCI capabilities. Think this was just an illustration not an actual architecture recommendation 👍
@Thomas-oh6os10 ай бұрын
.
@DCA_Strategy4 ай бұрын
Thank you so much, I didn't have seen the all episodes of the serie. I have a question, I saw so much videos about EVPN and VXLAN, but I can't find a good tutorial for adding a firewall to the design to handle the traffic between the vlans and handle traffic to internet, it will be great if you make a tutorial about how to add a firewall in Spine Leaf architecture and use it for handling traffic.
@Netcademy4 ай бұрын
I’ll add this to my list 😂👍 Thanks for your support
@悠然弈雪9 ай бұрын
非常感谢,帮了我很大的忙,thanks
@Netcademy7 ай бұрын
Thanks very much!
@AbdoAbdo-jz2pj4 ай бұрын
Thanks for the great explanation. I have a couple of questions here concerning the DF action mechanism. 1- you explained the case when the server 10.1.1.3 picks leaf 3 to send BUM traffic to, leaf 3 will send it out to leaves 1 & 2. yet leaf 2 will not send it out back to server 10.1.1.3 because it is not DF for this VNI, but what about User 2 which is single homed to leaf 2 in same VNI? how this BUM traffic will reach it? 2- in the case if server 10.1.1.3 picks leaf 2 to send the BUM traffic to, leaf 2 would send it over to leaves 1 & 3, in this case leaf 3 will forward back to server 10.1.1.3, as it is the DF for this VNI? Thanks and best of luck
@johnm2310Ай бұрын
1. i am not sure but maybe some kind of local learning on leaf 2 happens 2. this is where split horizon comes in
@dineshstill75734 ай бұрын
Another question. Do we run into a scenario, where a user sends arp request of a server which it wants to communicate and leaf doesn’t know the MAC address of server to reply proxy arp? How does leaf handle that arp request as it doesn’t know MAC address of server to reply via proxy arp.
@Netcademy4 ай бұрын
Honestly I don’t know of such a scenario. If a leaf is participating in an EVI then it will advertise, via RT2 etc, the MACs of all locally connected servers/ hosts etc. remote leafs will learn of that remote MAC addresses, which VTEP to reach it, which egress interfaces etc. But at the end of the day if a leaf doesn’t have an entry in its various tables to send traffic to, unless there’s a default route I can’t see how that traffic could not be dropped. However like I said I’ve never seen or heard of this as it just happens naturally ie advertisement of MACs via EVPN Thanks for your support 👍
@dineshstill75734 ай бұрын
@@Netcademy thank you for the reply David.
@kshitijamin59923 ай бұрын
Hello, amazing video. Thank you for this! at 30:50 you mention the server wants to send BUM traffic which leaves from Leaf 3 and it reaches Leaf 1 and Leaf 2 but Leaf 2 drops the BUM traffic since it is not the DF then why does Leaf 1 accept the BUM traffic even though its not the DF
@johnm2310Ай бұрын
Leaf 2 and leaf 3( as they are multihomed ) have an election using RT4 for DF and non DF election....leaf 1 is not part of that as it is not mutihomed and esi is 0
@coriolanus148 ай бұрын
HI, thanks for sharing this content, it is very informative. I've got soume doubts regarding the Host connectivity.The host must be connected at L2 with LACP, hence you can't connect it to leaf2 and leaf3 and use multipath
@Netcademy8 ай бұрын
Glad you found it informative. In this video the video wasn't about the hosts/ servers. The connection is there just for illustrative purposes, nothing more. In a later video you will see me configuring ESI-LAG/ AE between leaf and spine devices. As you can see the host here isn't configured or even turned on. It's more for illustrative purposes as this video is concentrating on theory not configuration. Thanks for watching :) 👍
@DCA_Strategy4 ай бұрын
Hi, you can't connect the server to Leaf3 en Leaf4 for Multipathing in this situation, I understand this is more for illustration purposes. But if you want to connect the server to Leaf3 en 4 you should build MCLAG or VPC in Cisco world between the Leaf3 en Leaf4 and they will work like one VTEP, but it will add complexities in the design.
@dineshstill75734 ай бұрын
Hi David. Question regarding DF (Designated forwarder). While explaining the scenario of handling BUM traffic. You said Leaf3 is elected as DF for vlan 10. What happens when server send BUM traffic to User 2 (vlan 10) on leaf 2? When Leaf 3 send BUM traffic coming from server to Leaf 2, will leaf 2 still drop the BUM traffic as it is not DF for vlan 10? If so we are in a situation where we are dropping traffic destined to user 2 from server which are in same vlan 10. How does EVPN handle this kind of scenario. Correct me if I’m wrong anywhere. Thank you. Btw, your videos on EVPN VxLAN are great!