If you like our videos and to see more FREE Courses by us, the best way to support our channel is to like, comment, subscribe, and share the videos to help spread the word!
How to deal with scenario if we plan to have communication between spine layers of different fabrics ? ( interfabric communication ). How can we reuse the ASN's in that scenario ?
this is a bit confusing by quickly jumping around different scenario instead of sticking to RFC3928, which we suppose do not need the interlink between the leaf switch. also the external route to WAN confused me as well, I was under impression we are not supposed to mix the underlay route with overlayer routes.
if this video gets 100 likes , we will record other videos similar to this, explaining real life design
100th like here!
If you like our videos and to see more FREE Courses by us, the best way to support our channel is to like, comment, subscribe, and share the videos to help spread the word!
It was a good discussion Orhan. I’m a big fan of all the policy tools and traffic steering capabilities that BGP can give you in DC deployments
It was nice discussion Ramiro , If this post gets 100 likes let's record another one :)
Great sir.. thanks for helping me
Super Duper video
Hi Orhan, why the convergence is faster when the ASN is same for all leaf switches in a pod?
Avoids BGP Path Hunting, have a look at what is it on the channel, BGP Path Hunting
How to deal with scenario if we plan to have communication between spine layers of different fabrics ? ( interfabric communication ). How can we reuse the ASN's in that scenario ?
this is a bit confusing by quickly jumping around different scenario instead of sticking to RFC3928, which we suppose do not need the interlink between the leaf switch. also the external route to WAN confused me as well, I was under impression we are not supposed to mix the underlay route with overlayer routes.
What is BGP "peak/peek" you guys are talking about?
It is BGP PIC, means Prefix Independent Convergence