SD-Access Data Plane part 2
Вставка
- Опубліковано 22 сер 2024
- www.bridgewhy.... is the name of our website where you can find all of our courses.
This video is the fourth video of SD-Access Series. It covers SD-Access data plane in detail. It is recommended that you watch first three videos of this series before watching this video for better understanding.
We have compared how a packet moves in vxlan environment and compared it with normal switching. We have also discussed about vxlan header in detail in this video.
All of our courses are available on bridgewhy.com
Below is the list for courses which we offer,
1. SD-WAN
2. SD-Access
3. Network Security
4. OSPF-BGP-MPLS from Scratch to Design
5. Routing Fundamentals
6. Network Interview Preparation Series.
You can connect me using following medium,
1. www.bridgewhy....
2. Phone Number: 86185 35205
3. WhatsApp: 86185 35205
4. LinkedIn: / vishnu-dutt-586a9813
This series of videos is by far the best explanation i have ever seen on SD-Access. I like how you always start by explaining the traditional way and then put it side by side with the new technology so the learner has something to relate to before learning the new technology. I understand better when i have something to compare with. Thank you for taking your valuable time to make these videos. Absolutely brilliant.
Glad it was helpful! Thanks..
This is the best series of videos on SD Access I've come across so far. I'm looking forward to your future videos.
Glad you like them!
Agreed!
The best SD-Access explanation ever, really appreciate your efforts and keep the good work, I will be the first one to buy your course in udemy.
Your way of teaching is extraordinary.
Thanks Mohamed.. I really appreciate the good words and people like you encourage me to create more videos.. So be there for some more interesting stuff.. I am pretty sure that you will love the control plane of SD-Access..
@@bridgewhy you are welcome and can't wait for more.
@@MohamedAhmed-vw5bc Just to inform you that I have started some course online on SD-WAN and other technologies, If interested please call me +91 9148515862
Great Video. Looking forward for the data plane between two different subnets.
Thanks !!! It's already available in the same channel !!!
Thanks Vishnu for nice Explanation
Thanks!!!
These videos are highly appreciated...
Thanks Pankaj...
Great. Thanks!
Hi Vishnu, The explanations that you have given are great.
Thank you so much 🙂 Released few more on Control Plane.. Please have a look..
fantastic...... very good way to explain traffic flow which we miss in any other sda video....great job
This is the best way to explain the technology shift, Good Work Vishnu.
Nicely explained
Hi , The contents that you have provided so for are very great.
Thanks.. I am glad that you liked the content..
Look forward to see control plane video at the earliest.
Interesting explanation!!... Cant wait for more :)))
Thanks.. Released few more on Control Plane.. Please have a look..
Perfect!
Superb explanation. Keep up the good work
Released few more on Control Plane.. Please have a look..
thank you so much, clear explanation, i hope you upload the new videos soon, thank you
You are welcome! Released few more on Control Plane.. Please have a look..
Very much looking forward to the Control Plane details.
It will be there soon!!!!
Hello i have some understanding like where we will not configure vlan in SDA but in this lecture i can learn that vlan and VNI will be mapped. Will please clear my query
This is really very helpful to understand SD-Access.When are we going to get control plane one ?I am eagerly waiting to see your more SDA-Access video.
Thanks Jamal.. Released few more on Control Plane.. Please have a look..
Nice explanantion... thankyou
Thanks Dude!!!!!
Thanks for such a nice series, I have a doubt, you explained that CP node will replay with loopback IP of Sw3 and Mac of host B . so my query is if CP will reply with Mac of B then why do we need to further send APR to get the MAC of B?
You are correct. This is what we know as ARP supression which can be used and available as one of the feature in SD-Access. But ARP is necessary in case of silent host who do not talk unless they receive ARP request message.
Really appreciate ur way of teaching
One question, I doubt that CP will not provide mac address of the destination PC (1:43) because mac changes over hops and its of no use, But at the last you have explained very correct that the dst mac will be of next device, please correct me if i m wrong
Also you should complete your promise by making remaining videos
never leave ur promise in between 😇😇
Hey, yes your understanding is correct. The inner packet requires the destination mac address of PC which is provided by Control Plane node. This inner packet is encapsulated in vxlan. But VXLAN packet is a IP packet which requires destination mac address of the next hop.
Yes, I will complete the videos 😀😀
The Bridge superb bro
I will be waiting for your next video
u already delayed six months 😀 don’t let ur audience wait
While the arp request from AC1 ro AC3 DNAC will provide the destination loop back IP and Host B mac address also na, then why again arp i going to final destination and giving the arp response to host A. Because at starting of arp packet DNAC is giving the loopback IP of destination and destination of the host also na
great video!
Thanks Martin !!!
Hi vishnu sir , My question is regarding the equal cost multipath , in the underlay ethernet header the destination mac address will be toggling between core-swi1 to core-sw2 mac addresses , is my understanding correcti
Nopes, here we add UDP header fto do multipath based on source and destination port number.
Thank you so much. PLZ I have question about UDP header why we need udp to forward packet ?
As you can see that the external IP header will be having same source and destination IP address (loopback addresses) when different host connected to two edge switches communicate. Hence there is no way to load balance the traffic going out of the edge switches if it has more than two links. We can create vxlan encapsulated packet with different source ports in UDP header and we can select the exit link on the basis of source port. You can say UDP port number helps in equal cost multipathing. Hope this helps..
@@bridgewhy It's clear know thank you very much. :) :)
As per the diagram starts at 11:21 the Underlying should be the original payload and the overlay should be the VXLAN header. Is it right?
Indeed!!! You got it correctly...
@@bridgewhy Thanks a lot for the clarification and reply :)
@@dhandapani1058 You are welcome dude!!!!
Hi, Thanks for sharing these videos.
I have a query on the VTAP Ip (10.0.0.1) and VNI ()VNI=500) , are those IP/VNI's address needs to provide manually ? Or is there any automation.
I have few more queries but I will ask later.
Hey Tech.xyz.. All these parameters (VTEP, VNI) and corresponding protocols (VXLAN, LISP etc) are automatically configured by DNAC which is a single pane of glass. You just need to define your intent on DNAC i.e security policies (micro segmentation), VRF requirements (macro segmentation) etc. and the DNAC will push related configuration to respected edges, borders and control plane nodes. Not only this, DNAC has the feature to automatically create your underlay also. Don't worry we will be covering all this in future videos.
Your questions are always welcome.
@@bridgewhy Thank you.. I will wait for your videos .
@@Techxyz-pj7xz sure.. You are always welcome...
hi vishnu will SW3 FLOOD FRAME ALL ITS LINK OR WILL IT SEND TO HOST B DIRECTLY
host B create cam table entry ? host dont have cam table@2.56
Switches are taking information to forward the packet from control plane.
Then why we are running ospf or is-is in between switches?
Does the network information goes to DNS?
Hi Yogesh, OSPF and IS-IS are running in underlay which guides a VXLAN encapsulated packet to destination switch loopback address. To underlay network, VXLAN packet is simply an IP packet and OSPF provides information to reach the destination switch. You will get this concept once you see both data plane videos..
Great Explanation. I do not see any further videos on Control plane. Are they published via any site?
Thanks Karthik.. I haven't published new videos till yet.. will let you know once done.. Take care..
very nice explanation , i have 1 question ......... you have explained that VNI is mapped to the vlan ID and it makes sense , but what about VRF ? I have read articles where it says that VNI is mapped to the virtual network (VRF) , which is a separate routing table.... Kindly clear my confusion.
Hi Najam.. Great question.. Till now I have explained communication between hosts in the same vlan. Don't worry we will cover the communication between host in different vlan or subnet. This is where VRF's will come in to picture. In SD-Access, vxlan header can carry information about VNI and the same VNI can represent vlan ID and VRF number. I will discuss this in detail in coming videos.
I am glad that you like these videos.
@@bridgewhy thats great , it means within the same vlan(subnet) VNI is mapped to the vlan ID , but when it comes to intervlan routing , the VNI Represents the VRF Instance , am i correct? i am desperately waiting for your new videos , its so nice of you to spread knowledge free of cost. RESPECT!!!!!!!!!
@@bridgewhy when will you upload more videos ? i am desperate to learn more about sd-access and your lessons help a lot.
@@najamhassan4081 The problem is, I am engaged in some projects where I need to devote lots of my time. It will take few more weeks to complete. Will upload as soon as I can..
@@bridgewhy waiting desperately
64k group ID, does it mean SDA only support up to 64k endpoint?
Nopes.. A group ID or SGT represents multiple endpoints that have the same characteristics.. It is analogous to groups you create in active directory.. Also you can consider a particular ID as a group of IP addresses that may or may not be part of same IP subnet... Hope it clears your doubt..
@@bridgewhy Thanks, got it. If we allocate an unique SGT to every endpoint, not in a group. We can have at most 64k endpoint? By way, when you will upload new course. I love it so much.
@@yanglijian Correct.. But it is as good as creating 64 K groups in Active Directory which is not even a corner case use case.. You will see the new videos soon. I am glad that you like this course.. Don't forget to register my channel so that you get the notification whenever I upload new videos..
@@bridgewhy do we can consider the endpoints belongs to the same characteristics as in the same VLAN?
@@TheUnni666 VLAN is no more the the construct to segment endpoints in SDA. You can even have only on VLAN per fabric and it should work. In SDA, we are dividing endpoints on the basis of SGT. This is also called microsegmentation.