Skip to main content

The Top 4 SD-WAN Myths

Software-defined WAN is hot, but there are misconceptions about the technology. We cut through the hype.  Software-defined WAN has received a lot of buzz of late, for good reason: After all, its slogan is essentially “No more MPLS."  That's enough to catch most IT pros' attention. However, one should look beyond slogans to see what the technology can actually deliver.  I've spent a lot of time talking with different SD-WAN vendors to know more about the technology, their products and capabilities. I do see a lot of benefits of this technology, but at the same time I see a lot of marketing mixed with the technical stuff, promising the moon to customers.  This blog, therefore, aims to clear up some misconceptions and myths about SD-WAN.  But before we dig deeper, let's define what SD-WAN is. SD-WAN makes it possible to bond multiple WAN connections -- Internet, MPLS or any other transport pipe --  effectively making the best use of bandwidth and reducing dependency on expensive MPLS links. This is done by placing edge devices at customer sites that are managed centrally. Overlay tunnels are created on top of the available transport links. SD-WAN is transport agnostic, so it does not care about whether the transport is MPLS, broadband or a 4G connection.  There is a direct business case here: Use the Internet pipe to deliver what the MPLS pipe would otherwise deliver. Why purchase a big pipe for MPLS when one can buy a small pipe with a parallel Internet/ broadband (best effort) link? SD-WAN will put the critical, real-time data on the MPLS link and the rest on broadband, thereby reducing the need to have a big pipe of MPLS to carry both kinds of data.

Now let’s start discussing the myths over at Network Computing here.

https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi