{"id":9485,"date":"2016-05-26T16:40:23","date_gmt":"2016-05-26T23:40:23","guid":{"rendered":"https:\/\/www.aerocominc.com\/info\/?p=9485"},"modified":"2017-06-27T10:18:37","modified_gmt":"2017-06-27T17:18:37","slug":"cloud-therapy-ep-003-5-ways-to-prepare-for-an-sdwan-install","status":"publish","type":"post","link":"https:\/\/www.aerocominc.com\/info\/cloud-therapy-ep-003-5-ways-to-prepare-for-an-sdwan-install\/","title":{"rendered":"Cloud Therapy: Ep 003 &#8211; 5 Ways to Prepare for an SD-WAN Install"},"content":{"rendered":"<p>&nbsp;<\/p>\n<p><a href=\"https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON.jpg\" rel='magnific'><img loading=\"lazy\" class=\"aligncenter wp-image-9486\" src=\"https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON.jpg\" alt=\"COMING SOON\" width=\"486\" height=\"486\" srcset=\"https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON.jpg 800w, https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON-150x150.jpg 150w, https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON-300x300.jpg 300w, https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON-200x200.jpg 200w, https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON-400x400.jpg 400w, https:\/\/www.aerocominc.com\/info\/wp-content\/uploads\/2016\/05\/COMING-SOON-120x120.jpg 120w\" sizes=\"(max-width: 486px) 100vw, 486px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>So you&#8217;ve decided to move to <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/access\/site-to-site\/sd-wan\/\" target=\"_blank\">SD-WAN<\/a><\/span>. What should your IT department do to make sure you have a smooth installation?<\/p>\n<p>To answer these questions, we invited an expert SD-WAN engineer, <a href=\"https:\/\/www.linkedin.com\/in\/jack-dolan-1897062\/\" target=\"_blank\">Jack Dolan<\/a> from <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/www.aerocominc.com\/company-profile\/aryaka\" target=\"_blank\">Aryaka Networks<\/a><\/span>, to speak with us. Aryaka has been doing SD-WAN as long as anyone so they absolutely know what needs to be done!<\/p>\n<p>Jack explains 5 specific tactical items that IT Departments need to do in order to transition from SD-WAN from <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/access\/site-to-site\/mpls\/\" target=\"_blank\">MPLS<\/a><\/span> or any other type of business WAN&#8230; flawlessly!<\/p>\n<p>For more episodes, find <em><a href=\"https:\/\/itunes.apple.com\/us\/podcast\/cloud-therapy-aerocominc.com\/id1112772590?mt=2\">Cloud Therapy on iTunes<\/a><\/em>!<\/p>\n<p><iframe style=\"border: none;\" src=\"\/\/html5-player.libsyn.com\/embed\/episode\/id\/4356014\/height\/90\/width\/640\/theme\/custom\/autonext\/no\/thumbnail\/yes\/autoplay\/no\/preload\/no\/no_addthis\/no\/direction\/backward\/render-playlist\/no\/custom-color\/87A93A\/\" width=\"640\" height=\"90\" scrolling=\"no\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<h5><span style=\"color: #ff6600;\">Have an AeroCom expert help you sort through every major SD-WAN offering to find your top 3.<\/span> Click below.<\/h5>\n<p><script src=\"\/\/static.leadpages.net\/leadboxes\/current\/embed.js\" async=\"\" defer=\"defer\"><\/script><button style=\"background: #f26e22; border-color: #f26e22; border-radius: 4px; color: #ffffff; display: inline-block; vertical-align: middle; padding: 16px 32px; min-width: 192px; border: 1px solid #f26e22; font-size: 1rem; font-family: Helvetica, Arial, sans-serif; text-align: center; outline: 0; line-height: 1; cursor: pointer; -webkit-transition: background 0.3s, color 0.3s, border 0.3s; transition: background 0.3s, color 0.3s, border 0.3s; box-shadow: 0px 5px 5px rgba(0, 0, 0, 0.6);\" data-leadbox-popup=\"144249073f72a2:136337e37f46dc\">MY TOP 3<\/button> \u00a0 <\/p>\n<h5>\u00a0or<\/h5>\n<p>&nbsp;<\/p>\n<h5><span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/www.aerocominc.com\/search?q=SD-WAN\" target=\"_blank\">Click here to see how IT professionals rate their SD-WAN provider.<\/a><\/span><\/h5>\n<p>&nbsp;<\/p>\n<h5><em>See below for the full transcript:<\/em><\/h5>\n<p>\u00a0 <a href=\"https:\/\/aerocominc.lpages.co\/leadbox\/144718873f72a2%3A136337e37f46dc\/5717271485874176\/\" target=\"_blank\"><img class=\"alignright\" src=\"https:\/\/lh3.googleusercontent.com\/odj7lWuNoLasZk5iG6BtrPhyLuhHeZO5mG6ySy4UET_q00fwwrx5AqFX708SlGp4e8XoCaYh-4nOj4RbQwuOgw=s0\" alt=\"\" \/><\/a><script src=\"https:\/\/aerocominc.lpages.co\/leadbox-1493382615.js\" type=\"text\/javascript\" data-leadbox=\"144718873f72a2:136337e37f46dc\" data-url=\"https:\/\/aerocominc.lpages.co\/leadbox\/144718873f72a2%3A136337e37f46dc\/5717271485874176\/\" data-config=\"%7B%7D\"><\/script>Mike: So, you just finished getting some quotes on this new <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/access\/site-to-site\/sd-wan\/\" target=\"_blank\">SD-WAN<\/a><\/span> stuff and it looks like a service that might be a great fit for creating a better WAN connection for those two remote sites on your network. But, before you pull the trigger and sign paperwork, you stop. There is something you need to know. Your boss is going to ask you how much work this transition will entail and your brain is a little foggy about that question. If that describes the situation you\u2019re in or you think you might be in, you\u2019ll love this podcast.<\/p>\n<p>On the podcast, today, I\u2019ve got a great guest. His name is <a href=\"https:\/\/www.linkedin.com\/in\/jack-dolan-1897062\/\" target=\"_blank\">Jack Dolan<\/a> and he\u2019s a sales engineer with <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/www.aerocominc.com\/company-profile\/aryaka\" target=\"_blank\">Aryaka Networks<\/a><\/span>. Now, Aryaka Networks has been an SD-WAN service provider for about seven or eight years, so they\u2019ve been in the game for a long time. They really know what they\u2019re doing and Jack knows some great stuff.<\/p>\n<p>Today, Jack is going to tell you the five things IT departments need to do in order to transition from an <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/access\/site-to-site\/mpls\/\" target=\"_blank\">MPLS<\/a><\/span> network to an SD-WAN network. In addition to that, he\u2019s also going to help clarify his points by walking us through what needs to take place to install an SD-WAN network if something like <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/cloud\/software-and-applications\/microsoft-office-365\/\" target=\"_blank\">Office 365<\/a><\/span> is a big priority in your environment.<\/p>\n<p>Then, as if that was enough, something really cool he\u2019s going to talk about is Aryaka Network\u2019s ability to give you a <strong>free trial<\/strong>. So, a lot of times, I don\u2019t like to get too salesy on the podcast with providers, but just because it\u2019s a free trial, I thought it would be really cool to ask him: Hey, what does that entail? How do our listeners get to try your service for free? What are the stipulations with that? So, we walk through that a little bit too.<\/p>\n<p>So, it\u2019s a great episode packed with a lot of good information from someone who\u2019s very knowledgeable about SD-WAN, and I hope you enjoy it.<\/p>\n<p>But, before we get started, I wanted to also offer you something free from us. I mentioned it a couple of episodes ago and I\u2019m going to mention it again, it\u2019s a free breakdown of SD-WAN and all of the different capabilities it has versus MPLS, point-to-point, and IPSEC VPN. So, it\u2019s basically a breakdown of how SD-WAN compares to all the other wide area network technologies out there, and we\u2019re giving it away for free as a gift to our listeners. All you have to do to get it is text the word \u201cWANGUIDE\u201d to 44-222. Again, text the word \u201cWANGUIDE\u201d to the number 44-222 and we will email you a free copy of this comparison we made comparing SD-WAN to all the other wide area network services out there. Enjoy the free gift and let\u2019s get on with the show.<\/p>\n<p>Alright, Jack, welcome to the program. Thanks for coming on.<\/p>\n<p>Jack: Thanks for the invite, appreciate it.<\/p>\n<p>Mike: Awesome. Well, can you tell us a little bit about yourself both personally and professionally?<\/p>\n<p>Jack: Sure. My name is Jack Dolan. I\u2019m out of Greenville, South Carolina. I\u2019ve lived here for about eleven years. I have three wonderful kids, two grandchildren. I\u2019ve been to a few companies before Aryaka Networks, which I\u2019ve been employed with for about two\/two and a half years.<\/p>\n<p>Mike: Awesome.<\/p>\n<p>Jack: Before that, it was with <a href=\"https:\/\/www.riverbed.com\/index.html\" target=\"_blank\">Riverbed Technology<\/a> for four and a half years. Before that, I was with <a href=\"https:\/\/bto.bluecoat.com\/knowledgebase\" target=\"_blank\">Blue Coat<\/a>. Before that, it was with <a href=\"https:\/\/www.avaya.com\/en\/\" target=\"_blank\">RouteScience Technologies<\/a>. RouteScience was one of the first companies I did where WAN optimization- where we were looking at quality of paths. So, you got multiple paths, you get to choose which path is best for your applications, which is, kind of, what SD-WAN is today. So, I\u2019ve got a lot of experience even up to WAN optimization and byte caching and compression that Riverbed provided. What\u2019s really neat about the company that I\u2019m at now is that it provides a lot my background all in to one product or service. So, that\u2019s, kind of, interesting. So, that\u2019s my background.<\/p>\n<p>Mike: Very cool. That\u2019s an awesome background and I think that really helps our listeners out in terms of knowing a little bit more about SD-WAN. You\u2019re a great person to talk to, which is why we have you on the show.<\/p>\n<p>So, Jack is going to talk to us today about five things that an IT department needs to do in preparation to successfully transfer from an MPLS network to an SD-WAN network, because I know a lot of you guys out there, Sys Admins, IT departments, you guys currently have MPLS and you\u2019re considering SD-WAN, but you\u2019re thinking what\u2019s involved with that transition.<\/p>\n<p>So, Jack, with that, I\u2019m just going to turn it over to you, and let\u2019s hit on number one.<\/p>\n<p>Jack: Sure, alright. The first thing that I would think about as far as if I wanted to move from MPLS to SD-WAN is know that SD-WAN do not have to be an all or nothing solution. It can, and we will talk about that, but it can be a solution for something very specific.<\/p>\n<p>Let\u2019s say you have a specific application that you need better performance for. Let\u2019s say you have to get Office 365 and MPLS doesn\u2019t provide that capability, and you don\u2019t want to use the internet to get to Office 365, SD-WAN might be a very good solution for that. So, keep in mind that whatever your goal is, stay focused on that goal and attack that goal so that, at first, you might be just wanting to accomplish something small to get to something big. So, know what you want to achieve with your SD-WAN solution, stay focused on that, implement that, and, obviously, later on MPLS, and replacing that would just be the evolution \u2013 it\u2019s the normal progress of things.<\/p>\n<p>Mike: Awesome. That\u2019s an angle that I wasn\u2019t as familiar with \u2013 going for a specific application. What are some of the other reasons that someone might want to go to an SD-WAN network in addition to improving their performance on one specific application. Are there other reasons why?<\/p>\n<p>Jack: Yeah. One of the biggest reasons is just, you know, total cost of ownership. So, MPLS, when you compare the price, specially when you go overseas and also the agility that they don\u2019t have, it could take weeks, months, something like that, to bring in an MPLS link to that location would be very expensive. You can pop in an SD-WAN solution pretty quickly, usually in less than a week and have it up and running very quickly. Therefore, it\u2019s more of a strategic play than it is a tactical play. You\u2019re not trying to fix something. What you\u2019re really trying to do is- You know what? I just want to go and\u2026 I want to get rid of MPLS or I want to reach places that MPLS can\u2019t reach and get the same quality of service that MPLS could do, but MPLS is having a hard time doing because of hard to reach places.<\/p>\n<p>So, there are a couple of other reasons. Most customers, what they do is they\u2019re looking for something specific to improve. A lot of customers will, just right of the bat, \u201cHey, I don\u2019t want to deal with MPLS anymore. It\u2019s too expensive. They\u2019re support isn\u2019t what I thought it was. How do I get to an SD-WAN solution that\u2019s better? Either they can maintain it or they can get a service like ours to maintain it, you know, be proactive or whatever, and it\u2019s a very simple this or that type of a decision. So, we see both.<\/p>\n<p>Mike: That makes sense. So, some of the top three that I heard were: obviously, improving the performance of a specific application, number one. Number two, cost savings over MPLS, and number three, reaching a location that MPLS network cannot reach; those are, kind of, three examples of the top priorities that companies might have when they\u2019re looking to transition from MPLS to SD-WAN. Is that fair?<\/p>\n<p>Jack: Yeah. Those hard to reach places are sometimes places where MPLS say they\u2019re reaching, but it\u2019s really a <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.aerocominc.com\/info\/our-products\/access\/internet\/fiber\/\" target=\"_blank\">DIA<\/a><\/span>, which is, you know, direct internet access. So, they\u2019re really getting an internet link to do MPLS, which means they\u2019re really riding the internet. So, why pay the extra money for MPLS after that location when you can just use your internet link and do an SD-WAN from there?<\/p>\n<p>Mike: Right. Now, how would that affect how they approach their implementation? Say, if somebody is focused on cost savings over MPLS versus trying to improve the performance of a specific application. I mean, there are some assumptions I can make there, but rather than assume stuff, I figure I\u2019d just rather ask you. How would that really change how they\u2019re implementing it or how they\u2019re evaluating providers?<\/p>\n<p>Jack: That\u2019s a great question because a lot of times what customers want to do with SD-WAN is, \u201cHey, I\u2019ve got this specific issue or a problem that MPLS is not able to handle,\u201d so they\u2019re, kind of, laser-focused on that one problem. Can SD-WAN help with that problem? So, there are a lot of features that SD-WAN can bring to the table for them, a lot of opportunities to tweak certain things whether it would be \u201cHey, let\u2019s use both links,\u201d if you\u2019ve got two ISP links and you want to be able to use both of them. We want to use the lowest <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Latency_(engineering)\" target=\"_blank\">latency<\/a> <\/span>one for voice, the one with the least <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Packet_loss\" target=\"_blank\">packet loss<\/a><\/span> \u2013 we want to use that link.<\/p>\n<p>Of course, if something doesn\u2019t meet the criteria or the quality of service requirements that you wanted to meet \u2013 let\u2019s say, 40 milliseconds round trip as far as <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Round-trip_delay_time\" target=\"_blank\">ping time<\/a><\/span>. If it goes above that and if the loss has increased\u2026 If it goes above, let\u2019s say, 1% loss, then go ahead and move it to the other path as long as the other path is good enough. This is the kind of technology that MPLS doesn\u2019t have, right?<\/p>\n<p>So, we could actually make voice better simply by taking advantage of the two paths that we have. The probability of those two paths having loss at the same time is pretty nil, therefore we could improve your voice, we could improve your virtual desktop interface where people are doing screen space back and forth with <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.citrix.com\/\" target=\"_blank\">Citrix<\/a><\/span> or with <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/www.vmware.com\/\" target=\"_blank\">VMware VDI<\/a><\/span>, things like that, or video. So, some of these things are what SD-WAN, kind of, prides ourselves on and the fact that we can even take these things that normally require quality of service, and yes we can provide that too, but we can also specifically fix applications through certain features that we wall have that MPLS doesn\u2019t.<\/p>\n<p>Mike: Got it. That makes sense. Cool. Okay, so, number one was staying focused on the purpose of your SD-WAN. How about number two?<\/p>\n<p>Jack: Well, the second one is understanding your SD-WAN deployment. How are you going to deploy this? All SD-WAN solutions require some kind of appliance that goes on site at the customer\u2019s site. The appliance has the intelligence that\u2019s needed to properly route traffic based on performance over the best path. Some of these appliances also have certain features that you can take advantage of such us <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.bluecoat.com\/sites\/default\/files\/documents\/files\/Byte_Caching.a.pdf\" target=\"_blank\">byte caching<\/a><\/span> and <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Data_compression\" target=\"_blank\">compression<\/a><\/span>, <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Transmission_Control_Protocol\" target=\"_blank\">TCP<\/a><\/span> (algorithms might different from everybody else), <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Tunneling_protocol\" target=\"_blank\">secure tunnels<\/a><\/span>, time to replay, there are a lot of things that you can take advantage of. These are some of the features that talk about the first criteria.<\/p>\n<p>But, part of that deployment, depending on what features you want to use, could affect how you want to deploy that appliance at each site. You want it to be like a next hop router, just like any other service provider \u2013 if you go left, it\u2019s MPLS, If you go right, it\u2019s the SD-WAN, or you can have it sit, literally, replacing the firewall. A lot of our devices can replace a simple firewall. It doesn\u2019t do all the <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/www.paloaltonetworks.com\/\" target=\"_blank\">Palo Alto<\/a><\/span> stuff, but if you\u2019re basically just trying to replace an <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/www.cisco.com\/c\/en\/us\/products\/security\/adaptive-security-appliance-asa-software\/index.html\" target=\"_blank\">ASA<\/a><\/span>, you know, it\u2019s real simple to do. If you have an ASA that\u2019s up for renewal, this might be a good opportunity. We\u2019re killing two birds with one stone, right?<\/p>\n<p>Mike: Right.<\/p>\n<p>Jack: You can place it transparently bridge. This is where as the traffic comes through it, it\u2019s in path, just like the firewall, what happens is the appliance would intercept only interesting data \u2013 traffic that needs to be routed across the SD-WAN, if it doesn\u2019t need to be routed, it\u2019s simply passed through a bridge through. So, there are a couple of deployment models.<\/p>\n<p>So, understand your environment for deployment. Keep in mind, are things like appliance redundancy required? Path redundancy, is that required? Path diversity. Path diversity is very, very important because if you\u2019re trying to communicate between two locations across two different paths and using those paths at the same time over the internet. You don\u2019t want them to actually converge in to one autonomous system on the internet at some place because that means you don\u2019t have full path diversity end to end. What you really want is that diversity so that if that one path is having an issue (loss, latency, <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Jitter\" target=\"_blank\">jitter<\/a><\/span>), the other path, probably, isn\u2019t having that issue, therefore, you can move the traffic to that immediately, usually in less than a second.<\/p>\n<p>Mike: That\u2019s awesome.<\/p>\n<p>Jack: So, these are some of the things that need to be thought about as far as how you\u2019re going to deploy. At my company at Aryaka Networks, that\u2019s what we do. That\u2019s what my job is \u2013 to help design and deploy this piece of it.<\/p>\n<p>Mike: Awesome. So, this is, kind of, like developing a little cheat sheet prior to an IT department quoting different SD-WAN providers. It would be to understand a little bit about the deployment models or spend some time, maybe, with the first provider that they talk to, and really understand how that provider deploys their SD-WAN service.<\/p>\n<p>Jack: Exactly. For instance, at Aryaka, we don\u2019t need two links. One link is fine in a lot of cases. I can get in to that a little bit later, but basically most SD-WAN provides two links, and that\u2019s great if you can do that \u2013 we highly recommend it \u2013 but, we can get pretty far with a single link as well. So, I can get in to that too.<\/p>\n<p>Mike: Awesome. Okay, so we\u2019ve got two down. Hit us with number three.<\/p>\n<p>Jack: Before you go to do the implementation, obviously, part of the design \u2013 and this is more like a two and a half than it is a three \u2013 but make sure that your network topologies are updated. I can\u2019t tell you how many times we go to implement and the data that we\u2019re working with is just out of date. So, that\u2019s the big thing. I mean, if you have ten sites, ten branch offices, when was the last time you updated your <a href=\"https:\/\/products.office.com\/en-us\/visio\/flowchart-software?tab=tabs-1\" target=\"_blank\"><span style=\"color: #ff6600;\">Visio<\/span> <\/a>diagrams, so something like that. So, that\u2019s very, very helpful specially when you want to know how to put them in, which deployment model you use, so make sure that that\u2019s all up to date. So, that\u2019s pretty easy to do.<\/p>\n<p>Mike: Yeah. I could see that where if a company\u2019s been around a long time or there has been some turnover in the IT department, a lot of times, I\u2019ve seen, myself, talking to IT departments where some of that stuff is out of date, so I think, yeah, that\u2019s a good point. How does that affect their implementation in terms of implementing SD-WAN? What\u2019s like a scenario where if it\u2019s not up to date, it could really hurt the implementation?<\/p>\n<p>Jack: Well, such us they have two carriers where they may have replaced the carrier and it\u2019s just not updated on the information. Therefore, the IP addresses might be incorrect and, therefore, the IP addresses that we could be assigned or that the appliance could be assigned are just not right. So, when the system or when the appliances ship out there with the configuration doesn\u2019t work, we may not have hands on experience on site \u2013 that slows things down. So, that\u2019s why it\u2019s very, very important to have updated information.<\/p>\n<p>Mike: Yeah, good point. Awesome. Alright, what about number four?<\/p>\n<p>Jack: Number four is when you actually go to install or implement. So, you have this model, it\u2019s deployed. In our case we\u2019ll bring up secure tunnels to our closest <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Point_of_presence\" target=\"_blank\">POP<\/a><\/span> to get it on to our core network, so now we have reachability end to end. The next step is to simply route the traffic over your SD-WAN. That could be as simple as a static route; that could be as simple as listening to <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Routing_Information_Protocol\" target=\"_blank\">RIP<\/a><\/span> updates from the appliance or <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Border_Gateway_Protocol\" target=\"_blank\">BGP<\/a><\/span> updates from the appliance. It\u2019s simply pushing the traffic on to the network. Also, if it\u2019s in-path, the traffic is already going through, you just simply turn on \u201cHey, intercept this traffic,\u201d and it would start sending it over the SD-WAN.<\/p>\n<p>The most important thing is that when somebody implements their first time traffic going over the network with default settings, nothing should break. Their applications should still run fine. What you want to do after that is that\u2019s when you want to start tweaking. So, first of all, you implement, make sure everything\u2019s running fine. It should only take a couple of hours or something like that. Then, later on, you might want to do some tweaking if necessary. So, this is where you would say for this application I want to watch for these network characteristics or network performance characteristics, and then if anything like this happens, move. So, make sure that you get a good baseline first, okay?<\/p>\n<p>Mike: That makes sense.<\/p>\n<p>Jake: The other thing is, you know, keep it simple. There\u2019s no reason to add complexity just because it exists. That\u2019s huge in the network world, right?<\/p>\n<p>Mike: Right.<\/p>\n<p>Jake: Just because you can tweak this now doesn\u2019t mean you need to. So, keep it simple for you because, you know, routing by itself is hard. When you start tweaking with performance routing\u2026 Hey, when this traffic reaches this much bandwidth usage, okay, move it over to this. Well, that application, by moving it over to the other route or other path, could affect other applications that are in route back to the other one, you could actually cause some serious performance issues thinking you\u2019re doing well. So, just keep your policies very simple.<\/p>\n<p>Mike: That\u2019s a great tip. Then, going back to the actual implementation, are there ways to do it where your current network is still up and running and you\u2019re kind of setting up your SD-WAN network without interruption to your current network?<\/p>\n<p>Jack: Yeah, absolutely. So, like I said, a lot of appliances can be placed in-path and it\u2019s simply a pass through box, so however your routing is doing today, we\u2019re not going to interrupt that. The only time we interrupt it is, you know\u2026 It takes what? Five seconds to put in a box, right? We actually plug in LAN port and WAN port and it just goes right on through.<\/p>\n<p>So, we can implement without affecting their specific production traffic, but what we like to do is when they start moving the traffic over to the SD-WAN, okay, it\u2019s simply a route change. Let\u2019s say you have a branch office and that branch office was Network A and the data center is Network D. In the branch office you say, \u201cHey, the next hop for Network D is this appliance\u201d and then the appliance takes it from there. Then, simultaneously, in a lot of cases depends on which vendor or SD-WAN solution you\u2019re talking about, the other side has to do the exact same thing at the same time. That\u2019s because some of the features, such as byte caching and compression, TCP acceleration, that requires symmetry, route symmetry.<\/p>\n<p>Mike: Right.<\/p>\n<p>Jack: So, this is where, you know, if you send out an SD-WAN, it has to come back SD-WAN \u2013 very, very important for those features, those acceleration features, to work. Alright? So, it\u2019s simply a routing statement.<\/p>\n<p>The answer to your question is it\u2019s simply a routing\u2026 Route convergence happen all the time on MPLS, so going from one path to another within their MPLS cloud happens all the time. This is no different, so it\u2019s not really impacting your network. What you do is you simply move the traffic over so that, between those two sites where you\u2019re using the SD-WAN network, you\u2019re taking a look at all the visibility portal, and the graphics, and the reports to see how well your traffic is doing. Obviously, you want to take baseline testing, performance testing before, and take those same baseline testings after to make sure you\u2019re getting improved performance. Okay?<\/p>\n<p>Mike: Got it.<\/p>\n<p>Jack: Making sure you\u2019re hitting your goal, which is\u2026 Remember, the first one was know your goals, know what you\u2019re trying to achieve. If you\u2019re trying to achieve better performance for an application, you want to have some baseline testing and you want to have some after the SD-WAN was deployed testing to see if your performance has improved.<\/p>\n<p>Mike: That\u2019s a great point to do the baseline testing, and then test again afterward, and then tweak as needed, maybe, share that with the provider as well that the goal to improve this and make sure that they\u2019re bought in, that they\u2019re going to be able to do that so that that way, if it\u2019s off, they can tweak it, and they know what your goal is.<\/p>\n<p>Jack: Right.<\/p>\n<p>Mike: Yeah. Is there, like, a day and time that you typically like to install networks with companies? Like, I know, being in telecom and ISPs over the years, a lot of times they\u2019ll say, like, a Friday at, like, three in the afternoon is usually ideal because it\u2019s not your busiest time of the day \u2013 typically. Obviously, it depends on the company, but they always say, \u201cHey, don\u2019t do it after hours because we don\u2019t have as many people working here at the provider after hours,\u201d or things like that. Are there days and times that you think is typically ideal for companies to make the transition?<\/p>\n<p>Jack: Well, I typically leave it up to the customer based on their comfort level or if they have a change control window that\u2019s from every Wednesday at, you know, 11:00 p.m. or something. However, if they leave it up to me, I usually say let\u2019s do this at 7:00 a.m. at whatever time that they\u2019re up for that branch office. Again, it takes five minutes to route traffic over our solution. And, as customers come in or as clients come in to work and as they\u2019re working, we actually see the traffic, we can monitor things. Now, it\u2019s usually me and the customer, it\u2019s not our support because we all know it\u2019s going to work. We just don\u2019t break things, right?<\/p>\n<p>Mike: Okay.<\/p>\n<p>Jack: If we see certain things that we could tweak, then we\u2019ll let the customer know. A lot of times we\u2019ll go ahead and tweak it during the middle of the day if it doesn\u2019t hurt anything to improve performance for a couple of applications. Again, that\u2019s something else that we, kind of, pride ourselves on. We\u2019re not just providing a service that provides connectivity end to end, we care about the application. If our customers call us and say, \u201cHey, email just doesn\u2019t seem as fast as it should be, but everything else is really working fast,\u201d they can call us and we can help them try to tweak it to make it faster.<\/p>\n<p>Mike: Got it.<\/p>\n<p>Jack: Not a problem.<\/p>\n<p>Mike: That makes sense.<\/p>\n<p>Jack: So, that\u2019s one of the key things about as far as what time to do it. I like it when there\u2019s going to be traffic up there, so we can get something done, and monitor things and look at things, but we\u2019ll do it any time they want to do it.<\/p>\n<p>Mike: Got it. That makes sense. Alright, how about number five?<\/p>\n<p>Jack: The fifth thing is more of to make sure that their comfort level is going to increase once they deploy SD-WAN. They don\u2019t have to do all sites to replace MPLS day one. They can do two or three if they want to. Take their problematic sites and let\u2019s do those first, you know, a data center and two other sites, or something.<\/p>\n<p>So, what\u2019s nice about that is you can piecemeal it. You don\u2019t have to do it all or nothing. Now, when you do that, your comfort level is easily going to grow, like, \u201cWow! This SD-WAN works pretty darn well. And, you know what? Next time around, I\u2019m just going to call this company and we\u2019re just going to do it. We\u2019re just going to cut everything over and then we\u2019ll get rid of MPLS.\u201d<\/p>\n<p>Now, one thing I did forget about one of the previous points is\u2026 Obviously, routing \u2013 when you\u2019re actually doing the routing, it can be with static routes, it can be with dynamic routing, with BGP, some of that stuff you want to get your routing engineer. If you\u2019ve got a very large network, you want to get your routing engineer or one of our solutions architects to really help you out to make sure that you implement that right, because BGP can be, kind of, complex sometimes depending on the customer\u2019s network.<\/p>\n<p>Mike: Got it.<\/p>\n<p>Jack: So, really, what it is, once you get a couple of sites under your belt, the rest of them are just cookie cutter from there \u2013 it\u2019s real simple.<\/p>\n<p>Mike: Awesome. Alright, just to summarize for everybody:<\/p>\n<p>#1: Stay focus on the purpose of your SD-WAN solution.<\/p>\n<p>#2: Understand the different deployment models and which one fits your requirements the best.<\/p>\n<p>#3: Make sure you\u2019re using the most current network diagrams and topologies including routing.<\/p>\n<p>#4: Install and implementation should not break anything. It should do the exact same things that your current network is doing, and making sure that you\u2019re setting some baselines both before and after you install it.<\/p>\n<p>#5: Consider, possibly, piece mealing your installation. So, maybe doing one site at a time as opposed to thinking you have to do it all at once.<\/p>\n<p>So, did I get that right, Jack?<\/p>\n<p>Jack: Yeah, sounds great.<\/p>\n<p>Mike: Awesome. So, what I\u2019d like to do now is have you tell us a little bit about how Aryaka, specifically, would deploy by giving you an example. So, say, a company had around ten or so sites and Office 365 was the cloud service they have that was a big priority. How would Aryaka look at installing that solution?<\/p>\n<p>Jack: Great question. In fact, this is what I do day to day. It\u2019s a lot of fun.<\/p>\n<p>So, let\u2019s say a customer comes to us and they say, \u201cHey, we\u2019re ready to deploy, you know, Aryaka.\u201d First of all, I need to really talk about a couple of really big differentiators between, probably, all of the SD-WAN solutions and Aryaka. First of all, the definition of SD-WAN is the ability to, from a centralized location, push policies, whether it be application performance policies or business policies, down to the edge so that something can be configured from a centralized location and therefore making an impact almost immediately \u2013 that\u2019s the big thing.<\/p>\n<p>So, the way our SD-WAN works is we have a core Layer-2 network. Inside that core Layer-2 network\u2026 It\u2019s not MPLS. MPLS is Layer-3. There\u2019s too many route convergences going on there and that makes your latency loss jump up and down all the time. With us, we have a flat line latency wherever it is. It might be from India back to the United States \u2013 it might be 200 or 300 milliseconds, but it\u2019s a flat 200\/300 milliseconds.<\/p>\n<p>So, the great thing is we, kind of, have an MPLS. Whereas, most SD-WAN providers, what they do is they want an SD-WAN to augment or to enhance their MPLS services, so they\u2019ll keep some traffic on MPLS, but they\u2019ll bring it over to the IPSEC world with the SD-WAN. What we do is we can allow MPLS to run as it is, we bring in SD-WAN, and what we\u2019re doing is we\u2019re bringing in to our own private core which is better than MPLS for a lot of reasons. Number one, again, it\u2019s a Layer-2 core.<\/p>\n<p>Two, we terminate \u2013 we\u2019re a TCP proxy both at our POPs as well as on our appliances on our customer sites. Therefore, we can tune, we can have our own proprietary TCP stack between our appliance and the POP. That allows us to tune our TCP stack so that we can maintain the highest throughput possible. That\u2019s huge. MPLS doesn\u2019t provide this. A lot of SD-WAN appliances don\u2019t apply this. They don\u2019t have this. They can\u2019t do this.<\/p>\n<p>So, that\u2019s just the TCP aspect of it for TCP traffic, but on top of that, we can also do byte caching and compression, a lot like Riverbed or <a href=\"https:\/\/www.silver-peak.com\/\" target=\"_blank\">SilverPeak<\/a>. That\u2019s also included, no extra charges, part of the service. So, you\u2019ve got those two things working for you.<\/p>\n<p>On top of that, we can also do some edge things. The way the customer connects to our POPs is from our ANAT to our POP, you have two IPSEC tunnels. Those IPSEC tunnels, we can send them over to different, diverse paths. This is where path diversity and redundancy is important over the internet. So, if you have two internet links or even one \u2013 and I\u2019ll get in to that in a second \u2013 but if you have two internet, we can send both those tunnels over the two different links just to get it to our closest POP 10-15 milliseconds away. We\u2019re not talking about end to end internet, which is what most SD-WAN providers have to deal with, and the longer you go, the more susceptible you are to loss, jitter, high latency going up and down, that kind of stuff \u2013 we\u2019re keeping it very short.<\/p>\n<p>Mike, do you have voice over IP at home?<\/p>\n<p>Mike: Yes.<\/p>\n<p>Jack: So do I. That\u2019s what we\u2019re talking about. We\u2019re talking about how good is your voice over IP at home. Because the distance that we\u2019re travelling from your site or the customer site to our POP is so minimal, the latency and loss is so small, we can use it all the time and it\u2019s not a problem now.<\/p>\n<p>What if there is a problem though? We\u2019ve got really cool features such as <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"http:\/\/info.aryaka.com\/rs\/477-WNL-836\/images\/smartconnect-wan-optimization-as-a-service-aag.pdf\" target=\"_blank\">Smart Link<\/a><\/span>, which includes path replication. For that important traffic such as voice, why not send it down both paths, the same packet, down both paths at the same time so that the POP, 20 milliseconds away, will take the first good packet and keep it going across our Layer-2 core.<\/p>\n<p>Now, SD-WAN products or solutions, they do the same thing except they do it from, let\u2019s say, LA to New York. LA to New York is 70-80 milliseconds and, depending on what providers you have, you may have to switch from one path to the other. That, actually, can create high levels of jitter and that\u2019s bad for voice. So, you may be trying to solve a voice problem, you could actually be causing other problems with voice by switching paths too often. With us, what we\u2019re simply doing is right there on the edge, 20 milliseconds away. Let\u2019s say one path is 20 milliseconds, the other path is 15, we\u2019re creating a 5 millisecond jitter, any voice buffer can handle that all day long.<\/p>\n<p>Mike: That\u2019s awesome.<\/p>\n<p>Jack: So, we have all these that are both from the edge, from a <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/User_Datagram_Protocol\" target=\"_blank\">UDP<\/a><\/span>, from a video, from a virtual desktop \u2013 these are great for the Smart Link capabilities. That&#8217;s a great application that\u2019s going to prove that. Then, from the TCP side and the data transfer side, we\u2019ve got the byte caching and compression, we\u2019ve got the proprietary TCP stack, the multi-segment architecture (which, by the way, we just received a patent on that) that\u2019s basically breaking up your client to server TCP session in to multiple segments and then controlling each segment individually in order to provide the fastest throughput possible.<\/p>\n<p>So, now let me explain the network. It\u2019s real simple to deploy Aryaka\u2019s solution. Customer, we get their network topology from them, we get IP addresses assigned to our appliance, we ship the appliance, we ship it unconfigured, and we also email them the config file. They take the config file and put it on a USB stick (we ship a USB stick with every appliance), they plug in the USB stick in to their laptop, they put the configuration on there, they pull it up, they put it in to the appliance, and they power it up \u2013 boom \u2013 they\u2019re configured.<\/p>\n<p>Mike: Wow.<\/p>\n<p>Jack: Now, if they\u2019re in-path like a firewall, our tunnels will be up and running. It doesn\u2019t mean we\u2019re routing any traffic over Aryaka, we don\u2019t do that until the customer says to go, you know, they say, \u201cHey, let\u2019s do this,\u201d but the tunnels can be up and running. We might have to wait for another site to come up anyway, right? Because you need at least two sites.<\/p>\n<p>So, we do the same thing at all sites where, literally, we could ship a box out, have it configured, and have it up and running in less than a week. That kills MPLS. Doesn\u2019t matter where in the world, most of the time it\u2019s a week, sometimes, with customs, it\u2019s two to three weeks, but, again, still much faster than MPLS, so we\u2019re more agile by far.<\/p>\n<p>Once we get the tunnels up, at least two locations, it\u2019s simply, \u201cOkay, Mr. Customer. Go ahead and turn on your routing.\u201d They route traffic over Aryaka simultaneously at both sites because we do the WAN optimization \u2013 in some cases, we definitely had the TCP acceleration, TCP proxy \u2013 and what happens is we are accelerating that traffic day one. Most of the time, customers don\u2019t have to do a thing after that at all.<\/p>\n<p>Now, when we route, again, this is where part of our job is: Is it going to be BGP? Is it going to be RIPv 2? Is it going to be static routes? So on and so forth.<\/p>\n<p>So, we\u2019re routing traffic, off it goes. If customers have SSL sites in their data center, they can load their private key and certificate up to our secure vault. It automatically gets distributed to our POPs and our appliances. That way, we can be that authorized man-in-the-middle to see that raw data, so that we can apply byte caching and compression, and make that so much faster than normal \u2013 think Sharepoint, right? Something like that.<\/p>\n<p>Mike: Right.<\/p>\n<p>Jack: Same thing with, let\u2019s say, cloud service. I mean, yeah, they can have access to it over the internet, but let\u2019s say you have a cloud service, Salesforce.com, sitting at Chicago \u2013 that\u2019s where the data resides. If you want to take your Singapore office, and your Singapore branch office needed to get to that data constantly every day, then what we can do is we can say, \u201cHey, for those routes going to Salesforce, your next hop is now Aryaka, through our appliance.\u201d We route the traffic all the way to Salesforce.com. It comes out of our Chicago POP, which, by the way, just like most SAS offerings, they\u2019re in the same building we are. We\u2019re just a few racks down. So, we NAT outbound, that forces to come back to us, okay, right there two milliseconds away, and then we bypass the internet completely to get it to their branch office in Singapore.<\/p>\n<p>Mike: Got it.<\/p>\n<p>Jack: So, this is how we can improve any, you know, any SAS offering anywhere on the internet. It doesn\u2019t matter where they are, we can improve performance for any SAS offerings. Whereas, MPLS &#8211; How do you get MPLS in to that service? They\u2019ve got to bring in one link for every single customer that might be in there, right? So, it, kind of, gives you an idea of how flexible we are and how quickly we can deploy.<\/p>\n<p>Once they bring up routing, you know, basically, you\u2019re done. Here\u2019s one of the great thinsg about Aryaka, we\u2019re proactive with support. We will tell the customer, \u201cHey, your latency just went up by 40 milliseconds,\u201d and usually within five minutes, or \u201cHey, your loss just jumped from none to 5%.\u201d We\u2019re going to let you know almost immediately. Also, if you want, for a small fee, we can be authorized to call your ISPs, so that way you don\u2019t have to call them. That way, we\u2019re not just notifying you, we are fixing it, we\u2019re getting it worked on if it\u2019s, you know, an ISP problem. Obviously, if it\u2019s within our core, which rarely, rarely happens, we\u2019re already working on it. We\u2019re getting it fixed. By the way, it\u2019s redundant core, you know, where we can switch from link to another link in usually less than a minute or less than a second in some cases.<\/p>\n<p>Mike: That\u2019s awesome.<\/p>\n<p>Jack: Yup.<\/p>\n<p>Mike: Yeah.<\/p>\n<p>Jack: So, it\u2019s more of a managed service. Our solution is a managed SD-WAN solution, whereas other solutions are \u201cHere\u2019s your box. Good luck. We\u2019ve got training if you want to go to it.\u201d It\u2019s like the Riverbed approach, which is not a bad thing. I mean, they\u2019ve got a pretty good box there for what they do, but if you want the combination of Riverbed, plus Talari, plus MPLS, or whatever, better MPLS core, that\u2019s who Aryaka is. In fact, I always like to say, the other SD-WAN providers, they want what we have, which is a core. What they typically rely on is MPLS as their good core and then they want to be able to use what\u2019s available, what the internet is good at, right?<\/p>\n<p>Mike: Right. Now, one thing I definitely wanted to bring up with you is I heard through the grapevine that Aryaka sometimes offers a free proof-of-concept. So, can you, kind of, clear up that \u201csometimes\u201d for us and tell the listeners what\u2019s involved with that? Because every IT department out there love to try stuff for free, but buying something without ever testing it is always a little bit scary, so can you fill us in on the \u201csometimes\u201d there?<\/p>\n<p>Jack: Yup. Absolutely. So, first of all, we\u2019re the only service provider that I know of that would allow customers to have a proof-of-concept. Now, it is free, but there has to be specific criteria that\u2019s met.<\/p>\n<p>Mike: Okay.<\/p>\n<p>Jack: One of the criteria is that they have to have something fixed. There has to be an application that\u2019s not doing well that we believe, based on our technology, that we can fix.<\/p>\n<p>Mike: Okay.<\/p>\n<p>Jack: Such as file transfers are just dog slow. They take three hours \u2013 something like that. If they\u2019re using Windows file sharing, we can probably turn that down to, instead of three hours, probably fifteen minutes. For that same file, instead of taking three hours, we bring it down to fifteen minutes, making the users more productive \u2013 so, something like that.<\/p>\n<p>Or, we have a call center that is trying to use the internet and is realizing, boy this is not a good idea to use the internet. It\u2019s just not as stable as it should be specially if it\u2019s some place, like, out of, I don\u2019t know, Mexico or something \u2013 that\u2019s where their call center is. So, they need a way to make their voice calls better. So, that\u2019s where we would say, \u201cWell, if we implement Smart Link and path replication between two paths. We\u2019re sending both packets down both paths, the probability of both those paths losing that packet goes from \u2013 let\u2019s say, it\u2019s 1% loss on both paths \u2013 it goes from 1% to 0.01%. There\u2019s your four nines\u201d Okay?<\/p>\n<p>Mike: Yeah.<\/p>\n<p>Jack: So, these are the things that we know we can fix. Great use cases where \u2013 You know what? If we slap this in, if we bring this up as a <span style=\"color: #ff6600;\"><a style=\"color: #ff6600;\" href=\"https:\/\/en.wikipedia.org\/wiki\/Proof_of_concept\" target=\"_blank\">POC<\/a><\/span>, you\u2019re obviously going to buy, right?<\/p>\n<p>Mike: Right.<\/p>\n<p>Jack: So, the second criteria is that when we\u2019re done, we\u2019re expecting them to sign on and become a customer right then and there. Okay?<\/p>\n<p>Mike: Okay, got it.<\/p>\n<p>Jack: So, now, we do offer paid POCs, not a problem, if they want to bring one for a month. If they want to do just functionality testing and make sure we don\u2019t break anything, which we know we don\u2019t, we\u2019re open to that. That\u2019s not a problem. Okay.<\/p>\n<p>Mike: Got it. Are there any limitations to the proof of concept? Is it just two sites or is it their whole network?<\/p>\n<p>Jack: Yeah, great question. Two sites. We like to do 2Mbps. We can go up to 10Mbs for the two sites. We can add a third so long as it\u2019s a cloud service. So, let\u2019s say Office 365 or, you know, something out there, right? An ERP application that\u2019s hosted in the cloud. So, we can bring up a third in that case.<\/p>\n<p>What we also do is there\u2019s a time limit from the moment\u2026 Now, remember it takes about, maybe, a week to get us up and running. Once the customer throws traffic on our network, the customer gets ten working days to test it out. Because, remember, before our equipment arrives, we expect that baseline testing be done, then traffic is thrown on to Aryaka, and then they retest, and they\u2019re done. I mean, in reality, they need three days, but we will give them up to two weeks. At the end of two weeks, if we meet their success criteria, what they\u2019re expecting, they\u2019re a customer \u2013 and we\u2019re looking forward to that.<\/p>\n<p>So, one thing as far as our POC that we\u2019re not, and this is, kind of, important \u2013 I know that people get to evaluate equipment from everywhere, from all these different vendors. We\u2019re not just a vendor. We actually provision our core for the customer, actually using and spending our own money for their POC. So, while it\u2019s free for them, it\u2019s not free for us, which is why we limit the time. So, we appreciate those that definitely we\u2019re getting this done in two weeks and we definitely get it done in two weeks. Okay?<\/p>\n<p>Mike: That makes sense. I think that\u2019s fair. It\u2019s like you hear \u201cfree proof of concept,\u201d your first thought is \u201cawesome,\u201d but then, obviously, there are going to be some stipulations in there. You guys can\u2019t deploy a fifty-location network for free.<\/p>\n<p>Jack: Exactly.<\/p>\n<p>Mike: Yeah, for an unlimited amount of time. I think that\u2019s awesome. I think that, hey, not a lot of providers do that. I\u2019m not used to providers ever offering any type of free trial or anything like that. So, that\u2019s great. I think you guys are breaking some new ground there, and I think that\u2019s very valuable to anybody listening to know that they can try it a little bit, you know, dip their toe in the water to make sure it works as they thought it would. So, that\u2019s awesome.<\/p>\n<p>Well, great. I think that wraps it up. Thanks for joining us, Jack. I really appreciate you taking the time, and that were some really valuable information on SD-WAN that I think our listeners would definitely benefit from. Thanks, again.<\/p>\n<p>Jack: Thank you, Mike. It\u2019s been a real pleasure. Thanks a lot.<\/p>\n<p>Mike: Man, Jack really knows his stuff, doesn\u2019t he? It\u2019s great to talk to somebody who\u2019s working for a company who\u2019s been doing SD-WAN for a long time since that\u2019s, kind of, such a new buzzword. A lot of companies are just now rolling out an SD-WAN product, so it\u2019s cool to talk to someone who works for a company that\u2019s been doing it for a long time. So, I really appreciate him coming on the show and I hope you enjoyed it as much as I did.<\/p>\n<p>Just one more, quick reminder: If you wanted to get the free SD-WAN comparison chart comparing SD-WAN to MPLS, point-to-point, and IPSEC VPN, comparing all the different capabilities of each, different technology, just text the word \u201cWANGUIDE\u201d to the number 44-222. Again, just text the word \u201cWANGUIDE\u201d to 44-222 and receive a free softcopy cheat sheet of our WAN comparison chart comparing SD-WAN to all the other WAN technologies.<\/p>\n<p>So, that\u2019s it. Have a great day and catch you next time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; &nbsp; So you&#8217;ve decided to move to SD-WAN. What should your IT department do to make sure you have a smooth installation? To answer these questions, we invited an expert SD-WAN engineer, Jack Dolan from Aryaka Networks, to speak<span class=\"ellipsis\">&hellip;<\/span> <a href=\"https:\/\/www.aerocominc.com\/info\/cloud-therapy-ep-003-5-ways-to-prepare-for-an-sdwan-install\/\"><\/p>\n<div class=\"read-more\">Read more &#8250;<\/div>\n<p><!-- end of .read-more --><\/a><\/p>\n","protected":false},"author":6,"featured_media":9486,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_mi_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[371],"tags":[266,268,270,704,542,707,422,429,615,700,681,561,703,478,176,428,367,433,430,479,423,709,480,708,370,706,476,693,705,711,710,272],"_links":{"self":[{"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/posts\/9485"}],"collection":[{"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/comments?post=9485"}],"version-history":[{"count":0,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/posts\/9485\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/media\/9486"}],"wp:attachment":[{"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/media?parent=9485"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/categories?post=9485"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aerocominc.com\/info\/wp-json\/wp\/v2\/tags?post=9485"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}