WEBVTT

1
00:00.000 --> 00:07.000
So next up, let's talk about Google Cloud Interconnect.

2
00:07.000 --> 00:12.000
Now, this is going to be very similar, as we'll see to Amazon's solution.

3
00:12.000 --> 00:15.000
So let's not waste a whole lot of time here.

4
00:15.000 --> 00:19.800
Let's just jump in, take a look at it, and see what the different components

5
00:19.800 --> 00:21.000
are for Google's solution.

6
00:21.000 --> 00:29.240
So GCP Cloud Interconnect has almost all of the same attributes as AWS Direct

7
00:29.240 --> 00:31.000
Connection.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:29.240 --> 00:31.000
Connection.

8
00:31.000 --> 00:34.550
So rather than going through every single one of them one by one, let's just

9
00:34.550 --> 00:36.000
bring them up here again.

10
00:36.000 --> 00:41.200
First, just like AWS, this allows full administration across all of the

11
00:41.200 --> 00:47.210
transports, because again, this is just acting as an underlay connection for

12
00:47.210 --> 00:49.000
the actual SD-WAN tunnels.

13
00:49.000 --> 00:55.450
For this to actually function correctly, SD-WAN tunnels are still going to be

14
00:55.450 --> 00:59.000
built to a transit VPC, where the SD-WAN devices are.

15
00:59.000 --> 01:04.870
One of those tunnels is going to be going over Cloud Interconnect to a Google
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:59.000 --> 01:04.870
One of those tunnels is going to be going over Cloud Interconnect to a Google

16
01:04.870 --> 01:06.000
Cloud Router.

17
01:06.000 --> 01:10.890
And of course, the redundant tunnel is still going to probably run over the

18
01:10.890 --> 01:14.000
Internet or some other type of connection.

19
01:14.000 --> 01:19.170
And again, all of the SD-WAN features are going to be fully supported as our

20
01:19.170 --> 01:26.000
Google Cloud Interconnect is again, just like AWS, only acting as a transport.

21
01:26.000 --> 01:29.000
So let's go ahead and take a look at our diagram.

22
01:29.000 --> 01:32.000
And we're going to notice here that a lot of things are very much the same.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
01:29.000 --> 01:32.000
And we're going to notice here that a lot of things are very much the same.

23
01:32.000 --> 01:38.000
Once again, we can have that transit VPC, we can have our host VPCs.

24
01:38.000 --> 01:43.940
In this case, they're going to be connected by network connectivity or Google

25
01:43.940 --> 01:49.240
Cloud Router, and notice that our Cloud Interconnect is also landing on a

26
01:49.240 --> 01:51.000
Google Cloud Router.

27
01:51.000 --> 01:57.000
This then, of course, allows for the communication to the SD-WAN edge devices.

28
01:57.000 --> 02:01.000
And just like we saw before, we're now going to have two separate tunnels,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:57.000 --> 02:01.000
And just like we saw before, we're now going to have two separate tunnels,

29
02:01.000 --> 02:06.300
tunnel one and tunnel two, going over two different transports, using two

30
02:06.300 --> 02:07.000
different colors.

31
02:07.000 --> 02:12.260
So as we can see, aside from some of the components being different, this is

32
02:12.260 --> 02:16.000
very similar to the AWS solution.

33
02:16.000 --> 02:23.960
So in this video, we just took a quick look at GCP's Cloud Interconnect, which,

34
02:23.960 --> 02:28.000
as we saw, very, very similar to the AWS solution.

35
02:28.000 --> 02:35.000
So next up, let's take a look at the Microsoft Azure solution express route.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
02:28.000 --> 02:35.000
So next up, let's take a look at the Microsoft Azure solution express route.

36
02:35.000 --> 02:38.760
out.