SDWAN Deep Dive

WEBVTT
00:00:30.230 --> 00:00:34.000
everybody, welcome back to this week's edition of Breaking Down the Bites.
00:00:35.024 --> 00:00:36.585
As usual, I'm your host Pat.
00:00:36.765 --> 00:00:38.865
You can find me on Twitter at layer eight packet.
00:00:38.924 --> 00:00:40.605
That is the number eight.
00:00:40.935 --> 00:00:45.015
You can find Kyle on Twitter at Dan 2 56.
00:00:45.375 --> 00:00:49.004
You can find the show on Twitter Breaking Bites pod.
00:00:49.364 --> 00:00:55.965
Alex, you're not on social, so if anybody wants to get a Alex, just hit the shows Twitter and we will certainly get it to him.
00:00:56.024 --> 00:00:58.905
So we are pretty active on Twitter, so come say hello.
00:00:59.054 --> 00:01:01.394
The more friends, the better the time is.
00:01:01.454 --> 00:01:07.384
So, also if you like the show, don't forget to subscribe on your streaming platform of choice.
00:01:07.895 --> 00:01:08.490
As usual.
00:01:08.495 --> 00:01:11.439
We always like those numbers and people coming to say hi.
00:01:11.579 --> 00:01:15.765
So, Pick it out, subscribe, like, share all that kind of good stuff.
00:01:16.155 --> 00:01:17.775
And more ears and eyes on us.
00:01:17.775 --> 00:01:18.465
It's always good.
00:01:18.465 --> 00:01:21.164
So the three amigos are back again.
00:01:21.615 --> 00:01:24.435
We had a rough few weeks schedules.
00:01:24.435 --> 00:01:29.085
Alex, you're on vacation, enjoying Disney World down there in sunny Florida.
00:01:29.715 --> 00:01:36.414
And so Kyle and I had to fend for ourselves and do the show you know, do the show as a duo rather than a trio.
00:01:36.414 --> 00:01:37.134
But that's okay.
00:01:37.254 --> 00:01:39.685
All back and rocking and rolling, right?
00:01:39.685 --> 00:01:41.164
So, back from vacation.
00:01:41.169 --> 00:01:41.435
Mr.
00:01:41.435 --> 00:01:41.854
Alex.
00:01:41.854 --> 00:01:42.365
What's up man?
00:01:42.370 --> 00:01:42.414
How
00:01:43.414 --> 00:01:49.185
Oh, doing pretty well, obviously back from extended vacation to the cruise too.
00:01:49.185 --> 00:01:55.895
So it was Disney World followed by a cruise, so it was 11 days and I'm back.
00:01:55.895 --> 00:01:56.525
I'm ready.
00:01:57.020 --> 00:01:57.240
man?
00:01:57.620 --> 00:01:59.990
Some people got all the luck, let me tell you, man.
00:02:00.990 --> 00:02:01.490
Oh man.
00:02:01.689 --> 00:02:02.620
Kyle, what's up man?
00:02:02.620 --> 00:02:03.009
What are you doing?
00:02:03.370 --> 00:02:03.879
What are you up to?
00:02:03.879 --> 00:02:05.169
Any Eddie Cruises for you?
00:02:05.634 --> 00:02:05.995
No.
00:02:06.115 --> 00:02:08.544
I mean, if it keeps raining like this though, maybe I could.
00:02:09.044 --> 00:02:11.955
Float down the road in like a little dinghy or something.
00:02:12.150 --> 00:02:15.060
We'll just build ourselves a boat and get rolling.
00:02:16.889 --> 00:02:17.099
Yeah.
00:02:17.099 --> 00:02:18.569
It was raining the last like three days.
00:02:18.569 --> 00:02:19.590
There's been nothing but rain
00:02:19.995 --> 00:02:20.354
Mm-hmm.
00:02:20.370 --> 00:02:21.539
in the front yard and everything.
00:02:21.544 --> 00:02:22.685
It's brutal out there.
00:02:23.685 --> 00:02:26.175
And that's that's your weekly weather report from Kyle, so
00:02:26.310 --> 00:02:26.819
That's right.
00:02:27.330 --> 00:02:27.810
That's right.
00:02:28.080 --> 00:02:29.520
I expect it every week now.
00:02:29.909 --> 00:02:30.689
What's the weather like?
00:02:32.310 --> 00:02:33.509
It's beautiful where I'm at.
00:02:33.960 --> 00:02:34.379
That's
00:02:34.419 --> 00:02:34.900
you're wondering,
00:02:35.319 --> 00:02:37.150
that's as expected.
00:02:37.435 --> 00:02:37.944
you're right.
00:02:38.080 --> 00:02:38.590
expected.
00:02:39.790 --> 00:02:40.030
No.
00:02:40.060 --> 00:02:40.599
All good.
00:02:40.659 --> 00:02:41.050
All good.
00:02:41.050 --> 00:02:41.980
So everybody's back this week.
00:02:42.590 --> 00:02:44.900
A few tidbit or notes Alex.
00:02:44.900 --> 00:02:47.599
Well first of all, what was your favorite ride at Disney?
00:02:47.659 --> 00:02:48.469
I have to know.
00:02:49.469 --> 00:02:58.290
well, I went to Animal Kingdom and Epcot and there was two that stood above the rest, I mean, pretty easy, pretty far ahead of third place probably.
00:02:58.800 --> 00:03:05.150
And that was Pandora's flight at Animal Kingdom and Cosmic Rewind at Epcot.
00:03:05.995 --> 00:03:09.750
Both of those are worth the wait and worth the trip to the parks just for those rides,
00:03:10.080 --> 00:03:10.409
Damn.
00:03:10.469 --> 00:03:11.040
Look at that.
00:03:11.370 --> 00:03:12.000
That's awesome.
00:03:12.450 --> 00:03:15.670
I have done Pandora's flight, which was awesome.
00:03:16.120 --> 00:03:27.655
And then so when I was there in 17 on the honeymoon, they did not have the the one in Epcot yet, so I'm sure it was being built or at least planned upon.
00:03:27.655 --> 00:03:34.280
So I'm, so we're going in December, so I'm curious to see what that that looks like in December again, so, we'll see.
00:03:34.280 --> 00:03:37.400
But like when we were there the first time, like toy story land, none of that was there.
00:03:37.400 --> 00:03:38.240
It was all being built.
00:03:38.240 --> 00:03:40.250
So I'm interested to see what's up there.
00:03:40.250 --> 00:03:42.770
So, oh, did you do test track at Epcot?
00:03:43.330 --> 00:03:44.060
Oh yeah, test.
00:03:44.060 --> 00:03:44.840
Yeah, I did test track.
00:03:44.840 --> 00:03:45.110
Yep.
00:03:45.170 --> 00:03:45.800
Yeah, that was fun.
00:03:45.860 --> 00:03:46.490
That was cute.
00:03:47.150 --> 00:03:48.349
Cuz my kids were there.
00:03:48.719 --> 00:03:56.659
So, you know, obviously it's a competition then, so you can build the best car and yeah, my oldest ended up having the best.
00:03:58.240 --> 00:03:58.540
So, yeah.
00:03:58.599 --> 00:04:01.569
Yeah, that was a good time and RTU was really good.
00:04:01.599 --> 00:04:03.969
I mean, that might even be one that I should have mentioned too.
00:04:03.969 --> 00:04:05.260
I really enjoyed rtu.
00:04:05.260 --> 00:04:06.760
It might be because I love the movie.
00:04:06.760 --> 00:04:10.900
It's probably, I'm not even ashamed to say it's probably my top five favorite movies.
00:04:11.335 --> 00:04:11.875
All right.
00:04:12.110 --> 00:04:14.800
And I really did enjoy the ride ba.
00:04:15.800 --> 00:04:16.490
Well, awesome.
00:04:16.490 --> 00:04:17.620
That's a good deal.
00:04:17.620 --> 00:04:22.680
So everybody's got a little low down on Alex's Disney trip, so it's all good.
00:04:22.800 --> 00:04:23.279
All good.
00:04:23.610 --> 00:04:31.769
One thing I will mention I don't know, Alex, you wanna mention this too, but this my, for my first time at Cisco live, so I'm excited.
00:04:31.829 --> 00:04:34.824
We got the sessions all scheduled, the hotel's good.
00:04:34.824 --> 00:04:36.209
The the flight's all scheduled.
00:04:36.209 --> 00:04:38.189
So first time out there in Vegas.
00:04:38.189 --> 00:04:39.629
So I'm ready to rock and roll.
00:04:40.009 --> 00:04:41.319
So, Alex, are you going?
00:04:41.529 --> 00:04:42.449
Did you say you were going
00:04:44.084 --> 00:04:53.745
Yeah, I think the last time we talked about it, I may have been 50 50, but yeah, I'm booked, I'm registered, I'll be out there, so we'll be able to catch up in a
00:04:54.000 --> 00:04:54.360
Yeah.
00:04:55.079 --> 00:04:55.790
Yeah, I'm in.
00:04:56.150 --> 00:04:56.780
I always
00:04:56.780 --> 00:04:58.170
and Nate's gonna be there.
00:04:58.785 --> 00:04:59.264
What's that?
00:04:59.910 --> 00:05:00.750
Nate
00:05:00.884 --> 00:05:01.694
Oh yeah.
00:05:01.829 --> 00:05:02.100
be there
00:05:02.329 --> 00:05:02.834
it's awesome.
00:05:03.165 --> 00:05:03.454
Yeah.
00:05:03.454 --> 00:05:04.305
Looking forward to
00:05:04.590 --> 00:05:07.350
and I are actually staying in the same hotel.
00:05:07.365 --> 00:05:07.935
Where are you staying?
00:05:08.225 --> 00:05:09.810
staying at Tropicana?
00:05:10.995 --> 00:05:11.754
I'm at the Luxer.
00:05:11.819 --> 00:05:12.480
know where.
00:05:13.199 --> 00:05:26.935
Yeah, that's kind of like the, don't wanna call it the budget one, but it's like if your part that's the cheapest hotel that's Cisco Live has some type of, Affiliation with so you can get some discount.
00:05:26.965 --> 00:05:27.475
Yeah.
00:05:27.775 --> 00:05:40.915
So yeah, if I didn't make he, but he managed to find a place at Tropicana a while back, probably through some crazy credit card deal thing that he likes spending half his day trying to
00:05:41.230 --> 00:05:41.519
Yeah.
00:05:41.665 --> 00:05:44.514
But yeah, so I got in for like 75 bucks a night.
00:05:44.725 --> 00:05:46.314
And that's after taxes and stuff?
00:05:46.560 --> 00:05:46.780
Wow.
00:05:47.084 --> 00:05:47.310
Yeah.
00:05:47.860 --> 00:05:48.490
Hell yeah.
00:05:48.769 --> 00:05:49.430
That's killer.
00:05:50.004 --> 00:05:50.125
Yeah.
00:05:50.970 --> 00:06:03.050
Yeah, so I'm going I know a bunch of the Cisco champs, the program that we're a part of, there's a bunch of people going there, so it'd be nice to put names with faces and, you know, they'll be friends for a couple of days in real life instead of just cyber life.
00:06:03.139 --> 00:06:04.430
So that's always kind of cool.
00:06:05.840 --> 00:06:08.060
So always a
00:06:08.105 --> 00:06:08.555
Yeah.
00:06:08.555 --> 00:06:15.930
And then we get to play the vendor dinner game because this is the first time that I've gone where work hasn't been paying for my travel.
00:06:16.285 --> 00:06:16.574
Okay.
00:06:17.150 --> 00:06:29.300
So, They're paying for me to get into the conference, well, using the learning credits that Disney has, but since they're still technically a travel freeze, the anything related to travel is on my time.
00:06:29.305 --> 00:06:41.009
So the 300 bucks on the hotel I spent I'm only a few hour drive away, so it's like a$70 flight if I wanted to do a flight, which I probably will, but yeah.
00:06:41.040 --> 00:06:49.920
But food, this will be the first time I've gone to Cisco live and since the company's not paying for my food, I'm gonna have to try real hard to get vendors to pay for it.
00:06:49.920 --> 00:06:50.280
So that's my
00:06:50.375 --> 00:06:50.905
Heck yeah.
00:06:50.944 --> 00:06:53.400
4, 4, 4 dinners paid for.
00:06:53.699 --> 00:06:54.530
I got one so far.
00:06:54.930 --> 00:06:56.819
My Cisco rep guaranteed me a
00:06:57.115 --> 00:06:57.405
Nice.
00:06:57.810 --> 00:07:00.480
so I gotta get three more and then the C C I E dinner.
00:07:01.050 --> 00:07:05.340
But I don't know if I'll go to it, but that's usually a decent meal, but I can only bring one person.
00:07:05.345 --> 00:07:09.030
So if I'm there with you and Nate, then I kind of feel like a, an ass
00:07:09.150 --> 00:07:13.079
Well, now that we're part of the champs, that there's a bunch of c Cs in the Champs program.
00:07:13.110 --> 00:07:15.590
So if they're there, then they can be my date for the night.
00:07:15.590 --> 00:07:16.040
That's cool.
00:07:16.090 --> 00:07:17.550
I, there's no shame in my game.
00:07:17.550 --> 00:07:24.266
So any of my fellow champs that are C C I e, that plan on going to the the dinner you I'm your plus one.
00:07:24.906 --> 00:07:25.896
I have your dibs.
00:07:26.706 --> 00:07:27.817
I'm making it public.
00:07:28.817 --> 00:07:29.507
Nah, it's gonna be cool.
00:07:29.627 --> 00:07:30.557
So we're looking forward to that.
00:07:30.557 --> 00:07:34.906
And I think there is a, there's a champs thing, I think I wanna say like Monday night.
00:07:35.086 --> 00:07:36.737
It's either Monday night or Tuesday night.
00:07:36.742 --> 00:07:38.417
They do like a thing with the actual champs.
00:07:38.422 --> 00:07:40.456
So like we have our own dedicated space and stuff.
00:07:40.456 --> 00:07:45.576
So I'm curious to check that out and kind of hang and see what all that brings to the table.
00:07:45.576 --> 00:07:46.387
So that's kind of cool.
00:07:46.896 --> 00:07:47.617
I'm looking forward to it.
00:07:47.901 --> 00:07:48.711
it's gonna be exciting.
00:07:48.711 --> 00:07:51.852
And if you're not already familiar with that, there's always some big event.
00:07:52.331 --> 00:08:00.081
You know, once a week, wherever everyone that goes to Cisco Alive can go to, they, they actually rented out Allegiant Stadium, a Raider Stadium.
00:08:00.912 --> 00:08:03.802
And I'm not big Gwen Stefani's playing.
00:08:03.862 --> 00:08:04.252
Okay.
00:08:04.852 --> 00:08:06.862
So if you're into Gwen Savani,
00:08:07.762 --> 00:08:08.662
See, I was into her
00:08:08.662 --> 00:08:09.531
at Legian Stadium.
00:08:09.531 --> 00:08:10.042
And we're there.
00:08:10.076 --> 00:08:11.122
I'll tell you that much right now.
00:08:11.127 --> 00:08:12.201
That was like my first crush.
00:08:12.206 --> 00:08:14.151
I was like, oh man, she's awesome.
00:08:15.151 --> 00:08:15.752
Heck yeah.
00:08:16.262 --> 00:08:18.572
Actually have a no doubt on, on vinyl.
00:08:18.932 --> 00:08:19.653
So I love I
00:08:19.680 --> 00:08:20.131
Well, there you
00:08:20.161 --> 00:08:20.550
from Gwen
00:08:20.821 --> 00:08:24.331
Well, maybe, so I guess you're gonna head to over and watch that
00:08:24.430 --> 00:08:25.721
See where the wind takes me.
00:08:26.620 --> 00:08:28.201
I feel like it's a big task.
00:08:28.381 --> 00:08:31.230
Being your first time in Cisco Live, there's just so much going on.
00:08:31.230 --> 00:08:32.640
You're just like, I don't know what to do next.
00:08:33.000 --> 00:08:36.120
So I'm sure I'll have a little bit of that as well.
00:08:36.480 --> 00:08:44.841
Yeah, there's the thing that I wanted to do but didn't get to do it to its full extent, last time I was at Cisco Live was they started doing escape rooms.
00:08:45.680 --> 00:08:48.170
But these escape rooms are it focused.
00:08:48.650 --> 00:08:59.331
So you, so to get outta it, you have to do things like like maybe log into an unencrypted S S I D and like mess around with that and find some stuff to get out of an escape room.
00:09:00.980 --> 00:09:01.490
Oh man.
00:09:01.490 --> 00:09:08.780
I hope they don't make me like, like code like Java file or JS O or write a Python script from scratch.
00:09:08.780 --> 00:09:11.481
Cuz I'll be there until like the following week they'll be like, oh, nope.
00:09:11.721 --> 00:09:12.530
Can't go anywhere.
00:09:13.460 --> 00:09:17.170
well, you'll just have to take a breakout session on programming before you do that or
00:09:17.320 --> 00:09:18.340
Yeah, I got a bunch
00:09:18.370 --> 00:09:18.550
Alright.
00:09:18.640 --> 00:09:19.480
There's so much fun.
00:09:20.710 --> 00:09:21.070
Yep.
00:09:21.075 --> 00:09:21.700
For sure.
00:09:21.750 --> 00:09:22.320
Lots of fun.
00:09:22.740 --> 00:09:29.710
And then I always like playing there's like trivia games that you can win prizes and I've won some pretty neat prizes over the years.
00:09:29.710 --> 00:09:31.900
Like a, an Amazon Echo.
00:09:31.905 --> 00:09:33.100
Before they were really cheap.
00:09:33.170 --> 00:09:33.171
Yeah.
00:09:33.545 --> 00:09:41.565
and one of those s n e s emulators that were really hard to find one year that was like everyone's go-to Christmas present or something.
00:09:42.165 --> 00:09:43.485
I won one of those one year.
00:09:43.840 --> 00:09:44.985
Yep, for sure.
00:09:45.855 --> 00:09:46.635
Yeah, it's interesting.
00:09:46.635 --> 00:09:49.125
So if anybody's had Cisco Live, hit us up.
00:09:49.485 --> 00:09:50.145
We'll be there.
00:09:51.075 --> 00:09:51.795
It's gonna be cool.
00:09:51.825 --> 00:09:52.846
So I'm looking forward to that.
00:09:52.846 --> 00:09:55.195
So, Kyle, maybe next year you can come with us, man.
00:09:55.315 --> 00:09:56.725
Just be like, yo, cuts down.
00:09:57.025 --> 00:09:58.346
Put me on a plane, let's go.
00:09:59.346 --> 00:10:00.235
Oh, it's awesome.
00:10:00.775 --> 00:10:02.795
So anyway get a little of that out of the way.
00:10:02.846 --> 00:10:07.405
The the topic this week, I feel like the deep dives that we've done have done pretty well for us.
00:10:07.415 --> 00:10:09.605
So pe people have really found some value out of it.
00:10:09.605 --> 00:10:19.535
So I figured the deep dive this week, and it'll kind of be, it'll in, it'll be in my wheelhouse, if you will, since I've dealt a lot with it over the last couple of years.
00:10:19.535 --> 00:10:22.035
But I think we would do a deep dive on SDWAN.
00:10:22.055 --> 00:10:23.285
I feel like that's a big one.
00:10:24.035 --> 00:10:26.315
It's a major player in today's space.
00:10:26.365 --> 00:10:28.995
It, you know, maybe a couple years ago it wasn't really.
00:10:29.925 --> 00:10:32.385
Mainstay yet or, you know, center stage.
00:10:32.385 --> 00:10:40.145
But I think now people are moving away from the legacy WAN types and SD WAN is very very much so in the conversation.
00:10:40.145 --> 00:10:43.955
So I figure we would take this episode and do an SD wan deep dive.
00:10:43.955 --> 00:10:47.045
So I guess I'll kind of get this started off.
00:10:47.045 --> 00:10:55.255
And you know, like I said, the last couple of places I've been have run a flavor of SD wan and they're all three different flavors, if you will.
00:10:55.525 --> 00:11:00.415
So I've gotten a wide breadth of SD wan experience over the last couple years.
00:11:00.475 --> 00:11:16.475
And both from a, you know, maintenance perspective of, okay, it's already here, just, you know, kind of scale it and maintain it and from a, you know, grassroots, completely greenfield, deploy it and then manage it, you know, perspective.
00:11:16.480 --> 00:11:19.985
So, yeah, I figured that this would be the good one to do that with.
00:11:19.985 --> 00:11:34.805
So, So, yeah, I guess, I kind of give a little depth in depth of kind of how we got here and what, and I think the sdwan stuff will make a little more sense, but just kind of talking general scopes like back I don't know.
00:11:34.955 --> 00:11:37.505
I took my CCNA in 2013.
00:11:37.685 --> 00:11:41.415
I started in 2010 and then passed it in 13.
00:11:42.015 --> 00:11:51.915
And when I passed it in 13, there was still frame relay questions on my CC n a, which you talk about frame relay now people look at you like you have six heads, look what the hell's frame relay.
00:11:52.215 --> 00:11:56.045
So, so, so some legacy wan things, right?
00:11:56.045 --> 00:12:03.575
So you have frame relay at least from my perspective when I started kind of learn about this stuff, frame relay was the wan back then.
00:12:04.065 --> 00:12:07.825
And Delsey's and all that kind of stuff that made frame relay work underneath the hood.
00:12:08.215 --> 00:12:17.905
And then, so, That from Frame Relay, then PLS came into the picture and it was yeah, that was the darling of the industry for quite a while.
00:12:17.995 --> 00:12:27.110
And, you know, so that was, you know, end to end QS and, you know, private connectivity and all that kind of stuff.
00:12:27.200 --> 00:12:28.430
Pls, cloud, whatever you wanna call it.
00:12:28.710 --> 00:12:35.990
So a lot of voice systems ran over pls cuz it was dedicated Q os and the flexibility that came, that sort of thing.
00:12:36.200 --> 00:12:39.535
But then m you know, the drawback to M pls was cost, right?
00:12:39.535 --> 00:12:40.525
It was really expensive.
00:12:40.530 --> 00:12:40.605
Right?
00:12:40.855 --> 00:12:54.035
And depending on how many offices you had or how many sites you had and to drop an mpl l s circuit in there, in some instances I've been in places that have two MPLS and primary and a secondary to drop both of them in there were quite expensive.
00:12:54.035 --> 00:13:02.705
So, And a couple years ago I started with SD WAN around, I wanna say 2018, 2019, somewhere in there.
00:13:03.125 --> 00:13:13.305
And so they were moving away from the more expensive circuits of npl l s frame relay, you know, for those that still had it out there, things of that nature.
00:13:13.365 --> 00:13:14.795
And go into broadband, right?
00:13:14.795 --> 00:13:18.735
Or, you know, just changing over to just business broadband, right?
00:13:18.735 --> 00:13:28.195
But the question was how do you get the M P L S performance or the benefits of NPL s out of a broadband you know, business class circuit, right?
00:13:28.195 --> 00:13:32.846
So I think that's where SD WAN comes in and sort of blends the two together.
00:13:33.475 --> 00:13:39.235
And so the idea of SD wan it has multiple.
00:13:40.450 --> 00:13:41.950
I should say ideas wrapped around it.
00:13:41.950 --> 00:13:42.130
Right.
00:13:42.130 --> 00:13:51.430
But it's the idea is to basically from an SDWAN perspective, get a get, you know, I should say from a WAN perspective, I.
00:13:52.695 --> 00:13:56.715
Basically use just whatever transports you want to use, right?
00:13:56.715 --> 00:13:59.205
Whether that's, if you wanna stick with mpls, great.
00:13:59.505 --> 00:14:04.125
If you wanna, if you want to get a broadband circuit, a business class, i s p in there, great.
00:14:04.125 --> 00:14:06.255
If you wanna do cellular or great, you know, that kind of thing.
00:14:06.645 --> 00:14:15.810
SD WAN can terminate all of those connections and then basically be intelligent enough to to make its decisions on which.
00:14:16.620 --> 00:14:27.600
Which circuit or with which leg, which transport to actually use based off of its own intelligence of, okay, packet loss jitter latency, things of that nature.
00:14:27.630 --> 00:14:40.420
It's constantly measuring for those three types, or I should say those three things, it's measuring those on each one of the legs, and then based off of those measurements it intelligently chooses which connection to use.
00:14:40.900 --> 00:14:46.260
So you have that automatic failover, you have that intelligence to it.
00:14:46.260 --> 00:14:50.790
You have, you know, you can prefer, you know, in the settings or, you know, however you design it.
00:14:50.846 --> 00:14:56.175
You can prefer, you know, one leg over the other two, or however many you have.
00:14:56.175 --> 00:14:57.405
Say you have three legs, right?
00:14:57.485 --> 00:14:59.165
You can load balance across all three.
00:14:59.346 --> 00:15:01.475
You can prefer one over the other two.
00:15:01.475 --> 00:15:04.325
You can do two over the other one, you know, that sort of thing.
00:15:04.325 --> 00:15:08.286
So there's quite a bit of flexibility and it scales very well as, as well.
00:15:08.375 --> 00:15:16.245
So from the underbelly of that, The SD WAN takes the, you know, the intelligence out of it, right?
00:15:16.245 --> 00:15:24.955
So, and Alex and Kyle, you guys have been around long enough that, you know, if you had 50 sites, you had 50 routers, and you were managing all 50 at each place, right?
00:15:24.955 --> 00:15:32.415
So, you know, you had the s SSH into each, you know, router or switch or whatever you're doing, and, you know, make those changes.
00:15:32.415 --> 00:15:34.576
And it was very time consuming and blah, blah, blah.
00:15:34.905 --> 00:15:38.145
So what Sdwan does is with software defined networking, right?
00:15:38.145 --> 00:15:41.765
It's a it's a central place to manage all.
00:15:42.605 --> 00:15:44.285
So however many sites you have.
00:15:44.585 --> 00:15:50.255
And then basically that config is then pushed down to each of the actual boxes on site.
00:15:50.495 --> 00:16:02.445
So you're taking the, you're taking the intelligence off the actual box, or I should say the control plane, really off the actual box and bringing it to a central, centralized location.
00:16:02.865 --> 00:16:07.945
And so that way, you know, you can have 50 sites today and you can have a hundred sites tomorrow.
00:16:07.945 --> 00:16:15.715
And basically you're just deploying the box at each site and the configuration gets pushed down and off you go.
00:16:15.715 --> 00:16:15.955
Right?
00:16:15.955 --> 00:16:18.605
So that it's very scalable in that fashion.
00:16:18.655 --> 00:16:18.835
So.
00:16:19.870 --> 00:16:22.320
But it's very centrally managed.
00:16:22.330 --> 00:16:29.165
Again, you know, the brain lives at a central location, and then everybody sort of, you know, all the, I should say spokes, right?
00:16:29.275 --> 00:16:31.405
Maybe it's a little better to say a hub and spoke.
00:16:31.455 --> 00:16:34.490
With that terminology everybody calls home, right?
00:16:34.770 --> 00:16:38.840
Each spoke calls home or you know, every now and then it checks in to make sure it's still there.
00:16:39.020 --> 00:16:45.645
And then if something needs to be pushed down, if the configuration needs to be pushed down, then it comes from the brain and goes downhill, right?
00:16:45.645 --> 00:16:48.625
Goes southbound, if you will, in today's technology.
00:16:48.630 --> 00:17:01.125
So those are some of the things that, you know, I've seen with SD WAN that make, you know, larger enterprises life's a little easier with scale, with you know, configurations all being the same, working from templates, right?
00:17:01.130 --> 00:17:07.211
So each one of those, or you can make as many templates as you want, but the idea is to templatize your configurations, right?
00:17:07.421 --> 00:17:12.826
Not just you know, Not just have 50 sites and 48 of them are all different, right?
00:17:12.826 --> 00:17:17.736
So the idea is then to push you know, templatize it, you get your standard config across the board.
00:17:17.855 --> 00:17:21.155
That way it's much easier to manage, et cetera, et cetera, you know, et cetera.
00:17:21.155 --> 00:17:22.836
So I said a lot there.
00:17:22.836 --> 00:17:37.191
Did you guys have any sort of questions as we kind of jump in here with either what it, what its purpose is, what it's trying to do, and kind of where it's, you know, where it's at the current state of today's networks?
00:17:38.191 --> 00:17:43.901
I think you, I guess you really kind of focused on two different things just now when you're trying to explain SD WANs.
00:17:43.906 --> 00:17:47.980
So, and like you said, it was quite a few minutes there of explaining it.
00:17:47.980 --> 00:17:57.851
So if you were trying to define SD WAN and weren't trying to use like the dictionary definition of it, what.
00:17:58.151 --> 00:18:01.391
What's the simplest way you could explain SD wan?
00:18:01.480 --> 00:18:25.691
So would you say, based on what you just said, that SD WAN is allowing you to use several different types of connectivities or such as mpl, l s, internet cellular, combining those and then kind of giving you a centralized management to intelligently do stuff with it?
00:18:25.901 --> 00:18:26.351
Or
00:18:26.451 --> 00:18:27.411
that's probably
00:18:27.456 --> 00:18:27.996
describe
00:18:28.161 --> 00:18:29.240
That's probably the best way.
00:18:29.240 --> 00:18:32.211
So I, you know, SD WAN basically uses software right?
00:18:32.211 --> 00:18:45.296
To control, you know, the big three connectivity management and the data, the services, right in between, you know, whatever you have data senators, remote offices, cloud, you know, the big three cloud, you know, that kind of thing.
00:18:45.296 --> 00:18:49.556
So it bridges all of those together from a WAN perspective, right?
00:18:49.561 --> 00:18:55.316
So, especially now with the, and I'll kind of touch on the cloud thing, especially now with the explosion of the cloud.
00:18:55.316 --> 00:18:56.876
Like if you were on a, on an PL l s.
00:18:57.746 --> 00:18:58.226
Network.
00:18:58.256 --> 00:18:58.526
Right?
00:18:58.526 --> 00:19:02.666
Or wan, how would you get an M P L S circuit in your cloud?
00:19:02.746 --> 00:19:03.556
That doesn't exist.
00:19:03.556 --> 00:19:04.906
That doesn't compute, right?
00:19:04.906 --> 00:19:11.416
So I think Estee Wan does a nice job of, you know, being able to bridge all of that, you know, together.
00:19:11.446 --> 00:19:13.586
And I think the old legacy wan stuff, right?
00:19:13.976 --> 00:19:22.446
For folks that have been around for a bit, the old way the wind used to work is everything was back hauled through a data center, right?
00:19:22.446 --> 00:19:43.875
So you had npl, l s, you know, connecting all your sites, but the security stack right was at a data center and then basically all the traffic had to come back to that data center, get scrubbed through the security stack, and then out the, out to the internet from the data center and not locally or like a local, you know, internet breakout at wherever the site may be.
00:19:43.875 --> 00:19:46.846
So SD WAN combats that as well.
00:19:46.846 --> 00:19:52.026
You can still do it that way with SD wan I've seen it done that way, but most of them, most of the.
00:19:52.355 --> 00:19:59.836
Modern designs they do a local internet breakout right at the site, and you're not back hauling traffic anymore.
00:19:59.836 --> 00:20:05.865
So, but at the end of the day, kind of defining what it is, we're trying to throw a couple words around it.
00:20:05.865 --> 00:20:18.766
It's basically you're using software to control connectivity, management and the data in between your, you know, in between your w insights in between your data centers, again, data centers, remote offices, cloud resources, right?
00:20:18.766 --> 00:20:26.951
So, it basically, and the other thing too it's the big one here, it's, it decouples, like I said, it decouples the control plane from the data plane.
00:20:27.250 --> 00:20:40.240
You're taking the brains off of the local box at your actual sites and bringing it to a central place where then it is centrally managed and then the configuration is pushed down to the actual boxes.
00:20:41.861 --> 00:20:43.961
So I hope that answers a little bit of your question.
00:20:45.851 --> 00:20:46.121
Yeah.
00:20:46.151 --> 00:20:46.391
Yeah.
00:20:46.490 --> 00:20:48.621
I mean, certainly I'm familiar with SD wan.
00:20:48.621 --> 00:20:51.891
I'm just trying to try to see how you would describe it.
00:20:51.891 --> 00:20:57.082
Cause I think SD WAN can be defined a few different ways by different vendors, but I think.
00:20:58.895 --> 00:21:08.016
Looking for a definition that is true amongst every vendor, and I think that's probably the case, especially the two things that you mentioned and focused on.
00:21:08.181 --> 00:21:08.451
Yep.
00:21:09.661 --> 00:21:17.401
We kind of touched on it before, but I think one of the SD wan's sort of key features, right, is the ability to manage multiple connection types, right?
00:21:17.401 --> 00:21:23.230
Whether it be mpls, whether it be broadband, whether it be like cellular or wireless, things of that nature.
00:21:23.531 --> 00:21:27.441
And then basically you can segment traffic within.
00:21:27.951 --> 00:21:31.551
Those within multiple segments, right?
00:21:31.561 --> 00:21:36.451
You can chop that up and, you know, basically send it along the wan, right?
00:21:36.456 --> 00:21:42.631
So, you know, you can think of it as for those of you that are familiar, think of it as multiple vfs, right?
00:21:42.635 --> 00:21:43.641
You can split that traffic.
00:21:43.641 --> 00:21:49.770
However, you know, if you need to keep separate traffic within your wan, you can do that with SD wan.
00:21:50.111 --> 00:22:01.616
Send them within multiple segments or vfs and, you know, they use the same pipes, they use the same technologies, but they don't know, you know, tho those two vfs don't know each other exists, right?
00:22:01.622 --> 00:22:02.516
That sort of thing.
00:22:02.516 --> 00:22:05.966
So there's multiple ways to kind of, you know, skin that cat, if you will.
00:22:05.966 --> 00:22:08.336
So, I feel like that's a big one.
00:22:08.726 --> 00:22:14.726
I also think the big one there is the, again, the traditional WAN model is, you know, back hauling all that traffic.
00:22:14.726 --> 00:22:23.786
So then at your data center you have to have these, you know, massive scales of, you know, firewalls and circuits and all that kind of stuff to handle all of that traffic.
00:22:23.816 --> 00:22:42.736
Now you don't, you know, with s D A, you don't have to, cuz all the internet traffic is still, you know, with the security stuff that the SD WAN boxes now have it the, it can be done right there at the edge and, you know, broken out and sent to the internet right from the actual site instead of back hauling, you know, it all.
00:22:42.740 --> 00:22:45.176
So I think that that definitely helps as well.
00:22:45.226 --> 00:22:52.365
I was just gonna mention cause I think another question that may come up is like, how is SD WAN getting better or how's it evolving?
00:22:52.365 --> 00:23:04.605
And I think it's probably best for people to realize that, oh, I think when SD WAN was first really catching on, it was really, people just thought of it as a way to connect back to that data center, a simple way to connect back to it.
00:23:04.605 --> 00:23:12.615
They didn't wanna have to throw in a router that they had to configure some complicated VPN tunnel that they didn't know about it, how to do that.
00:23:12.615 --> 00:23:14.865
And if you have 200 sites, that can get complicated.
00:23:15.446 --> 00:23:18.596
So I think Estee Wan's first purpose was, Hey.
00:23:19.091 --> 00:23:25.510
Remote office, get back to, you know, get back to this my own little internal cloud, I guess you can say.
00:23:26.260 --> 00:23:28.510
And now it's evolving too.
00:23:28.510 --> 00:23:49.161
They can do quite a bit more, like you said now they have security functions on them and just now the, you know, several different types of connectivity you can plug into them and now they're more intelligent and they can pick, okay, this voice traffic should go over this connection that you're running because this says lower jitter.
00:23:49.166 --> 00:24:00.611
And yeah, it's just, cuz like I said I think it's interesting to know where it's going in the future and I think it's a good idea for people to understand where it's gone through so far.
00:24:01.480 --> 00:24:03.371
So just wanted to chime in there.
00:24:03.701 --> 00:24:05.111
Yeah, no, I think that's a good point.
00:24:05.111 --> 00:24:13.411
I think that it has come quite a bit and I actually forgot that when Alex, when you and I worked at Evolve, they sort of got their own.
00:24:14.066 --> 00:24:16.131
They put out their own version of SD wan.
00:24:16.191 --> 00:24:18.141
It really, it wasn't called that at the time.
00:24:18.581 --> 00:24:23.026
But I, you know, speaking of Nate we, we you know, he was kind of working a lot with that.
00:24:23.115 --> 00:24:30.779
It was like evolves a little, I don't wanna say homegrown, I guess you wanna call it, it's probably the best word for it, but it was ba you know, I think they called it what the bonder or something.
00:24:31.190 --> 00:24:37.259
It was some terminology but it wasn't SD a at the time, but it basically served the same fun, the function, right.
00:24:37.259 --> 00:24:47.100
So, you know, we had customers that wanted to try it, and it basically just put two, two raw ISPs into this bonder, into a, you know, a glorified Linux box.
00:24:47.100 --> 00:24:47.101
Right.
00:24:47.500 --> 00:24:54.130
And it, you know, it made connections with the head end, which was, you know, evolve's data center at the time and then, you know, left from there.
00:24:54.134 --> 00:24:57.720
So Evolve was doing that, like, that was probably what, 2015, Alex?
00:24:57.720 --> 00:24:58.350
Something like that.
00:24:58.350 --> 00:24:59.970
So that was a little even before.
00:25:00.390 --> 00:25:04.170
Some of the, you know, the Estee WAN verbiage was out there and it was a buzzword.
00:25:04.170 --> 00:25:09.480
So, but yeah, so that was, you know, a cool little taste of, you know, how some of that worked and whatnot.
00:25:09.480 --> 00:25:14.640
And then, you know, in the last couple years, it's certainly, you know, Estee Wan has exploded to everybody.
00:25:14.644 --> 00:25:17.250
Everybody's got, it seems like everybody's got a flavor of Estie Wan now know.
00:25:18.810 --> 00:25:19.170
Right.
00:25:19.174 --> 00:25:19.370
Yep.
00:25:19.430 --> 00:25:19.850
For sure.
00:25:21.299 --> 00:25:26.730
So I guess some of the, I don't wanna get too into the details, but at a high level, right?
00:25:26.730 --> 00:25:33.441
So, yeah, most of the, you know, we talked about okay, so you're abstracting the brains from the actual boxes, right?
00:25:33.630 --> 00:25:36.380
The intelligence of the routers, switches, whatever it is.
00:25:36.690 --> 00:25:37.680
So where does that go?
00:25:37.740 --> 00:25:37.980
Right?
00:25:37.985 --> 00:25:43.085
So most of your SD WAN providers now are cloud-based, like the brain is in a cloud, right?
00:25:43.265 --> 00:25:45.005
I mean, you can host it yourself.
00:25:45.065 --> 00:25:48.195
I don't necessarily recommend it but you know, you can do that.
00:25:48.664 --> 00:25:53.630
But most of them, you know, like for example, Ciscos they host it in aws, right?
00:25:53.779 --> 00:25:56.029
And, you know, VeloCloud right?
00:25:56.250 --> 00:25:57.060
Does the same thing.
00:25:57.190 --> 00:25:58.674
Basically it's all cloud hosted.
00:25:58.674 --> 00:26:01.154
So, you know, Palo Alto, same deal.
00:26:01.154 --> 00:26:02.325
It's all cloud hosted.
00:26:02.330 --> 00:26:03.884
I think they do have versions.
00:26:03.884 --> 00:26:07.745
I think Cisco has a version of the Cisco Vitello is what they call it.
00:26:08.055 --> 00:26:12.380
You can do you can download like an ova, a VM machine to, to be the Marines.
00:26:12.380 --> 00:26:13.940
But is Cisco already hosted?
00:26:13.940 --> 00:26:15.980
Why, like, why, what's the point of that?
00:26:16.009 --> 00:26:20.029
So, so yeah, most of'em are gonna be cloud hosted, and then basically it's just all web based, right?
00:26:20.029 --> 00:26:25.250
You get in there through a gooey and start pointing and clicking and building, building your stuff.
00:26:25.299 --> 00:26:31.870
The main gist of it is you're basically taking I guess trying to formulate this better.
00:26:31.875 --> 00:26:43.205
So the you know, like I said if you have configurations that you're doing, you're basically then pushing it down to the actual devices via templates or whatever.
00:26:43.545 --> 00:26:48.740
And then also but that's, that communication is actually done over IP sec tunnels.
00:26:48.830 --> 00:26:49.759
So it's all encrypted.
00:26:50.180 --> 00:26:52.910
So you don't have any sort of real data hanging out there.
00:26:52.914 --> 00:26:54.860
It's all in ip sec tunnels.
00:26:55.310 --> 00:27:02.390
And then basically, if one site wanted to talk to another site, the head end or the brains isn't involved at all.
00:27:02.445 --> 00:27:04.965
They build automatic tunnels to each other.
00:27:05.535 --> 00:27:05.805
Right.
00:27:05.810 --> 00:27:11.860
So again, so that takes that back haul piece out of it, cuz you don't necessarily need it.
00:27:11.860 --> 00:27:14.170
It's intelligent enough to sort of know its own.
00:27:14.650 --> 00:27:18.880
Wan or its own neighbors, and then basically, Hey, I need to get to here.
00:27:19.160 --> 00:27:22.910
I'm gonna form automatic tunnel with you and, you know, off you go, sort of thing.
00:27:22.910 --> 00:27:32.990
So, some other terminology you'll sort of hear on, on, on as they're building or as the SD wan functions build their tunnels you'll hear an overlay and an underlay.
00:27:33.220 --> 00:27:35.519
So basically the underlay is the ISPs, right?
00:27:35.519 --> 00:27:37.650
The physical part of that.
00:27:37.680 --> 00:27:37.980
Right.
00:27:37.980 --> 00:27:44.970
And then the overlay is the actual tunnels that SD wan builds on top of the underlay.
00:27:45.299 --> 00:27:48.660
So they split it out into that particular, you know, terminology.
00:27:48.660 --> 00:27:59.210
So again, not to get too crazy into the weeds, but some of the g generic terms you'll hear when dealing with SD wan overlay and underlay are a big one controller, obviously the brains that, that's another big one.
00:27:59.549 --> 00:28:00.150
So just trying to.
00:28:00.945 --> 00:28:02.654
Piece, you know, some of this together.
00:28:02.654 --> 00:28:12.195
So, but yeah everything from a communication standpoint, whether you're going to the controller or to another actual S two RamBox it, it is all ip sec VPN tunnels.
00:28:12.195 --> 00:28:14.995
So, that's also you know, a big one there as well.
00:28:14.995 --> 00:28:19.625
So, Kyle, any questions with that or Alex any other questions?
00:28:20.810 --> 00:28:36.174
Well, you mentioned underlay and overlay and that was, those were terms I wanted to use earlier on, but I feel like some people, if they're not in this space, struggle with that concept cuz that is, especially for someone in networking who understands that's the easiest way to describe it really.
00:28:37.115 --> 00:28:51.195
And you mentioned IP sec and again, if people are in this space, might see a lot of similarities between like classic DMV VPNs and how these SD WANs function, at least underneath
00:28:51.250 --> 00:28:51.470
Yep.
00:28:52.394 --> 00:29:04.410
So I feel like a lot of this stuff, the SD WANs do that technology has been around for quite some time, but They've now made it much more accessible for people that are simply in it.
00:29:04.769 --> 00:29:09.000
I mean, you don't have to be some seasoned network engineer to support it.
00:29:09.000 --> 00:29:17.549
Now they've put a, you know, a fancy gooey and centralized it in one place, and now it's much more feasible for just about any organization to run it.
00:29:17.680 --> 00:29:17.900
Yep.
00:29:18.795 --> 00:29:19.065
Yep.
00:29:19.670 --> 00:29:19.890
But,
00:29:20.625 --> 00:29:24.845
and I think that's, that, that's a good point I think it, it facilitates a lot of things.
00:29:25.505 --> 00:29:29.970
Like you said the technology's been around there, been around the block for quite a bit.
00:29:30.360 --> 00:29:39.085
SD WAN just kind of, I think, puts a pretty coat of paint on it, and it makes it a little more, you know, a little more usable from a scalable, you know, perspective.
00:29:39.090 --> 00:29:44.285
So, and I don't know, Alex, I guess I'll get your your kind of take on this and, you know, maybe Kyle too.
00:29:44.644 --> 00:29:55.509
Do you think your company has to have a certain number of sites or a certain size to actually take to benefit from SD wan?
00:29:56.509 --> 00:30:02.778
Well, I'm not familiar with the SD WAN price models yet, so I don't know if there's much cost to entry.
00:30:02.778 --> 00:30:14.778
I would like to think, especially with SaaS models and some really cheap boxes that maybe that it's, you could make an argument to do it as soon as you have two or three sites that really need connectivity to each other.
00:30:15.528 --> 00:30:17.629
So I'm thinking, no, not really.
00:30:17.739 --> 00:30:25.538
It's probably still simpler to get an SD WAN solution than set up full mesh VPN n tunnels between three
00:30:25.764 --> 00:30:26.903
Or DMV P editor.
00:30:27.173 --> 00:30:27.504
Yeah.
00:30:28.149 --> 00:30:32.304
Certainly when you start talking about D VPNs and like failover solutions with that.
00:30:32.634 --> 00:30:34.974
Cuz then the failover solutions is the other thing too.
00:30:35.094 --> 00:30:40.594
Which really, if you're doing it classically with VPNs it starts getting really complicated.
00:30:40.594 --> 00:30:46.984
Like you have two ISPs and you don't own your own block and you have two different public IP addresses.
00:30:46.984 --> 00:30:50.544
Now you're several different tunnels and failure over dynamically.
00:30:51.663 --> 00:30:54.784
It starts, it just starts getting much more complicated.
00:30:54.784 --> 00:31:00.933
And then at that case, SD WAN is probably a much simpler solution.
00:31:00.939 --> 00:31:11.794
And if there's not a obvious financial drawback to, you know, like if, again, like the initial cost of just setting it up, if that's not there, yeah.
00:31:11.794 --> 00:31:15.124
I can't see a reason why you wouldn't consider it early on.
00:31:15.274 --> 00:31:17.824
But again, I'm not familiar with it, the.
00:31:19.084 --> 00:31:27.054
The companies that I've been with have either done it themselves at Evolve IP, or have been PlayStation in Disney, which you know, we're talking about scale.
00:31:27.054 --> 00:31:28.614
That obviously becomes
00:31:28.929 --> 00:31:29.199
Right.
00:31:29.814 --> 00:31:32.004
simpler to handle with an S D N solution.
00:31:32.739 --> 00:31:41.170
Yeah, I was kind of thinking that myself, like, you know, originally I thought, well, if you're kind of small, like I don't really see the point of like two or three sites doing SD wan.
00:31:41.379 --> 00:31:42.959
But again, if the money.
00:31:43.544 --> 00:31:46.544
Is not, if there's a low cost entry.
00:31:46.544 --> 00:31:46.933
Yeah.
00:31:46.933 --> 00:31:48.433
I wouldn't see why you wouldn't.
00:31:48.534 --> 00:31:56.544
But I'd be curious to see if anybody has any thoughts on that as like, is SD N meant for the larger enterprise because of its scale?
00:31:57.234 --> 00:31:59.564
You know, scaling abilities, right?
00:31:59.653 --> 00:32:05.644
I think that's probably one of its biggest pros is the you know, is the way to scale, right?
00:32:05.649 --> 00:32:22.054
So, you know, you're not necessarily, you know, there's no, you know, buy-in something from a vendor, having it shipped to an office, somebody configuring it and then reshipping it to wherever it needs to go, and then having somebody plug it in and blah, blah blah and all that.
00:32:22.054 --> 00:32:23.193
You know, we've all been there.
00:32:23.703 --> 00:32:28.594
Now with SD N you can basically, Ship it to wherever it's gonna go.
00:32:28.683 --> 00:32:33.724
Have somebody rack and stack plug it in, it calls home and it knows where to go.
00:32:33.784 --> 00:32:34.054
Right?
00:32:34.054 --> 00:32:38.433
That, that zero touch provisioning is also a large pro.
00:32:38.644 --> 00:32:38.943
Right.
00:32:38.949 --> 00:32:51.544
For that for the SDWAN stuff, and again, you can scale in a matter of, you know, you can spin these things up in a matter of minutes if you had everything ready to go, you know, from a template perspective before it actually got to where it's going.
00:32:51.814 --> 00:32:53.494
You know, had that template ready to go.
00:32:53.564 --> 00:33:05.494
Serial number boom, it plugs in, you know how plug however many legs you have in at these offices and off you go and it calls home and, you know, in a couple of minutes you're, you know, you got traffic flowing.
00:33:05.494 --> 00:33:22.044
So it's this whole mind shift from traditional legacy, you know, networking that we've, you know, we've all grown up on and loved, but it's it's definitely a shift in mindset and, you know, again, talking about the overlays, the underlays and all this terminology, right?
00:33:22.153 --> 00:33:28.324
Northbound southbound APIs and how it communicates with the controllers and all kinds of crazy stuff.
00:33:28.374 --> 00:33:36.689
It's some really it's a new day here in the networking world and it just feels like, it's some cool stuff and I'm I don't think it's done sort of growing up yet.
00:33:36.689 --> 00:33:39.629
I think that's the land's got some growing to do yet.
00:33:39.689 --> 00:33:41.609
But I definitely think it's heading in the right direction.
00:33:42.609 --> 00:33:43.028
Agreed.
00:33:43.849 --> 00:33:45.139
So, Kyle, anything for you?
00:33:45.199 --> 00:33:47.209
You're kind of out of the Estee Wan game, so,
00:33:47.979 --> 00:33:48.274
Yeah.
00:33:48.274 --> 00:33:48.693
A little bit.
00:33:48.693 --> 00:33:52.714
So, I mean, I'm hearing a lot of things that sound really interesting.
00:33:52.774 --> 00:33:53.374
Pretty cool.
00:33:53.384 --> 00:33:54.869
I haven't had a lot of hands on.
00:33:55.179 --> 00:34:04.658
There any cons, pitfalls that you've kind of come across in the Estie WAN realm versus you know, I guess maybe the more traditional legacy style.
00:34:06.368 --> 00:34:06.878
yeah.
00:34:06.878 --> 00:34:10.768
At least for me, I think and some are better at this than others.
00:34:10.827 --> 00:34:22.137
A and again, I think that goes back to Alex with the pricing sort of nomenclature saying, okay, look like, you know, these vendors that, that have stuff out there, like they're expecting you to have X amount of sites, so it's cost.
00:34:22.947 --> 00:34:25.152
Beneficial then you can justify that cost.
00:34:25.373 --> 00:34:34.873
So that's probably one I would say, Hey, you know, it, you know, depending on your infrastructure you know, depending on where that price breakpoint is, it may or may not be a good fit for some folks.
00:34:35.212 --> 00:34:42.862
The other thing I found too is if you're pushing like templates, I think they're good and bad at the same time.
00:34:43.163 --> 00:34:47.602
Like I think templates are great for things that are standard across the board, right?
00:34:47.692 --> 00:34:54.002
Your NTP servers, your DNS servers, S N M P things of that, you know, banner messages, things of that nature.
00:34:54.012 --> 00:35:02.512
Stuff that doesn't change or shouldn't change, I should say, from site to site, no matter what site you're at, all that stuff should be the same a across the boards.
00:35:02.962 --> 00:35:09.492
The other part of the templates is if your environment isn't quite right, or I should say isn't quite.
00:35:10.482 --> 00:35:17.772
At a space where it can be templatized, you have to sort of do like a one-off for like you can't.
00:35:19.542 --> 00:35:26.842
The templates aren't aren't flexible enough if you have one or two sites that are just a little different than the other ones.
00:35:27.022 --> 00:35:33.242
Now the goal there is to get those two or three sites, whatever they are you know, those outliers into that template, right?
00:35:33.242 --> 00:35:37.832
Get them structured enough so they can fit in a template and everybody's cookie cutter, right?
00:35:38.163 --> 00:35:49.322
But if you do have that environment where those, that wonder two sites is quite different for whatever reason, it just has enough to just to be annoying, you know, it needs to do something that all the others don't.
00:35:49.672 --> 00:35:56.572
You have to create a whole new template for that and basically do the whole thing over and then change your template to fit that site.
00:35:56.932 --> 00:36:00.682
And then that can kind of get into where you get into like template sprawl, right?
00:36:00.682 --> 00:36:10.062
So you have like a bunch of templates and, but the whole idea is to get your environment, get it towards a spot where everyone can be fed from the same.
00:36:10.547 --> 00:36:11.237
Template.
00:36:11.268 --> 00:36:16.457
I think that's probably a con, but that's more of a management sort of, you know, con with that.
00:36:16.697 --> 00:36:22.518
I've worked with different SD WAN flavors that some are easier to kind of set up.
00:36:22.627 --> 00:36:26.207
Things like q o s things of that nature.
00:36:26.477 --> 00:36:28.427
Some are better to set up that than others.
00:36:28.538 --> 00:36:37.577
So if you're not in a if you're with a vendor that doesn't make that easy, that can kind of become a, you know, a little bit of a rabbit hole sort of thing.
00:36:37.582 --> 00:36:40.587
So, it just depends on, you know, various things.
00:36:40.607 --> 00:36:51.262
But, I think the, under the underlying SD WAN product itself or what it's, you know what it does at a nuts and bolts, no matter who slaps a vendor name on it.
00:36:51.623 --> 00:36:52.643
I think it's good.
00:36:52.972 --> 00:37:02.042
It just depends on these vendors that they have their quirks depending on, you know, how much they actually give you eyes under the covers.
00:37:02.042 --> 00:37:02.252
Right.
00:37:02.252 --> 00:37:17.672
Because I've had places like and I don't know if this is still the way or not, but like when I was doing the velo cloud Sdwan stuff, they gave you very little visual or I should say a very little peak under the covers as far as like what happens in the back end.
00:37:18.212 --> 00:37:22.132
So you basically had control of your front end sdwan boxes.
00:37:22.462 --> 00:37:26.992
It magically left that sdwan box and showed up at the SDWAN box in your data center.
00:37:27.232 --> 00:37:31.282
You had no visibility in between the actual SD WAN boxes.
00:37:31.282 --> 00:37:36.143
Like you didn't have any visibility in the actual fabric into the cloud, right into that SD WAN cloud.
00:37:36.762 --> 00:37:42.192
So that made it a little hard trying to figure out, you know, troubleshooting and things of that nature.
00:37:42.282 --> 00:37:49.932
Now, on the other hand, the Cisco stuff, the Vitello, they give you full visibility from underneath the covers.
00:37:49.932 --> 00:37:53.082
So that is fully customizable from front to back.
00:37:53.202 --> 00:38:05.982
So the other part of that is, yeah, you get the visibility, that's great, but if you're not like well-versed enough in it, it can be daunting to be like, okay, am I doing this right cuz I'm seeing now all the under the covers things right.
00:38:05.987 --> 00:38:06.582
That sort of thing.
00:38:06.582 --> 00:38:11.742
So it can be overwhelming to kind of learn that, you know, all that piece, all the way from A to Z.
00:38:13.507 --> 00:38:13.837
Okay.
00:38:15.163 --> 00:38:17.232
Yeah, and I'll probably add.
00:38:17.937 --> 00:38:25.607
That vendor interoperability is probably quite a bit harder if you're talking about an Sdwan n solution.
00:38:26.268 --> 00:38:32.087
Cause you know, you can create an IP sec tunnel between a thousand different vendors.
00:38:32.092 --> 00:38:38.018
But trying to get a vitel to work with silver Peak or 40 Net or something like that,
00:38:38.157 --> 00:38:38.937
That's a good point.
00:38:39.277 --> 00:38:40.837
WAN solution is a whole different ballgame.
00:38:41.737 --> 00:38:47.087
So, I haven't run into it enough, so I'm sure there's solutions out there cuz I'm sure they've come across it.
00:38:47.087 --> 00:38:57.588
Like, if you acquire a new company and they have a thousand vitelli nodes and you're rocking and VMware Ello cloud, now there's gotta be some way you can integrate them.
00:38:58.108 --> 00:39:12.308
That would be my thought is vendor interoperability might be a bit more difficult and Probably a bit harder to move off a vendor, but it seems like most people tend to stick with one vendor anyway, so that's probably not a major deal breaker for a lot of people.
00:39:12.563 --> 00:39:18.203
Yeah, the only place I would think of where the vendor interoperability comes with is like a merger or an acquisition.
00:39:18.983 --> 00:39:27.553
Like you said, you know, if you're a, if you're a thousand, thousand shop Vitello and you Yeah, you buy a shop that has 48, like, you know, okay, what do you, yeah.
00:39:27.583 --> 00:39:29.023
How do you blend those two together?
00:39:29.114 --> 00:39:29.353
Right?
00:39:29.413 --> 00:39:36.768
So I think that's probably the, where they see the most, you know, hills, if you will, from a, from an interoperability, you know, perspective.
00:39:36.798 --> 00:39:48.168
But the other thing I was kind of talk thinking about too is, you know, like there are some security tools out there that they have that the Sdwan boxes are sort of, you know, now coming built in, if you will.
00:39:48.558 --> 00:39:52.958
You know, but like, what are the other security tools that you have to integrate with them?
00:39:53.048 --> 00:40:03.953
Like I think there's some shortfalls around that as far as trying to get it in the, you know, operate that sdwan box operating within your existing security stack, right?
00:40:04.183 --> 00:40:05.393
Or other sort of tools, right?
00:40:05.453 --> 00:40:14.263
So whether that's a scene tool or, you know, like a Splunk or, you know, things of that nature, like how does that all, you know, integrate as well?
00:40:14.263 --> 00:40:18.253
So there, there may be some, you know, maybe some pitfalls there.
00:40:18.453 --> 00:40:23.199
The visibility, right, that we talked about before, I mentioned a few minutes ago that that's a big one.
00:40:23.298 --> 00:40:25.248
As well, especially for the security side, right?
00:40:25.248 --> 00:40:29.268
You really don't have a whole lot of that, you know, visibility, you know, things of that nature.
00:40:29.268 --> 00:40:30.348
So, but yeah.
00:40:30.348 --> 00:40:36.063
Hey, who, yeah, who knows, maybe there's some they're developing some stuff and you know, that sort of gets gets better every day.
00:40:36.063 --> 00:40:37.743
So it's it's an interesting.
00:40:38.178 --> 00:40:42.638
You know, take on, it just depends on, you know, where we see it going in the next couple years.
00:40:42.638 --> 00:40:43.888
But I it's definitely here.
00:40:43.938 --> 00:40:45.588
It's a, it's an everyday thing.
00:40:45.588 --> 00:40:52.009
It's, you know, it's not just a fringe, Hey, larger corporations can't afford it cuz they're throwing money at it sort of thing.
00:40:52.013 --> 00:40:52.923
It's here for everybody, I think.
00:40:52.943 --> 00:40:56.443
And then I think it's got some really good some really good pros to it.
00:40:57.443 --> 00:40:58.703
Kyle, you got anything else?
00:40:59.643 --> 00:41:00.823
That was that was what I had for
00:41:00.973 --> 00:41:01.273
Cool.
00:41:01.723 --> 00:41:02.053
Cool.
00:41:02.203 --> 00:41:14.663
So just some vendors I wanna throw out there for you know, we, we've been talking about like I said, VeloCloud Palo Alto has a, has their own sdwan now which Palo Altos are nice cuz they don't require a separate SD WAN box.
00:41:14.963 --> 00:41:16.193
It all works within their.
00:41:16.763 --> 00:41:18.083
Next Generation firewall.
00:41:18.153 --> 00:41:23.903
So if you have, if you're already on Palo Firewalls, it's just a, it's a plugin for their firewalls, which is kind of nice.
00:41:23.963 --> 00:41:27.563
Silver Peak is the I think Silver Peak was one of the first ones to the game.
00:41:27.683 --> 00:41:29.028
So they're always popular.
00:41:29.388 --> 00:41:32.208
And then Cisco Vitello you know, it's always a good one.
00:41:32.208 --> 00:41:44.058
So obviously Vitello was a standalone company and then Cisco came and bought them a few years ago, so now they just, they, you know, they basically called Cisco Vitello, so it's they slapped their name on it and off they go.
00:41:44.268 --> 00:41:45.228
I'm trying to think of what else.
00:41:45.768 --> 00:41:46.978
Like, some use cases,
00:41:47.408 --> 00:41:48.458
Val Cloud.
00:41:49.088 --> 00:41:49.378
Yeah.
00:41:50.378 --> 00:41:51.368
that'd be about it.
00:41:51.373 --> 00:41:52.688
Those are the big ones, at least.
00:41:53.688 --> 00:41:53.928
Yeah.
00:41:53.928 --> 00:41:58.278
And like you said, at this point it's kinda like streaming services.
00:41:58.278 --> 00:42:01.698
You got a few guys that kind of run the show, but everyone's doing it.
00:42:03.288 --> 00:42:03.558
Yep.
00:42:03.858 --> 00:42:04.068
Yep.
00:42:04.578 --> 00:42:07.698
So, just a couple of key takeaways from the SD WAN stuff.
00:42:07.798 --> 00:42:11.969
You know, that we kind of spewed out here in no, no particular order.
00:42:12.028 --> 00:42:19.858
But basically SD WAN is the, you know, it's a WAN technology with a virtualized, you know, again, here's that term overlay, right?
00:42:20.198 --> 00:42:24.009
It's basically abstracting the software, you know, from the hardware, right?
00:42:24.009 --> 00:42:31.393
So you're, again, taking the central, you're taking the brain off the actual individual box and putting it into a centralized location, right?
00:42:32.033 --> 00:42:34.948
Controller you know, that's the technical, you know, term for it.
00:42:34.953 --> 00:42:38.118
So, again network abstraction, right?
00:42:38.148 --> 00:42:42.438
Land virtualization, policy driven, centralized management, right?
00:42:42.438 --> 00:42:45.888
You can do all kinds of crazy policies with how you wanna do traffic, right?
00:42:45.888 --> 00:42:47.509
So, again, q o s is a big one.
00:42:47.848 --> 00:42:55.958
You know, with VoIP, obviously being around the last oh geez, seems like a billion years yeah, you gotta make sure that traffic is prioritized, things of that nature.
00:42:56.198 --> 00:43:08.239
You know, and it again, it scales, scales, scales very well from a, you know, both from a local perspective of, Hey, you wanna get a third leg in there, or if you can get a third I s p, great, you know, whatever.
00:43:08.628 --> 00:43:10.308
Or from a site perspective, right?
00:43:10.313 --> 00:43:18.083
You all of a sudden now you bought somebody and now they're, you know, they're, they got 50 sites across the states, you can get'em on your wan tomorrow, right?
00:43:18.103 --> 00:43:30.163
You know, in a relatively, you know, short amount of time versus, you know, the old school way of, you know, configuring 50 different routers and sending'em out and getting all that stuff you know, scheduled and all that kind of crazy stuff.
00:43:30.163 --> 00:43:33.513
So, You know, there, there's various ways to architect it, right?
00:43:33.513 --> 00:43:34.864
So it can be cloud-based.
00:43:34.864 --> 00:43:37.923
Most of them, most of the controllers, like I said, are cloud-based.
00:43:37.923 --> 00:43:42.353
Or you can do it on-prem you can technically do a cloud and an on-prem if you wanted to.
00:43:42.503 --> 00:43:44.158
But the way I've seen it done is amazing.
00:43:45.018 --> 00:43:48.618
Basically, the controller part, the brains part is all in the cloud.
00:43:48.888 --> 00:43:52.989
And those those boxes just point there to a p from a public IP perspective.
00:43:52.989 --> 00:43:55.568
So, you know, you're reducing CapEx, right?
00:43:55.568 --> 00:43:58.028
So, you know, hardware, things of that nature.
00:43:58.138 --> 00:44:03.478
There's no need of, there's really no need for specialized equipment, you know, anymore, that sort of thing.
00:44:03.478 --> 00:44:06.108
So, you know, it can terminate all kinds of different.
00:44:06.478 --> 00:44:08.578
Internet providers, you know, internet types, right?
00:44:08.578 --> 00:44:19.678
So again, your fibers or metro E or regular broadband wireless 5G for LT fi, 5G, wireless it's got stuff for all of it.
00:44:19.678 --> 00:44:24.158
So, and it's just a better way to simplify management, right?
00:44:24.158 --> 00:44:26.518
It's just you get better visibility with that.
00:44:26.518 --> 00:44:31.413
You could see, you know, again the big three that it, it looks at these legs, right?
00:44:31.413 --> 00:44:35.783
Or each I s P is packet loss, latency and jitter, right?
00:44:35.788 --> 00:44:46.493
So that's you know, it's constantly measuring those three things from each internet circuit and then makes its intelligent decision on where to send that packet or when it comes in, or which leg to send it over.
00:44:46.493 --> 00:44:49.373
So, at least in the Vitello world each.
00:44:50.573 --> 00:45:01.323
I'm gonna say each I s P has its own tunnel, so again, it makes, is, it makes connections to both the controller and other SDM boxes over IP sec.
00:45:01.634 --> 00:45:05.233
And then it makes a tunnel over each interface as well.
00:45:05.233 --> 00:45:12.009
Each provider gets a, gets an own its own isp, so it handles failover seamlessly.
00:45:12.348 --> 00:45:18.708
Like for example, if you have two ISPs going into an SDWAN box and one fails, the end user has no idea.
00:45:18.768 --> 00:45:21.094
The SD WAN automatically I don't know, it's a bundle.
00:45:21.233 --> 00:45:23.956
It, It's probably that's the simplest word for it.
00:45:23.956 --> 00:45:27.476
But it's basically taking those two ISPs and making it one big pipe.
00:45:27.777 --> 00:45:32.516
And then basically if the I S P goes down it then ju it.
00:45:32.861 --> 00:45:38.351
Senses that, and then doesn't, you know, it drops that from its table and the end user has no idea.
00:45:38.351 --> 00:45:41.531
So, and then when it comes back up, it just brings it back into the fold.
00:45:41.531 --> 00:45:43.781
And again, the end user has no idea.
00:45:43.781 --> 00:45:45.371
So failover is seamless.
00:45:45.442 --> 00:45:47.781
Not noticeable, which is always a big one.
00:45:47.991 --> 00:45:54.038
Cuz in the old days, right, the old land days you know, you're usually running some sort of internal like routing protocol.
00:45:54.147 --> 00:45:56.812
Over the popular one in NPLS land is bgp.
00:45:57.262 --> 00:46:07.163
So if you're running bgp, then just the nature of BGP and how slow it is till it fails and then until it, you know, till the timers run out and all this stuff, like, there's a hiccup there.
00:46:07.163 --> 00:46:08.393
People are gonna notice, right?
00:46:08.572 --> 00:46:10.663
With SD wan it's seamless.
00:46:10.663 --> 00:46:11.652
It, they have no idea.
00:46:11.657 --> 00:46:18.252
It fails over that quickly and it just basically takes that leg out of the SD wan fabric and keeps the other good legs in.
00:46:18.252 --> 00:46:21.852
So, like for example, I was at a place once that they had two ISPs.
00:46:23.697 --> 00:46:30.557
Into an SDWAN box, and then they did a 5G lte, or I should say whatever the wireless was, the L LTE e at the time.
00:46:31.077 --> 00:46:39.087
And then they had a policy in SDWAN to say, okay, look, use these two ISPs first, only use this LTE as an absolute failover.
00:46:39.087 --> 00:46:42.268
It's, if it's the only game in town, that's the only time you use it, right?
00:46:42.268 --> 00:46:49.917
So you can write policy that way as well to say, you knows kind of traffic shape and policy-based routing, things of that nature.
00:46:49.917 --> 00:46:53.397
So, you know, so that's the flexibility there, you know, you know, as well.
00:46:53.402 --> 00:46:58.687
So, or you know, I've been to places that have one I s P and an m ms MPLS link in there.
00:46:58.687 --> 00:47:06.847
And yeah, you basically route your phone traffic or web traffic over the pls and use the i p as a failover and all the other internet traffic.
00:47:07.222 --> 00:47:08.862
It just goes out the the I s P.
00:47:09.222 --> 00:47:14.712
So, you know, there's multiple ways to really, you know, benefit from that from that policy-based routing stuff.
00:47:14.712 --> 00:47:22.462
So, but yeah, I think the visibility, the simplified management really goes a long way with the SDWAN stuff, cuz it, you know, the reduced cost, right.
00:47:22.522 --> 00:47:25.682
You know, we just find cost savings all over with that.
00:47:25.922 --> 00:47:29.272
And then, like Alex said, there's less you know, less vendor lock-in.
00:47:29.362 --> 00:47:29.542
Right?
00:47:29.542 --> 00:47:38.503
You don't have to rely on a vendor all the way through to, you know, most people stick with one vendor, but you ne you don't necessarily have to, you can spread that out a little bit.
00:47:38.802 --> 00:47:40.482
You know, so that's interesting as well.
00:47:40.482 --> 00:47:44.502
So I'm curious to see where it goes from a security perspective.
00:47:44.652 --> 00:47:46.422
Like it, it has a firewall.
00:47:46.482 --> 00:47:53.732
Most of'em have a firewall built into them and can give you that visibility of, you know, logs and things of that nature.
00:47:53.737 --> 00:47:57.498
But I think there's a lot more there to really tap into from a security perspective.
00:47:57.498 --> 00:48:02.268
don't know if Alex or Kyle have anything to kind add to that, but I'm curious to see where that goes in the next couple of years.
00:48:03.268 --> 00:48:05.367
I'm talking specifically about security.
00:48:05.607 --> 00:48:12.947
Yeah, just from a security perspective on the SD wa boxees say, you know, like, like they have them now, but you don't know how good they are, that sort of thing.
00:48:12.947 --> 00:48:14.463
Like, they're there, they get it.
00:48:14.463 --> 00:48:25.493
But, you know, I'm curious to see if, you know, if it can if it has any more beef when it comes to the security stuff like deep packet inspection or any of that kind of crazy stuff that some of the NextGen firewalls have today.
00:48:27.173 --> 00:48:29.893
Well, I'm sure it'll keep getting better and better.
00:48:30.433 --> 00:48:34.243
I mean, will it eventually replace a full on firewall?
00:48:34.844 --> 00:48:38.233
Maybe for like the rural small business that will be sufficient.
00:48:38.833 --> 00:48:52.364
I think it's much more likely that you'll just end up doing what Palo Alto is doing, which is you'll buy Palo Alto because you want a firewall and then utilize SD WAN as an add-on as opposed to firewall being the add-on to the SD WAN product.
00:48:52.588 --> 00:48:52.798
Right.
00:48:53.713 --> 00:49:01.423
And I'm kind of out of the out of touch with some of the more recent security technologies out there.
00:49:01.423 --> 00:49:11.773
And yeah, maybe, I don't know if anyone here talking with us today like you or like, I can't even think of his name.
00:49:11.773 --> 00:49:15.683
What was the guy that was just on our conversation like two weeks ago or three weeks ago.
00:49:16.103 --> 00:49:23.463
But maybe we should ask people like that what the next security feature will be and then I'll be curious if SD WIN is gonna support it.
00:49:24.408 --> 00:49:30.888
Yeah, that's an interesting take to see what that, I really like what Palo Alto's doing with the, there's no separate box for that then.
00:49:30.893 --> 00:49:32.148
So that's, you're spending less on
00:49:32.418 --> 00:49:32.808
Yeah,
00:49:32.838 --> 00:49:33.739
it's just a plugin.
00:49:33.918 --> 00:49:40.368
because I think generally, so anytime you're talking about security aisle, at least in my head, I'm thinking about deep inspection.
00:49:40.373 --> 00:49:52.248
And deep inspection is just so processor intensive and you feel like you need so much beef to do that, that's almost the opposite of what the SD WAN is trying to do, which is trying to be like a lightweight thing.
00:49:52.848 --> 00:49:54.398
And that's, yeah.
00:49:54.403 --> 00:50:04.653
That's why I think that it'll eventually, it'll become a limit to what these SD WAN devices can do, because that's not their immediate thought process, so,
00:50:05.973 --> 00:50:07.943
Yeah, no, it's a good it's a good point.
00:50:07.943 --> 00:50:10.853
And I, so just a selling point for Palo Alto.
00:50:10.913 --> 00:50:11.223
You know,
00:50:11.533 --> 00:50:11.823
Yeah.
00:50:12.463 --> 00:50:15.489
Yeah, again, you're not using, you know, you're not buying separate boxes.
00:50:15.489 --> 00:50:17.378
It's just a plugin for the Palo stuff.
00:50:17.378 --> 00:50:20.739
And Palo's app Id carries all the way through the Sdwan.
00:50:20.858 --> 00:50:25.239
So you see that app Id, you see that traffic all the way through their fabric, which is really nice.
00:50:25.388 --> 00:50:31.808
So it's really nice when it comes to troubleshooting and trying to find out, you know, who you know, who.
00:50:32.993 --> 00:50:37.543
What's eaten the packet and all this kind of stuff and you know, trying to track a lot of that traffic and whatnot.
00:50:37.543 --> 00:50:46.303
So again, you know, depending on vendor, you may, you know, once it leaves that SD wan edge, you may not see it until it comes to the other end.
00:50:46.493 --> 00:50:50.893
And if it never gets to the other end, then you don't know what's eating it inside the SD WAN fabric.
00:50:50.953 --> 00:50:57.473
So, pal, you know, Pao does a nice job of, you know, it's, it gives you visibility all the way through.
00:50:57.833 --> 00:51:02.483
And the their app ID feature follows it all the way through as well, keeps it intact, which is nice.
00:51:02.483 --> 00:51:04.969
So plus one for the boys over there at Palo.
00:51:04.969 --> 00:51:07.847
So, always a good always a good product from them.
00:51:07.907 --> 00:51:11.417
I've always had a good experience with Palo, so, Yeah, that was kind of it.
00:51:11.417 --> 00:51:12.977
That was kind of my spiel.
00:51:12.977 --> 00:51:14.237
I didn't wanna get too crazy.
00:51:14.297 --> 00:51:25.347
Technical, I mean, there's, you can certainly deep dive into Estee Wan for, you know, for days upon days, but just to, for those that may not be familiar with it, or maybe just getting into the field.
00:51:25.407 --> 00:51:33.992
I feel like Estee Wan was a good topic cuz it's everywhere, or at least you'd say it's a lot of places it's really starting to, you know, creep into more places.
00:51:33.992 --> 00:51:37.492
Like we said, you know, all sizes of business and things of that nature.
00:51:37.552 --> 00:51:43.862
So I feel like it was a good time to talk to the Sdwan stuff and and kind of give you the 50,000 foot view.
00:51:43.932 --> 00:51:52.422
But if you're looking for more, certainly like we said, VeloCloud, Palo Alto, silver Peak, Cisco Vitello, you take a couple flyers on those.
00:51:52.663 --> 00:51:54.292
I mean, just SD WAN as a.
00:51:54.957 --> 00:51:56.768
As a technology.
00:51:56.768 --> 00:52:02.257
It's, you know, it's agnostic to, you know, to all those couple of things I just mentioned, those vendors I just mentioned.
00:52:02.597 --> 00:52:14.307
If you wanna really learn how the nuts and bolts work you know, I'll post a couple links in the show notes if you wanna take a peek at those and see what you just really kind of dive in and, you know, roll your sleeves up and whatnot.
00:52:14.307 --> 00:52:26.989
So, but I thought it was a good topic and to give you a 50,000 foot view and I would assume those breaking in now they're gonna at least find you know, sdwan somewhere along their careers and, you know, quite early I would think.
00:52:26.993 --> 00:52:28.197
Cause it's here now to stay.
00:52:28.207 --> 00:52:30.518
It's not a fringe technology anymore.
00:52:30.518 --> 00:52:32.913
People are really kind of diving into this yeah.
00:52:32.922 --> 00:52:33.702
With both feet.
00:52:33.702 --> 00:52:36.377
So, Kyle, anything else from you or Alex.
00:52:37.377 --> 00:52:45.987
Well, I was going to close with something we often close with, and you already touched on it when we said security, and we talked about it a little bit earlier.
00:52:45.987 --> 00:52:51.212
But outside of security, is there anything else you see as like the future of SD wan?
00:52:52.292 --> 00:52:55.592
I would say the.
00:52:56.492 --> 00:52:59.772
Kind of adaptation into the hybrid cloud things.
00:53:00.242 --> 00:53:07.172
They're really, I think there's some cool things that they're doing now with some of their onboarding and like multi-cloud things of that nature.
00:53:07.232 --> 00:53:09.542
I know with the Cisco stuff they call it on-ramp.
00:53:09.623 --> 00:53:12.652
So basically you're, if you're in the multi-cloud game, right?
00:53:12.652 --> 00:53:15.623
The, if you're in a AWS and Azure, right?
00:53:15.623 --> 00:53:18.307
So, Cisco does they call it Cloud OnRamp.
00:53:18.447 --> 00:53:24.788
And basically it's just a, it's like we had it we actually had it already spun up in the cloud.
00:53:25.268 --> 00:53:29.538
I took a flyer on it, like I saw it later after the, after all the hard part was done.
00:53:29.867 --> 00:53:36.207
But basically what they do is if you want to do an on-ramp a cloud on-ramp, it basically builds the whole thing for you.
00:53:36.207 --> 00:53:44.547
All you basically do is tie your cloud ID if you will the tenant IDs and things of that nature to your vitello controller.
00:53:44.877 --> 00:53:50.167
And basically then Vitello goes out and It builds the networks and everything right around it.
00:53:50.167 --> 00:53:51.687
And you don't really have to do anything.
00:53:51.788 --> 00:53:54.367
It builds it all right from a push of a button.
00:53:54.437 --> 00:53:56.327
They do it via like a workflow, right?
00:53:56.327 --> 00:54:03.408
So it's just boom, you know, spinning up the vnet, carving out a subnet, spinning up the VM that's gonna support the sdwan box.
00:54:03.487 --> 00:54:03.777
Boom.
00:54:04.007 --> 00:54:05.917
You know, and it's, you know, it's done.
00:54:06.097 --> 00:54:08.717
So, I probably should have looked at that a little earlier.
00:54:09.207 --> 00:54:09.567
I did.
00:54:09.657 --> 00:54:12.087
I did it the hard way and spun it up myself manually.
00:54:12.087 --> 00:54:16.817
But it's just me being sort of a rookie when it comes to some of the cloud stuff.
00:54:16.817 --> 00:54:21.498
I'm probably at this point working harder, not smarter, but, you know, hopefully someday that may change.
00:54:21.822 --> 00:54:23.057
So I don't know.
00:54:23.387 --> 00:54:26.257
But Yeah, they basically make that on-ramp process real easy.
00:54:26.587 --> 00:54:32.227
And then if you're working in multiple clouds, they have a hook in, somewhere in the backend.
00:54:32.857 --> 00:54:37.297
It's still kind of fuzzy to me, but somewhere in the backend, they basically can hook the two.
00:54:38.362 --> 00:54:51.842
say say if I was an AWS and Azure you know, and you spun up a, an SD RamBox in both there's somewhere on the back end where it's, they can sort of blend those two clouds together and fail over and all kinds of crazy stuff.
00:54:51.847 --> 00:54:56.097
So I, I see some cloud stuff really kind of taken off with the with the sdwan stuff.
00:54:56.097 --> 00:55:04.527
So curious to see what that looks like in the next couple of years and how they sort of really integrate that more and get that visibility across, especially across multi-cloud.
00:55:04.527 --> 00:55:07.597
Cause I think a lot of people are looking at multi-cloud now.
00:55:07.597 --> 00:55:13.177
So I think again, that, that's that vendor interoperability that we talked about a little bit ago.
00:55:13.177 --> 00:55:16.147
Like, how do you make Azure work with AWS and vice versa.
00:55:16.147 --> 00:55:21.917
And so I think some of them are sort of bringing everybody to the table and, you know, kind of being the peacemaker there.
00:55:21.917 --> 00:55:23.447
So curious to see how that goes.
00:55:25.022 --> 00:55:25.312
Yeah.
00:55:26.102 --> 00:55:26.393
Okay.
00:55:27.652 --> 00:55:29.362
Let's see if there's anything else.
00:55:29.413 --> 00:55:36.102
Well, it's a common theme just about anytime we have any technology, we'll talk about machine learning and ai.
00:55:36.832 --> 00:55:44.842
Cuz you kind of go back to one of the fundamental things that we talked about that Sdwan could do is it can intelligently route traffic over different connections that you have.
00:55:44.842 --> 00:55:56.032
So the simplest example we can give people is probably talking about voice, which is really jitter dependent, like high jitter not good for voice.
00:55:56.038 --> 00:56:05.002
So if it sees a low jitter path, you know, SD WANs today can move traffic over intelligently to maybe a path that has less jitter.
00:56:05.002 --> 00:56:16.332
But I'm sure that'll just continue to get much more advanced to the point where it's gonna any application and not something that's just specifically voice.
00:56:16.332 --> 00:56:27.032
It's any application it's gonna have much more information and just be able to better route traffic across the links that are better suited for application X, y, Z for whatever reason that may be.
00:56:27.602 --> 00:56:29.702
So I'm sure that'll just continue to evolve and.
00:56:30.722 --> 00:56:34.352
And I don't deal with SDN all the time.
00:56:34.352 --> 00:56:42.302
So I know when I was dealing with a lot, that was very manual process and it's probably much, so much less so the case today.
00:56:42.302 --> 00:56:48.082
And by manual process, I mean getting like specific applications to go over certain links.
00:56:48.862 --> 00:56:53.692
So just to where that gets to the point where it's just automatically doing that intelligently.
00:56:53.962 --> 00:56:55.582
It'd be interesting to see where that goes.
00:56:56.422 --> 00:57:03.682
The only anything else would probably be interested to see automation when it comes to SD win.
00:57:03.682 --> 00:57:24.132
You touched on it a little bit, how to, it could automatically deploy an environment, but similar kind of concept where it can, it, can it control or automatically deploy itself in another cloud region to accommodate your already existing automation strategy, which might be spin up x amount of boxes if we need it, but.
00:57:24.582 --> 00:57:30.932
Now there's an SD WAN component to it also, cuz you need to have to touch base with the data center that you have.
00:57:30.932 --> 00:57:42.373
So, piecing SD WAN into this just broader automation that everyone's trying to do, be interesting to see what they can accomplish with that.
00:57:43.152 --> 00:57:45.672
Yeah, I think a lot of automation is already sort of here.
00:57:45.732 --> 00:57:47.532
And I'll kind of touch on a little bit.
00:57:47.532 --> 00:57:52.992
It's not Sdwan, but it's that software defined networking and that it's in the same family.
00:57:53.393 --> 00:57:56.182
Cisco's DNA center right, is a big one with that as well.
00:57:56.187 --> 00:58:04.052
Again, very, you know, gooey driven, template driven, all your switches are the same, you know, things of that nature.
00:58:04.052 --> 00:58:11.217
And they give you a spot where you can, you know you can basically run scripts and push'em down and all kinds of stuff.
00:58:11.222 --> 00:58:16.707
And, you know, again, the automation and the workflows and sort of how they have that, you know, there.
00:58:16.707 --> 00:58:23.672
So, you know, DNA center's doing a lot of that already, and I'm sure Estee Wan is not that far behind with a lot of that.
00:58:23.893 --> 00:58:38.663
You know, the automation stuff, the Python scripts, Ansibles again, all North and southbound you know, API stuff and you know, getting Intel from your boxes on, you know, depending on whether you, how you wanna do it, you know, most popular by api you know, things of that nature.
00:58:38.663 --> 00:58:48.862
So yeah, I'm curious to see how that rolls over the next couple of years as well as you know, some of the automation stuff and taking the taking the intelligence game one step one or two steps further.
00:58:49.862 --> 00:58:52.022
So Kyle, anything else from you otherwise?
00:58:52.022 --> 00:58:55.582
We'll we'll get outta here and we're right around that hour mark, so it's always good.
00:58:56.582 --> 00:58:58.772
No, that's pretty that covers it pretty much for me.
00:58:58.777 --> 00:59:02.268
I'm the newbie here, so I'm I'm learning a lot right on the, on
00:59:02.357 --> 00:59:06.257
So, so what you're saying is you're gonna go to your boss tomorrow and be like, yo, we need Estee Wan.
00:59:06.377 --> 00:59:07.157
Like today.
00:59:08.072 --> 00:59:08.822
Most certainly.
00:59:09.947 --> 00:59:11.297
Be like, I got a guy.
00:59:12.297 --> 00:59:12.987
Well, that's awesome.
00:59:12.987 --> 00:59:14.187
So, all right buddy.
00:59:14.187 --> 00:59:15.748
Thanks for joining this week.
00:59:15.807 --> 00:59:19.308
We will wrap it up here for you on this I thought it was a good episode on SD wan.
00:59:19.313 --> 00:59:21.667
So it's everybody's got any questions certainly hit us up.
00:59:21.667 --> 00:59:26.127
We like helping y'all out and making the picture a little clearer so everybody's got any questions.
00:59:26.127 --> 00:59:27.117
Certainly let us know.
00:59:27.123 --> 00:59:28.498
We're all over social media.
00:59:28.498 --> 00:59:31.407
Everybody can find our stuff in the show notes.
00:59:31.407 --> 00:59:32.652
All of our socials are there.
00:59:33.062 --> 00:59:34.862
So yeah, there's multiple ways to get ahold of us.
00:59:34.862 --> 00:59:39.582
So, obviously make sure you visit our website, breakingbytespod.io.
00:59:40.032 --> 00:59:44.123
can subscribe to the show right from there on multiple platforms.
00:59:44.232 --> 00:59:47.312
Or if you just need an RSS feed that's there as well.
00:59:47.312 --> 00:59:50.913
So you'll never miss a show Nosa rating on the Apple Podcast.
00:59:51.332 --> 00:59:54.503
That would be great if you still simply tell a friend too.
00:59:54.509 --> 00:59:57.942
That's always good word of mouth works just as well these days.
00:59:57.942 --> 01:00:03.373
So, again, LinkedIn, Twitter, Instagram, Facebook there's a Discord server out there.
01:00:03.373 --> 01:00:04.962
The surveys still hanging out there.
01:00:05.302 --> 01:00:06.922
All of that stuff's in the show notes.
01:00:06.972 --> 01:00:10.727
I'll put a couple of links that we talked about SD WAN stuff today.
01:00:10.947 --> 01:00:13.167
I'll put that in the show notes there as well.
01:00:13.197 --> 01:00:14.492
And that's it boys.
01:00:14.702 --> 01:00:17.672
Another good episode and we'll, Alex, you got a guest next week.
01:00:17.672 --> 01:00:18.812
I think we got somebody coming on.
01:00:18.812 --> 01:00:21.123
An old friend of ours, if I'm not mistaken.
01:00:22.893 --> 01:00:23.182
Yeah.
01:00:23.623 --> 01:00:29.502
Like we've said before, it comes up a lot, but another conversation on AI machine learning.
01:00:29.652 --> 01:00:35.862
I'm sure chat G P t will be mentioned, but it's the most interesting thing out there, so why
01:00:35.952 --> 01:00:36.768
that That it is.
01:00:36.772 --> 01:00:37.067
All right.
01:00:37.127 --> 01:00:39.893
So we're not gonna tell you his name but so you gotta tune in for that.
01:00:39.893 --> 01:00:46.387
So, tune in next week for some cool AI discussions with our a good buddy of ours that Alex and I used to work with.
01:00:46.387 --> 01:00:47.768
That seems to be a theme here at the show.
01:00:47.768 --> 01:00:49.597
We're just bringing everybody back and it's all good.
01:00:49.597 --> 01:00:51.697
So, all right, buddy.
01:00:51.727 --> 01:00:52.807
We'll see you next week.
01:00:53.018 --> 01:00:53.377
Thanks.