SD-WAN 360

Episode 4: IT version 1.0 : What Are The Challenges With Traditional Networks?

February 05, 2019 Season 1 Episode 4
SD-WAN 360
Episode 4: IT version 1.0 : What Are The Challenges With Traditional Networks?
Chapters
SD-WAN 360
Episode 4: IT version 1.0 : What Are The Challenges With Traditional Networks?
Feb 05, 2019 Season 1 Episode 4
Rohan Naggi
IT 1.0, What are the pain points with Traditional Networking?
Show Notes Transcript

In this episode, we discuss the challenges and pain points of using traditional networks and how SD-WAN comes to the rescue. 

SD-WAN technology is vast and cannot be captured in a single episode. Stay tuned for upcoming episodes to take you into SD-WAN journey and learn about:

- Challenges with traditional networking, pain points
- What is SD-WAN? Basics of SD-WAN
- Why SD-WAN? Why customers are moving towards SD-WAN?
- What network problem SD-WAN solves?
- What is the architecture for SD-WAN and their Core features?
- What are the form factors and different deployment options and more.....Stay tuned.



Support the show

Speaker 1:
0:05
Hello and welcome to the podcast. I'm your host [inaudible] 93 60 podcast is your destination for all things SD ban. The technology that is transforming networking, SD one three 60 podcasts will help you keep abreast of the latest in the industries and learn from industry experts their opinion and their experiences. Please do reach out if you have a solution on topics are people you would like to hear from. Stay tuned for SD wan three 60 part because one of its kind
Speaker 2:
0:41
do your import cars from the heart up to the con
Speaker 1:
0:50
model van has an a. In this episode we'll talk about Sd van software defined wide area networking, the core concept of the software defined wide area networking. I will also discuss how networking needs have evolved as businesses can zoom application services and those networking sources in a new one different way. So after listening to this episode, you'll be able to answer what is se van, what are the basics of these Sd van? Why is the one why customers are moving towards this? Steven, what are the network challenges are the problem? Does the SD wan Salts? What's the architecture of Steven and what are the those core features, which makes this a complete solution? What are the form factors, deployment options and more so get ready for this SD ram journey. Let's define van equity high level and then we'll go deeper in. And Stephen takes the same principles from SDN, software defined networking, vetted decouples, the control plane from the underlying network infrastructure control plane, segregation from the data plane.
Speaker 1:
2:08
And this will help us manage multiple SDN devices, which are deployed that grand site audit, the data center side so that the orchestrator, the management layer can centrally manage all these devices. We also run these as dyn on multiple grants circuits. So transport independence comes to play, but SD ban. So from here, let's first start off with what are the challenges with the traditional van and how those challenges or address by s d man. So what are the challenges with their traditional run? First one where we can talk about this expensive Capex and opex model. Slower deployment time. If I have to deploy brand site, I would be requiring an ID stuff. Then ordering the leased lines, those private circus, which would take months and months put point back haul for the Internet traffic and the cloud services. So from the brand site, if a user wants to access the internet or any SASS application through the enterprises are back calling their internet traffic from the brand side to the data center side and then to data applications are running slow applications are everywhere.
Speaker 1:
3:33
They are on prem are in cloud not leveraging those multiple van circuits which are getting terminated at the brand sex. So you have public circuit, you have private circuit, you have purchased multiple van circuit for redundancy. But are you using all of them at the same time? No, they are in active standby or what we call it as active backup mode element management as did on multiple devices for each function, like security services for one optimization for Kashi. So for each of these services, that brand site, what are you having to manage, monitor or push policies? You're having monthly management stations for these devices. So to do any changes to let's say a thousand of these brand site becomes really difficult. Brand site doesn't have enough horsepower today to support today's applications or today's let's say iot devices. Let's understand some of these pain points. Let me take you back in time. Not so long ago. I'm not telling a story here, but not so long ago what I call is it 1.0
Speaker 2:
4:52
yeah.
Speaker 1:
4:52
Keeping the business connected on productive on a van was relatively rigid, but what's a straight forward process? Most applications where the siding in the data center, all your servers, we're in the data center and most of the deployment model was on premise deployment model. There was no concept of cloud that that time where it stopped. Good monitor the network, the resources, servers, storage network policy from data center. Now to access these sort of sources from grants, site users simply connect to these resources by a private circuit, MPLS or even public suckage. Multiple ran circuits exist that time, but then only one circuit was active, so the circuits written an active standby mode. User traffic was very predictable, flowing directly from each of these brands site to data center and back again
Speaker 1:
5:51
when it was time to add more bandwidth, it staff would have to purchase more bandwidth which could take to get these private connections or like these knees lines plus the setup configuration of the devices which comes with it. The Ce router, the router which comes with the MPLS network, you also need a trained id stuff. Are these remote locations? This we just talked about, the sector are bringing up the new side. After the site is up, all the internet traffic which end user wants to access from the brand side, it has to be back hauled to the data center where the centralized firewall, the bullet proof firewall offer security services for our traffic which is destined for public cloud or for Internet in this case, from brand side to data center enterprises using the private circuit for Internet traffic. Again, the enterprise is using the private circuit, the MPLS limited bandwidth, the expensive bandwidth from the brand side to data center for Internet traffic.
Speaker 1:
7:01
This uproar traces to concerns enterprise business critical application, but now have to fight for the bandwidth contention and the latency problem on these private suit. It's going to affect all the business critical application and at the same time the Internet traffic it stops. We'll have to start working on the quality of service configuration for each of these sites and configured to us on each of these network devices. So the configuration is also not complicated. It has to be done for each and every network device. Now let's bring in one more angle, which is the Kong Bangkok lover of Van problem with the emerging technologies like cloud virtualization, Iot devices, mobile labs, mobile devices and option network is expanding. Network architecture today requires a fresh approach. Management trends are changing and the book teams are facing increasing pressure, [inaudible] centralized, then they took control and at the same time provide optimal part to these applications. Whether those applications are on prem or in the cloud network equipment footprint under deployment complexity is on the rise.
Speaker 2:
8:30
Okay.
Speaker 1:
8:31
Two days earlier. Name applications are demanding more and more bandwidth or the other time application. At the same time, they are sensitive to these van impairments like latency, jitter, packet loss, especially when they are on the broadband connections. At the same time the piece of the network change is on the rise and it infrastructure is a key enabler for these demanding business growth. Business requirement is to offer user access to these next vocalist sources at any given time, 24 by seven and at the same time skill these on demand. So I need more bandwidth for an application on demand. The Banbagers Barton minus it is simply unacceptable for a network to be a bottleneck. That's the key for a business to function. No. Let's summarize all these challenges faced by today's Yvonne. First point here is enterprises are adopting to the cloud. So from on Prem we are moving towards cloud.
Speaker 1:
9:42
There are enterprises who are having both on prem solution, cloud deployment model. Also applications out of Rebif applications are on prem applications are in the cloud, do SAS based applications. Now accessing application in the cloud and on premise enterprises are deploying multiple ran circuits because now applications have increased, application growth have increased. So the van, so goods are in tourism. Enterprises are deploying multiple van circuits of all types from all the service providers for it and NC Paupers, private circuit, public socket, the moderns, all those are being deployed. Nick fuck policy push becomes a problem. Complex quantity of service netbook policies are required to access these applications, switch out in cloud or on prem element management times to play. Each and every network device has their wound element management. And then once you have these broadband public connections for your enterprise application, they bring their own problem security and those run impairments we talked about CJ tell packet loss with multiple brands.
Speaker 1:
11:00
Okay. Now these network policies, which an ID staff needs to push from the orchestrator or from the management station. Now they have to push it for each applications. Each branch has a unique or a different topology network topology. So based on their network topology, the policies needs to be pushed. So if you see the net network management becomes very complex at the same time when your network is growing end to end. Visibility also becomes a nightmare. These element management and he hits a road block and providing centralized visibility and control at the same time. They creates a roadblock for troubleshooting. Now you have multiple devices from multiple vendors and then the troubleshooting, cla access each has their own syntex shoots all together becomes a nightmare. So for business continuity, netbook should always be on 24 by seven. That's what an enterprise Bolus, even a brief outage can cause a significant disruption to the business. So till now we talked about these challenges, today's Van Interpretation van where we have on prem cloud deployment model applications are everywhere. There are multiple vans sockets on the public one circuit we have problems of security. Those van impairments like latency, jitter, backward clause, the element management, which is coming in the end to end visibility, which is required in today's Vanek book.
Speaker 1:
12:50
So in this episode we're going to talk about how as the van can head position enterprises to address these concerns. And so as a foundation to modernize the enterprise network for the future, what does it mean in real world falling into place? What if you could set up a brand site, let's say for the retail customer, one for a construction site in less than a novel without sending an IT staff, providing better health care by delivering high resolution scans and quality audio video communication to the remote clinics. Stay tuned for the next episode. Take you to the SD Ranjan [inaudible].
×

Listen to this podcast on