You’ve probably seen SD-WAN solutions in the last few years touting themselves as the best thing since Betty White. You gain all of the VPN overlays you want with consumer priced circuits and application visibility. But are those all the things that really make up SD-WAN? Are they even requirements to be considered an SD-WAN solution?
Daniel Dib has done a lot of thinking on the situation and he’s come up with a great list of things that he thinks need to be included to consider a solution SD-WAN. Note that this list isn’t definitive or all-inclusive. But as you go down the bullet points you’ll quickly realize that Daniel is a lot closer to a real SD-WAN definition than your average marketing department:
We’ve been using things like IP SLA and PfR to provide application-aware routing, that is, the ability to send traffic on different paths depending on how a transport is performing, in regards to the amount of packet loss, latency, and jitter. This provides the ability to protect against brownouts and not only blackouts.
Read more here: When Is Something SD-WAN?
- Design: Is It One Site or Two? - October 15, 2019
- Investing in the CWNE - October 15, 2019
- Wi-Fi6 Ratification: Not So Fast My Friend - October 14, 2019
- Connectivity Solved with Aryaka - October 11, 2019
- All-In on AI With Mist and Juniper - October 10, 2019
- Firefox DNS-over-HTTPS for the Enterprise - October 9, 2019
- When Is Something SD-WAN? - October 8, 2019
- Supply-Chain Security and Trust - October 3, 2019
- Using SD-WAN to Unify Communications with NEC and InfoVista - October 3, 2019
- Customer FAQ: Is NAT Security? Should I Remove My Public IPv4 From My Internal Network? - October 1, 2019