In this edition of our SD-WAN series I’m going to take a step away from our lab environment and attempt to address a question I get a lot from our customers. “How do we integrate a SD-WAN router or pair of SD-WAN routers into our current environment?” Well the answer I’m afraid is the networking consultants classic line of “It depends”. And it really does, Cisco’s SD-WAN solution was created by engineers with a background in routing and this routing foundation really gives us a lot of flexibility when positioning our SD-WAN routers into our existing environment.
Technology is constantly moving and advancing, and as we continue to innovate we are able to use different enterprise technologies to grow our business. Technology used to be a means to help operate the business but has transformed into a means to better the business beyond those day-to-day operations. Technology is connecting our teams, connecting us with our customers and helping us to serve those customers more efficiently.
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.
Hello, my loyal blog post readers, in this my third installment of our SD-WAN series I am going to walk you through how our vEdge router locates, communicates and authenticates itself onto our SD-WAN fabric. Along the way we will take a look at a few packets captures and command line output to see what is going on under the hood.
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.
Over the past year I have been fortunate enough to work on several Cisco SD-WAN (formally Viptela) deployments. These projects have ranged from small three or four site implementations here in the bay area, right through to large scale international rollouts incorporating hundreds of sites spread-out across the globe with regional POPs providing branch services and backbone connectivity.
Day 2 of Cisco Live was filled with amazing new technology, new applications, new innovative services, and the power of Cisco’s partnerships. Cisco is continuing to build their intent-based networking with DNA, DNA Center now DNA Assurance. What really caught our attention today was the network and security innovations and integrations. Here are our top takeaways.
By this time, I’m sure you’ve all heard about the whole SD-WAN, or Software Defined Wide Area Network, craze hitting the industry. Heck, if you are reading this now, it probably means you are in the process of researching, piloting, or operating one yourself. This is great news! However, if you are looking for a high-level, marketing overview of the four pillars of an SD-WAN, then you are probably in the wrong place! In this article, I’m going to pass on some information from my personal experiences with one SD-WAN solution, Cisco IWAN.
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.
Subscribe to the informative Newsletter to be Notified Updates in the Technology world.