WEBVTT

1
00:00.000 --> 00:09.000
Finally, let's take a look at using DIA links at a co-location.

2
00:09.000 --> 00:13.960
Now this is going to be very, very similar to using a gateway site.

3
00:13.960 --> 00:15.960
So this is going to be a very quick discussion.

4
00:15.960 --> 00:18.760
We just want to talk about some of the subtle differences.

5
00:18.760 --> 00:22.890
Other than that, the forwarding is going to be handled pretty much the same way

6
00:22.890 --> 00:23.000
.

7
00:23.000 --> 00:28.720
Let's go ahead and take a look at some of those minor changes.

8
00:28.720 --> 00:35.320
So the basic idea behind this design is we're going to now use a regional hub
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:28.720 --> 00:35.320
So the basic idea behind this design is we're going to now use a regional hub

9
00:35.320 --> 00:36.440
that has direct

10
00:36.440 --> 00:38.320
internet access.

11
00:38.320 --> 00:43.360
The branch sites then connect to that regional hub for their internet

12
00:43.360 --> 00:44.560
connection.

13
00:44.560 --> 00:49.560
So in this example, the branch sites don't have their own internet connection.

14
00:49.560 --> 00:52.960
Although truth be told, they really still could.

15
00:52.960 --> 00:56.400
That's just not really part of this particular design.

16
00:56.400 --> 01:00.960
And sort of the way it gets its name is oftentimes companies are going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:56.400 --> 01:00.960
And sort of the way it gets its name is oftentimes companies are going to

17
01:00.960 --> 01:02.640
choose to host these

18
01:02.640 --> 01:11.640
hubs at either a co-location or a CNF, which is a carrier neutral facility.

19
01:11.640 --> 01:16.630
Usually places that carry multiple different providers that we can use for that

20
01:16.630 --> 01:17.280
internet

21
01:17.280 --> 01:18.720
access.

22
01:18.720 --> 01:25.380
So then this is as simple as deploying SD-WAN edge routers at these regional

23
01:25.380 --> 01:26.560
offices.

24
01:26.560 --> 01:30.420
And those are then configured as gateway sites.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:26.560 --> 01:30.420
And those are then configured as gateway sites.

25
01:30.420 --> 01:34.610
So you can sort of see here how this isn't really all that different from the

26
01:34.610 --> 01:35.400
other gateway

27
01:35.400 --> 01:36.400
sites.

28
01:36.400 --> 01:41.320
It's just being hosted at a co-location or a CNF.

29
01:41.320 --> 01:45.960
Sort of the fundamental difference is that connection to the gateway site is

30
01:45.960 --> 01:46.440
going to

31
01:46.440 --> 01:48.680
be over a private connection.

32
01:48.680 --> 01:53.300
Again, the assumption is that the branch office doesn't have its own internet

33
01:53.300 --> 01:54.240
connection.

34
01:54.240 --> 01:56.560
It's a private WAN connection.

35
01:56.560 --> 02:01.180
Now just like always, we're still going to choose the best path and we're going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:56.560 --> 02:01.180
Now just like always, we're still going to choose the best path and we're going

36
02:01.180 --> 02:02.040
to choose

37
02:02.040 --> 02:06.120
the best path the same way as we did before.

38
02:06.120 --> 02:11.650
So this follows that same forwarding logic that we did in the previous video

39
02:11.650 --> 02:12.400
where we

40
02:12.400 --> 02:15.800
talked about using a gateway site.

41
02:15.800 --> 02:18.400
So again, almost an identical model.

42
02:18.400 --> 02:23.240
The only difference here is we're hosting it at a co-location and we have our

43
02:23.240 --> 02:24.080
own SD-WAN

44
02:24.080 --> 02:30.800
edge routers at that co-location that's then acting as our gateway site.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:24.080 --> 02:30.800
edge routers at that co-location that's then acting as our gateway site.

45
02:30.800 --> 02:35.540
In this video, we talked about some of the minor changes that happened with our

46
02:35.540 --> 02:36.000
model

47
02:36.000 --> 02:43.480
where we decided to use a co-location or a CNF to host our own SD-WAN routers

48
02:43.480 --> 02:44.040
that then

49
02:44.040 --> 02:46.360
act as a gateway site.

50
02:46.360 --> 02:51.430
Again, the logic with the forwarding here is the same as it is with any other

51
02:51.430 --> 02:51.800
gateway

52
02:51.800 --> 02:53.120
site.

53
02:53.120 --> 02:57.860
So that actually concludes everything we need to discuss in this skill, which

54
02:57.860 --> 02:58.880
leaves us

55
02:58.880 --> 03:00.840
with just the challenge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:58.880 --> 03:00.840
with just the challenge.

56
03:00.840 --> 03:05.650
So go ahead and tackle that challenge and I'll see you in the solution video on

57
03:05.650 --> 03:06.160
the other

58
03:06.160 --> 03:06.640
side.
