In my last post we looked at the steps that a vEdge goes through to bring up its control plane connections and authenticate itself onto the fabric. In this post we will follow on from where we left off and see how we use these control plane connections to exchange topology information, WAN policies and security keys via OMP.
In my last post in the series I introduced you to the four architectural components that control and enable our SD-WAN fabric. In that post I had promised that in our next installment we would take a closer look at our fabric bring up sequence, but if you will indulge me I would like to hold off on that topic for the next post. In its place I would like to use this post to introduce you to the lab environment that I have built for this series and take you through the process of deploying and registering a virtual vEdge router into our lab.
On February 2, 2017 Cisco announced a major issue affecting products from their routing, switching, security and server product lines. Reference Tables A through D below for a full list of affected products and part numbers.
Enjoy the first Fireside Chat. Fireside Chats are a LookingPoint video series where we bring casual technology conversations to you! This week we are discussing one of the hottest topics of 2017: SD-WAN. Sit back, relax, and enjoy a nice fireside chat.
Learn more about SD-WAN here.
The title to this blog is a question that I have been hearing a lot from customers in the last few months. With Gartner’s recent prediction that spending on SD-WAN will rise from $129 million in 2016 to $1.24 billion in 2020, I figured it’s about time I write up a little blog article all about this latest offering to revolutionize the enterprise WAN, or perhaps not!
Subscribe to the informative Newsletter to be Notified Updates in the Technology world.