Відео

Thanks for the comment. Glad to know you found this useful

Np at all, thanks for the comment

Thanks Vishnu, glad that you liked the video.

Thanks for the comment. Glad to know you found this useful..

Thanks for the comment. Glad to know you liked the content. Yes sure, committed to it.

Thanks, glad to know you liked the content.

Thanks Santosh ji, glad to know you found the content useful.

Thanks Philip, glad to know it was useful..

Thanks for the comment. So glad that you found this valuable.

Thanks for the comment. Glad to know you found the video useful

Thanks Santosh Mishra ji..glad to know it was useful for you..

Thanks Syed, glad that you liked the content.

haha, now that you noticed I can say sustainability and environmental perspective.. Good observation btw..

Thanks for the comment, glad to know that you found the video useful. Yes, EVPN doesnt change anything on the host side. It is still flood and learn. But with EVPN, Switch learn the destination MAC address via EVPN control plane, it can supress that flooding at the vtep itself whereas your VPLS or traditional switching doesnt do that. Hope this helps.

@@emergingtechbytes how does it help if arp broadcast is happening for host to learn destination Mac n sent to all other PEs then at that time only pe can also populate their table?? Is PE has got mechanism to look as destination ip of arp packet to reply back the destination Mac?? N so don't forward arp broadcast to other pes.

@@minalagrawal5638 From the host side, there will be no change. It will follow the usual mechanism. But when the arp packets come to switch, now here is the change. Via EVPN Route Type 2, Switch already knows the destination MAC address so it can suppress the arp packet, basically no flooding happens towards other switches or in your words no flooding towards other PEs. This is the process when ARP suppression is used. ARP suppression is an enhancement provided by the MP-BGP EVPN control plane to reduce network flooding caused by broadcast traffic from ARP. Hope this helps.

Let me know if this is still not clear.

@@emergingtechbytes thanks a lot .. i got it. I really appreciate your timely responses, it helped me a lot.

Thank you for comment and glad that you found the video useful. Ah ok, not sure if you recall the timestamp where I said port number rather than a protocol field, if you recall, let me know. But you are right, ports numbers are at transport layer...

​@@emergingtechbytes it's at 41:40 - 42:00.

Hi, thanks for your query. Transport label is basically a MPLS label used for hop by hop switching in a MPLS network. Hope this helps and Happy Learning!!!

Thanks for the comment, glad that you found the content useful. Unfortunately at this time I was learning video editing, in fact still learning it. Recent videos are better, hopefully you will find them useful as well.

@@emergingtechbytes I understand. I learn a great deal about VPLS and the perspectives and examples are very helpful.

@@DrGriff2000 Great..

Thanks jefeymathew3609, glad to you found this useful

jefeymathew3609- thanks for the for comment. Feel free to distribute this in your circle..I will be grateful.

jefeymathew3609, Thanks for the feedback. Glad that it was useful

Thanks for the feedback Patrick. I will see what more I can do from next video onwards..

Thanks Aruran, glad to know you found this useful

Thanks, Glad to know you found this useful

Thanks for the comment. Glad to know you found this useful.

Thanks.

Thanks for the comment and glad to know you found this useful. Regarding queries: 1. Using same range is not a problem and there will be no conflict. Each LSR assign label independently. 2. Yes, LDP Assign labels to IGP based destinations 3. Yes, labels can be assigned to physical link IPs as well. Hope this helps.

Thanks Arunan for the comment, glad to know you found this useful. Can you be little more descriptive which case you are talking here. Though IGP is there, its IGP which will select the best path and LDP just provide the Label to be used for forwarding via that path. Not sure if this answer your query, if not tell me what part of the video you are talking about. Thanks

Thank you for your response. If EIGRP is being used as the IGP, will LDP distribute labels for both paths to the same destination?

@@aruranganeshan2951 np at all. yes LDP will assign labels to all IGP paths, primary or secondary. IGP will decide the best path and whatever label LDP assign for that path, that label will be used for forwarding.

Thanks for the comments, glad to know it is helping.

Thanks @aruranganeshan2951, glad to know that it was useful for you.

Thanks @JKRowl, Glad to know that it was useful for you.

Thanks a lot Arun, Glad to know that it was helpful

Thanks Benhur, glad to know that you found this useful.

Thanks Fernando for the query, actually this lab has been dismantled but I will resume this series in some time. You may stay tuned.

Thanks, Glad to know that you are finding the content useful.

Thanks for your query. 4 or sometime 5 labels can be seen even in carrier supporting carrier (CSC) scenario as well. But here is the catch, I had seen when there are more labels in a stack , it hit the hardware limit of the device as well. This label stack depth support depends on vendor as well.

Thanks Scott for the comment. Glad to know it was useful for you..

Thanks for the comment..Glad that you found the story useful

Thanks Enrique Gabriel, I am glad that you found this useful.

I totally agree with that.. I learn EVPN-VXLAN from him.. Its outstanding content and presentation.. Its there on Udemy now

Thanks for the comment. Glad to know that you are finding this useful

Thanks a lot for the comment Harpreet ji. If I may correct you, RD is only used to distinguish a route like you may have overlapping subnets in VPNs, So RD will make them unique. its the Route-Target (RT) value that can be used to leak routes. Having said this, I didnt understand your query, if you may elaborate a bit more and point me to the time stamp in the video that would be great.

@@emergingtechbytes as you said, RD is only used to distinguish a route and this distinguished route will traverse towards egress node. On egress node, we will have this unique route. As this route is unique, why we need RT at egress node ?

@@harpreetsinghhoshiarpur4113 First of all, its great to see that you are thinking in this direction. Always question like this and I am sure you will go a long way in your career. Having said this, RT is very much needed. To keep it precise and short, lets say you have 1000 unique routes and on other end you only need 300 routes, now it you tag these 300 routes with a simple tag which is RT(Extended Community) then on other end you can simply accept route just for this tag rather than scanning all routes individually and then picking these 300 routes. Also please note RT is not something that got introduced with EVPN, it was there since MPLS days and there are more reasons for it.

@@emergingtechbytes Thanks for clarification.