Viptela is now part of Cisco.

Analyst Keynote

Research Insights on the Next Generation WAN (EMA Research)

ema logoJoin Analyst Shamus McGillicuddy (EMA Research) as he provides insight from the research of 200 networking professionals into how enterprises are utilizing Software-Defined WAN (SD-WAN) and transforming their business connectivity.

Going in detail on the survey results, Shamus will walk you through the key trends in SDN and SD-WAN across major enterprises. These include the major application performance issues, operational challenges, cloud migration hurdles and reasons for rapid SD-WAN adoption.

Some of the key discussion topics will include:

  • What percentage are transitioning from MPLS to Hybrid, and why?
  • How pervasive is 4G/LTE in the WAN?
  • How Cloud migration affects WAN infrastructure teams?
  • What are the major drivers for NFV services?
  • How important is WAN optimization?
  • What are the characteristics of major organizations deploying SD-WAN?
  • What are the major tools to monitor and manage SD-WAN?

Preview of some of the results:

  • 96% of enterprises say they use wireless as the primary network connectivity in at least some of their sites (4G/LTE is the most common wireless technology, followed by carrier/municipal Wi-Fi)
  • Only 52% of enterprises monitor their WAN provider’s service-level agreements (SLAs)
  • 30% say their service providers have violated an SLA in the past year

The wide area network (WAN) is the essential infrastructure component to driving global communication, collaboration and data access across enterprise networks. Enterprises have been deploying traditional architectures but with increased cloud adoption and high bandwidth demands, a new architecture of connectivity is needed. IT organizations across the globe have begun adopting SD-WAN to address their new connectivity requirements.

Download Slides Here

Presenter

Shamus McGillicuddy EMA photo
Shamus McGillicuddy Senior Analyst, EMA Research

Shamus has more than nine years of experience in the IT industry, primarily as a journalist covering the network infrastructure market. At Enterprise Management Associates (EMA), he is the senior analyst for the network management practice.

Transcript

Analyst Keynote: Research Insights on the Next Generation WAN (EMA Research)

Interviewer: Hello. Good morning or good afternoon, depending where in the world you are today. Welcome to 2017. I’m Rob McBride. I’ll be your host for today’s webinar.

It’s an exciting week of webinars that we’re hosting here at Viptela for the future WAN Virtual Summit and SD WAN Focus Summit also focus on customer stories, analyst research, as well as some deployment and case studies.

Today we have an exciting session. I’m proud to announce and introduce Mr. Shamus McGillicuddy, a senior analyst and researcher over at EMA. Today’s session will be focused on providing all of you in the audience some really deep insights based off of Shamus’ research focused on Next Generation WAN technology.

And a couple of housekeeping items for all of you:  We like to keep this an interactive session, so, please, ask as many questions throughout. We’ll be taking and answering questions toward the end of today’s webinar and if we are unable to actually answer all questions this webinar is being recorded and we’ll reach out to you offline and provide answers to those questions that we were unable to be taken.

And with that, Shamus, I’d like to hand it off to you.

Shamus: Thanks, Rob. As Rob mentioned my name is Shamus McGillicuddy and the title of today’s presentation I’m delivering is Next Generation WAN Research Insights.

As Rob mentioned I’m the Senior Analyst for networking management and networking structure research at Enterprise Management Associates. And you see my email address and my Twitter handle there if you need to – if you’re interested in following up with me after the presentation.

So thank you for joining and with that said I’m going to go right into it. Now, the agenda for my presentation today – I’m going to start with a little background on the research that I’ll be citing in most of my presentation and then I’ll move into drivers for why Enterprises look for a new wide area network or a new approach to wide area networking.

Then I will look at some things you should consider when planning your wide-area network – your Future WAN, so to speak. And finally we’ll look at software-defined WAN. We surveyed some early adopters of the technology around some key requirements, benefits they’re looking to gain from the technology – things like that. So we’ll review some data on that subject.

So first the background on the research. We published this in August, Next Generation Wide Area Networking. It was a research report that was focused on examining Enterprise WAN trends and best practices. It was a broad piece of research. It looked at software-defined WAN, but it also looked at topics like Enterprise relationship with service providers, how they validate service-level agreements and things like that – organizational change, how the Cloud impacts architecture – things like that.

Like I said, it was published in August. We surveyed 200 IT pros who were specifically involved in some aspect of WAN planning, WAN engineering, operations. They’re usually involved in multiple aspects of their WAN. And roughly about half of them were IT staff-level people and another half were in management-level positions. 74% of them were based in North America and just over a quarter were based in Europe.

And we also specifically surveyed organizations that had more than 10 sites connected to a Wide Area Network just so that we could make sure that we were talking to actually – distributed enterprises. So that’s the research.

Then going into drivers for a new WAN. First let’s look at what yesterday’s wide area networks is all about, traditional WAN infrastructure and architecture it’s typically dominated by managed WAN services, like MPLS. Internet is usually used as a backup connection in case the managed WAN services go down.

The infrastructure is typically static. If you’re going to connect a new site it’s going to take you weeks, if not months, to get it up and running. Sometimes if you need a bandwidth upgrade it’s going to take a similar amount of time. High availability and high performance for instance, for that matter, trump high bandwidth and the cost per bit for these managed connections are very high. What you’re paying for is service-level agreements, then security and knowing that the network is probably going to be highly available and perform well, but you’re not getting a lot of bandwidth, which can be a problem if you’re using bandwidth intensive applications.

It’s architected to connect users to private data centers, that is users in branch offices and campus networks and enterprise networks connecting to applications that are hosted in a private data center or more than one private data center and there’s typically no direct web access. A lot of web traffic is backhauled from remote site to a data center or regional hub for security purposes and policy application.

The new WAN and the drivers for it begin with the Cloud. Enterprises are migrating applications to the public Cloud. They are connecting remote sites to software as a service and infrastructure as a service via the internet and back hauling that access to the Cloud through a data center, like traditional web access, go to degrade performance is going to lead to latency and dropped packets.

And incidentally other research that we did earlier last year found that 44% of all traffic on the network is attributable to external cloud services, like SaaS and infrastructure as a service, so this is a big area of change for enterprises.

So in our research we found that 55 percent of enterprises now prefer to directly connect the remote sites to Cloud services rather than routing them through a data center for security and screening and so forth.

Now, there are some inhibitors, as you can see on the right in this chart. Security operations, really, is opposed to this for a lot of companies. Also, the security architecture is centralized and doesn’t enable the freedom to connect with remote sites directly and and since all the security is applied in a central data center quite often.

Core network services are also centralized and as we mentioned internet connectivity is backhauled to the data center regional hub. So those are issues that really impede this movement and something like software-defined WAN can help with that.

Another big driver for change in the WAN is just growth. We’re seeing multiple dimensions of growth demanding a new wired area network. First of all, when you look at the chart on the right, we found that a lot of enterprises are adding additional WAN connectivity at remote sides, both in the form of MPLS and in internet connectivity. And those that were doing that we asked them what the drivers were. Business growth that was organic, that is not caused by mergers and acquisitions, was the number one driver of that additional network connectivity. And M&A, merger and acquisition driven growth, was also a driver, as was just the need for improvement or resiliency and availability.

So growth is demanding change in the WAN, whether that is business growth that is demanding change in the WAN. Also, 82 percent of enterprises told us that they’re connecting more remote sites to their networks this year. Slightly less than a quarter said that they were seeing over 25 percent growth in the number of remote sites connecting to their WAN, so that’s significant. And that’s a lot of sites coming on online and that adds a lot of complexity. Also, if static infrastructure is not going to be very responsive to that kind of growth.

And finally 84 percent of enterprises told us that they’re growing the number of network-connected end-point devices that are connecting through their remote sites and number one on the source of that growth was PCs and laptops, but number two is the Internet of Things, which is another thing you need to consider as you’re getting a new WAN up and going.

Now, we talked about growth in the Cloud. One thing that I think is also driving a new WAN is just the limited resources that IT organizations are dealing with. And here you see we asked enterprises to tell us what their top challenges were to success with WAN engineering and operations and the top three were lack of necessary skills and knowledge and rising costs and lack of budget. You need to technologies that can help you address these issues and also don’t forget number two, here, problems traceable to network, hardware and software vendor, so make sure you’re selecting quality solutions when you’re doing this change.

And then one last driver change is rising security risk. With all this growth, with all these new devices connecting to the WAN, with all this adoption of Cloud, you know, you’re expanding your tech surface and we’ve been hearing for years that the perimeter defense is just not working for people anymore. Your WAN is going to be more distributed, you’re going to be connecting more devices and individual sites, you’re going to be connecting to Cloud services. You’re stretching your IT resources then, so you really need a technology that enables a new security architecture.

So planning your future WAN – here’s some considerations to keep in mind:  First of all, the next generation wide area network architecture should be characterized by these four things: They should be Cloud-ready, which means remote sites are connecting directly to the Cloud via the internet, offering MPLS connectivity to internal apps where needed will also need to continue to be in place. We’ll talk about this in the future, but we don’t think MPLS is going away just because it’s more internet needed for the Cloud.

Then future WAN should also be dynamic. It should be able to rapidly connect new sites to address all that growth. It should be easy to expand bandwidth when needed, you know, applications like video and big data and IoT come into play. It should be simple to use so that when you are dealing with limited resources you can manage and operate this network appropriately which means centralized management, maybe some automation and think about that intent-based networking, business and application policy rather than device-by-device CLI where you’re relying on highly skilled engineers to really build out your network device by device based on their advanced skills that might be better used elsewhere, such as optimization and so forth.

And then the WAN should obviously be secure. We talked the expanded attack service, so architects must be able to layer security onto this new infrastructure, wherever it’s needed and a lot of that’s going to be enabled by things like SD-WAN and network function virtualization and Cloud-based services.

So hybrid connectivity we believe is going to be essential here. There’s a lot of hype out there that the internet is going to replace MPLS and managed WAN services in general, but the reality is that internet is actually complementing and supplementing MPLS. It’s not replacing it. We asked enterprises who are adding more internet connectivity what are you doing with it. Are you replacing MPLS with that internet connectivity and 74 percent of them said yes, but that changed over from internet to MPLS for primary connections. It’s only going to affect 45 percent of their sites, which means that MPLS is here to stay.

Enterprises have very specific forwarding preferences for different types of applications and that’s really going to drive the persistence of hybrid WANs rather than, you know, a changeover from MPLS to the internet. Enterprises have told us in our research that when it comes to storage replication and restoration traffic, big data collection and analytics and ERP traffic, that’s ERP systems that are deployed internally in a data center rather than a Cloud-based ERP service, they want to forward that traffic over MPLS, but they’ve identified the internet as ideal for secure enterprise web application, that’s applications based upon https and also, in some cases, Cloud applications if they’re connecting remote sites directly the cloud they’re going to forward those Cloud applications over the internet.

So, but imagine a lot of these remote sites are going to have a mix of connectivity needs. Imagine like a research and development site, for instance. Enterprises tell us that R&D sites are number two on the list of most important types of connected remote sites on their WAN behind your generic branch office with information workers.

So those R&D sites they might produce a lot of large files using the CAD technologies and research systems and those files need to be backed up offsite more often than not and the replication of those files is going to go over MPLS. Now, that same site might also have R&D engineers and researchers collaborating with partners, with other remote sites on your network and they’re going to be using perhaps web-based applications that use https and you might want to forward that traffic over the internet, so you’re going to need a technology and an architecture in place that’s smart enough to know which applications go on which type of transport, but also as network conditions change, for instance, MPLS degrades and you’d really need to get some traffic that usually going over MPLS to wherever it’s going you might need a technology that can intelligently route that traffic over to the internet, but also do it in such a way that other applications that typically rely on the internet are not negatively impacted to the extent that they no longer work. So for instance a backup of a CAD file is going over the internet suddenly. It needs to be constrained in such a way that all the collaboration technologies that the workers in that site are using do not get interrupted.

Moving on, when we asked these enterprises that were replacing MPLS with the internet what the drivers were we got an unexpected result. I’ve put this in there thinking it would be at the bottom of the list, but it’s actually at the top. They thought that the internet would make them more secure. Now, does that mean that the public internet is more secure than private connections and MPLS? No. It does not. But I think what we’re seeing here is that some enterprises recognize the use of the internet as an opportunity to improve overall security hygiene. They’re going to encrypt that traffic over the internet by default, which just puts them in a better position.

You know, in the past they may have relied on MPLS as being inherently secure, when we know that even a tier-one service provider can be vulnerable to a hack sometime and if you’re not securing the traffic you’re sending over MPLS and that tier-one provider gets compromised then your traffic then your data might be compromised as well, so just relying on a more secure posture toward, you know, encryption and so forth that just leads to a trickle down effect and maybe that’s one of the drivers here, but it’s also worth noting that the internet also enables easier access to Cloud-based security services. I know that Zscaler is a part of the summit this week and, you know, being able to connect to them more easily and in other security services it’s going to allow you to have flexible granular security without relying on appliances in your remote sites.

So that’s another thing that can drive this. The other big drivers here for internet replacing MPLS… connectivity of Cloud services we’ve covered exhaustively already. You can see why that’s there. Superior performance is also kind of an unexpected result. I’m pretty sure that it’s driven by the fact that a lot of remote sites might be in geographies where managed WAN service infrastructure is ageing. Maybe you have a decade old T1 line available to you, but a newer broadband network that’s only two or three years old is just performing better, even if it is the internet. It’s the best connection available to you there. Maybe you’re using wireless internet as well, which is higher performing than anything you’ve gotten in that isolated region, for instance.

And then also higher bandwidth options and service agilities just kind of speak for themselves based on what we’ve been talking about already. We also think that another big thing to consider here is consolidation of infrastructure. There’s strong interest in network functions virtualization in remote sites. It enables flexibility, elasticity. It’s gonna eliminate things like truck rolls. It’s going to enable zero IT in the branch.

You see this green bar is the preference – we asked enterprises what’s your preference for consuming these various network functions – VPN, WANOP, network address translation, network security routing. The green bar shows a preference for virtual network functions deployed on off the shelf servers or on a multifunction network appliance and you see really strong preferences here for VPN, WANOP and network address translation being deployed as software services on a multifunction box of some kind or server in your branch. It replaces dedicated appliances in your remote sites that might be more expensive, static and require IT people to visit the site in order to make any changes.

This is sort of pointing towards a post-appliance world where you can add network and security services on the fly in the form of software. You see, even routing there’s pretty strong interest in routing at the top there as a virtual network function, but also, obviously, with the blue bar there there’s still a lot of reluctance from a significant number of enterprises to take routing into software, but it’s there. And then the orange bar represents those who prefer Cloud-based services and there you see network security and that’s where people are really interested, as I mentioned early network security delivered through the Cloud is of strong interest.

We’re going to see WAN architecture that leans on virtual network functions, but also Cloud-based services where it’s appropriate, explained in network security and I think that’s something that can be enabled by software-defined WAN.

So moving into key requirements for software-defined WAN we see here we asked early adopters what does software-defined WAN mean you?  Please select the defining capabilities of the technology that are most important to you in the solutions that you deploy. These three climbed to the top:  Centrally programmable network, Cloud-based and virtual network functioning services and dynamic hybrid WAN connection with past selection based on policies and network condition.

So software-defined WAN, we see this as a platform at EMA to enable a dynamic Cloud-ready security network – all the thing I’ve been talking about already, but most important and something we haven’t necessary talked about in-depth here is enterprises recognized software-defined WAN as an opportunity to improve application performance.

And here you see this chart. Business drivers for the adoption of the technology. Improved application performance was at the very top of the list. Number two was direct access to Cloud services, which we’ve been covering, essentially, through this session. Also, improved network security – they saw that as an opportunity. And then reducing operational costs associated with the network and rapid inflexible deliver network services and connectivity. Those are the top five.

When you slice this data by the status of IT budgets we found that organizations that have either flat or shrinking IT budgets had a much more narrow focus here. Their number one driver for SD-WAN adoption was direct Cloud access and then after that it was reducing infrastructure costs, so they weren’t really focused on improving application performance or improving network security. And I think that’s a potential lost opportunity for them, in fact I’m quite certain it is.

I think that if you are in an organization that has limited budget resources available and you’re looking to invest in SD-WAN really make sure that you’re not leaving anything undone and look for the opportunities to really transform your business by being able to improve application performance over a distributed enterprise and also don’t miss out on the opportunity to improve network security.

And then incidentally you look at the bottom of the list here. Software-defined WAN was the best option for network resets. I put that in there just to see if there are people out there that didn’t necessarily see the business drivers for the technology – you know, they’re just being sold on technology for the sake of technology and you see 30 percent of them were doing it for that reason and that’s a warning sign.

We also saw that IT management-level respondents were much more likely to select that as a reason and then staff-level people who work much more closely with the technology and can possibly understand it better or understand the potential of it better were much less likely to select that as an option, so there’s that to keep in mind.

We also asked them what were the most important features in their SD-WAN solutions and these early adopters really look at device consolidation as a huge driver here. Cloud-based services and network functions and virtual network functions are number one and number two.

Improved network and application visibility was number three and that’s important to keep in mind if they’re being driven by the need to improve or the desire to improve application performance then visibility is going to help them validate that and maintain that improvement.

And then number four was dynamic hybrid WAN connectivity, which we’ve been discussing essentially so far. I put in this one here, the red bar here – I put this in here as another check on what’s happening in the market. WAN-linked load balancing or link bonding or static hybrid connectivity or whatever you want to call it… active connectivity. I believe this is a legacy technology that’s being oversold as SD-WAN. You see, this is an indication that a quarter of early adopters are being misled on their solutions and they don’t understand the value of a dynamic hybrid WAN solution that can help them make intelligent forwarding decision from all the remote sites.

It’s a warning sign to keep in mind when you’re talking to potential vendors to make sure that you’re not engaging with vendors that aren’t necessarily delivering the full potential of SD-WAN in their current solutions. I’m not accusing anyone of doing that, but there is some indication here that that might be happening, so just keep that in mind.

And then we also asked early adopters what management concerns do you have going into your use of this technology and number one on their list was management of all of those virtual WAN elements – those virtual network functions. This is actually a bigger concerns for organizations that were still in the planning and design stage. 62 percent of them listed that as a top concern, but still even those that had completed a deployment – 35 percent of those who’ve completed the deployment said they were concerned about this, so it is an issue, just not as big an issue as maybe it looks like here.

But so make sure that you have end-to-end tools for monitoring and troubleshooting, both the hardware that hosts your virtual network functions and the software that delivers that functionality and also keep in mind the Cloud-based services in being able to get this done just so that when you do have a problem with a virtual network function, like a WAN optimization software or routing software that you can tell where the problem is coming from – is the server that’s hosting the function, is it the software itself or it something else.

Number two on this list, managing multiple service providers who transport virtualization that’s hybrid WAN connectivity. They’re concerned that when the connectivity is abstracted they might not be able to maintain visibility into individual provider networks, so make sure that you have the tools in place to be able to differentiate which service providers are performing at which levels.

You know, a lot of times with this SD-WAN technology if one of the service providers at a remote site goes down the SD-WAN solution is going to route around that and make sure all your traffic is going over another link. And you probably won’t get any complaints from users and you might not get a red alert from your monitoring systems, but if that problem persists and then the other links go down then you’re really in trouble. So you want tools that can help you address problems as they come up, even they’re not immediately impacting application performance.

Number three here was the need for onsite IT staff to manage new infrastructure, so make sure that when you are deploying software-defined WAN it does not put any extra burden on you and force you to send IT people to remote sites on a regular basis. You want to have central management, central control. You want to be able to deploy Cloud-based services, virtual network functions through software, through central management consoles wherever possible.

And then number four on this list, integrating management with legacy and third-party infrastructure. As I mentioned, they’re only deploying SD-WAN in roughly 41 to 60 percent of their sites, so that means like another half of sites are going to continue to have legacy architecture in place. You don’t want to be able to have end-to-end visibility integrated and management across those sites, so if you have one sites that an SD-WAN-enabled and another site that’s using legacy technology and they’re trying to communicate with each other and having trouble you don’t want to have to use two sets of tools to figure out what the problem is. It’d be really nice if you could just use one and sort of streamline the workflows and reduce any complex data correlation you might have to do in the process of figuring out what’s wrong.

So a best practice would be to establish end-to-end network operations capabilities across legacy and SD-WAN infrastructure. And you might want to ask your tool vendors and your SD-WAN vendors to help you with that. So think about it, you know, in the planning stage.

So in conclusion enterprises we feel need a new WAN. It should be dynamic, Cloud-ready, easy to operate and secure. The WAN of the future will be featuring hybrid connectivity and it will consolidate infrastructure via the Cloud and through virtual network functions and software-defined WAN is one of the platforms, if not the platform, for building that WAN of the future. It addresses a lot of the drivers for a new WAN and ultimately improves application performance, so keep that in mind – improved application performance is an opportunity for you.

Now a lot of the results that I talked about here and many more data points and analysis are available and free to download. A research summary of the Next Generation Wide Area Network research, which can be found at the link here on the Viptela site, so write that down if you’re interested in it and it will probably be made available to you in other follow-up communications, so if you don’t get a chance to do that right now don’t worry about it and with that I’m going to turn it over back to Rob for Q&A, but also he might want to tell you about some of the other sessions going on with FutureWAN today and this week.

Interviewer: Thanks Shamus, that’s was awesome. We do have a couple of questions from the audience and as a reminder to everybody, you know, keep queueing them. We do have a little bit of time to kind of answer them.

I’ll repeat this later on after we get through the Q&A, but, you know, this is an exciting week. We have SD-WAN virtual summit called FutureWAN 2017. There’s a number of exciting education sessions that I encourage everyone here attending to go and take a look at the summit web page and take a look at a variety of different other sessions. We’ve listed a couple of them that might be of interest to our audience here, some focus on security, from Zscaler, Voice of the Enterprise sessions, focused on the transformation of specific Enterprises customers, as well as a demonstration for folks to take advantage of.

So as we let a few more questions queue up here, Shamus, I’m going to go off a couple that we already have.

The first one I want to ask is – you know, an audience member asked:  I see a lot of monitoring vendors announcing partnerships with SD-WAN vendors.

You have any understanding as to why is that?

Shamus: Well, a lot of it is validation that the monitoring tool vendors can work with a specific SD-WAN’s infrastructure. A lot of software-defined WAN vendors offer APIs for direct access to various points of the telemetry and device metrics and so forth in their overall solutions, so a lot of monitoring vendors will integrate with that API and then validate that integration through a formal partnership, so I think that’s one of the big drivers there.

It’s probably going to vary from tool vendor to tool vendor and from SD-WAN vendor to SD-WAN vendor. Some monitoring tool vendors are really good at collecting data from new sources and others maybe require some modification, so you’ll see some variation through the market, but I think the big thing is, you know, we see a lot of monitoring vendors – or we see a lot infrastructure vendors offering APIs. Going forward, I mean, all kinds of things from routing and switching to two or more system-based solutions, like SDN and SD-WAN and the ability for monitoring, then, is to pull the data through those APIs can really be valuable to network operations.

Interviewer: Awesome. Thank you. Here’s another one. This one is really about VNS. I’m going to paraphrase a little bit from what’s listed here, but do you see the preferences for VNS-based consumption of services to be thick or thin-based?

Shamus: Well, we haven’t done a lot of research on that specifically, so I don’t think I’ll be able to answer that question with a lot of confidence. I’m sorry about that.

Interviewer: Yeah. No problem. What about wireless connectivity. Are people using that to replace MPLS?

Shamus: In some cases. We found that 96 percent of enterprises are using wireless as a primary form of network connectivity in some of the remote sites. I think it’s really specific to certain situations and also the biggest type of wireless connectivity their using is 4G LTE – 84 percent of them said they were doing that. A lot were also using municipal Wi-Fi or carrier Wi-Fi. I think about half are doing that, but I think those that are using wireless are doing it for reasons such as, you know, being able to get better performance when wired options are really poor performing or low band width.

I’ve talked to some enterprises who when they’re growing really fast, even getting broadband connections not fast enough for them, and so what they’ll do is they’ll shit a 4G router to a new site that needs to get up and running quickly and provide the network services and connectivity through that 4G router until a wired option gets up and running for them.

So I think wireless is continuing to be a good option and as you get more interested in IoT, for instance, wireless becomes essential if you’ve got a lot of devices that are connecting from really remote, isolated areas.

Interviewer: Okay. You know, actually, you know, we have an interesting question here. You were mentioning about IoT. So what kinds of IoT devices are people connecting in their remote sites?

Shamus: With IoT in remote sites the number one type of device we saw in this survey was physical security controls and surveillance cameras and things like that. We also saw a lot of connectivity for customer service things, technologies like digital signage, virtual kiosks and things like that. And we saw smart building systems also topping the list – heating, power management – things like that, so those were all that seemed to be the low-hanging fruit right now for IoT and the remote site.

Interviewer: We have a few more questions and we’ll probably maybe take two or three more here.

So do you see most managed services on the market today as end point services only or are the providers also controlling and routing traffic in the backbone based on NFV?

Shamus: Okay. Trying to understand what they’re trying to get at with that question. I think what they’re saying is it only – is NFV only in the customer premise equipment or is it also in service provider backbones. I think that’s what they’re asking?

Interviewer: I believe, it might be pseudo-related to the other one, which is, you know, in some respects, you know, managed services that they own on the end-point side, but also some more thick or thin-based services they might be actually controlling, too, as well, I think it’s that.

Shamus: Yeah. I mean, you know, we did some research about a year ago. I think there’s a lot of use of NFV providers controlling and routing traffic in, you know, using NFV and not just the backbone, but I think it’s mostly end point right now. I think that’s really the early target for this type of technology.

I mean, backbone infrastructure and things like that I think that’s still – I don’t think that’s quite mature yet.

Interviewer: Fair enough. Got another one that’s popped in that’s pretty interesting – a little bit techy here: Are VC wireless connections using SSL better than using, for example, 3DES to kind to get some clarification on that from the audience member. Seems like many of the end-point providers do not support SSL, but only 3DES.

Shamus: That’s another thing where I haven’t really looked into that. You know, my research into wireless connectivity was pretty shallow and I haven’t really talked to the market very extensively on, you know, SSL versus 3DES, so I couldn’t really answer that with any precision unfortunately.

Interviewer: So that’s the end of our questions right now. We have a few in here, but our time is running out, so, you know, Shamus thank you very much for your time today. You provided a number of different great insights as far as, you know, Next Generation WAN and architecture and some, you know, rationales as to why people are adopting software-defined WAN or thinking about and obviously some considerations that enterprises need to think about as they migrate.

For our audience here I’d like to kind of provide some reminders, as well as thank you all for attending our session today. This was part of FutureWAN 2017, which is an SD-WAN virtual summit going on all week.

As you see on the screen there there is a link that will provide you to our registration page, as well as give you a list of all the sessions and various different abstracts so you can understand what might be of most interest to you. Listed for you here are four sessions that we thought might be of particular interest to our audience members. Once is The Voice of Enterprise for Kindred Healthcare, talking about their transformation to SD-WAN. Zscaler talking about their Cloud-delivered security with SD-WAN specifically with Viptela and a number of case studies and best practices, a live demonstration, which is quite popular, which will help you understand how to actually deploy SD-WAN, as well as cloud migrations from AWS, as well as Azure.

And, Shamus, do you have any final words that you’d like to end with?

Shamus: No, just thank you for including me in this and I hope everyone has a great week attending all these webinars. I hope it’s very valuable to them and if anyone has any questions, you know, I’ve included my email and my Twitter handle at the beginning, so please reach out to me.

Interviewer: And with that I’d like to thank everybody for joining our webinar today and, again, please look through the Summit and register for some other sessions. It’s going to be an exciting week. Thank you.

Shamus: Thank you.

[End of recorded material 00:39:34]

 

Watch Now