WEBVTT

1
00:00.000 --> 00:05.000
So before we just jump in and start configuring things,

2
00:05.000 --> 00:08.280
we have to take a look at our game plan.

3
00:08.280 --> 00:10.780
So we know what it is we're trying to accomplish

4
00:10.780 --> 00:12.140
with this skill.

5
00:12.140 --> 00:15.420
So let's start by taking a look at our diagram,

6
00:15.420 --> 00:17.920
taking a look at what exactly we're trying to accomplish

7
00:17.920 --> 00:21.200
and what we're going to be deploying into Google Cloud.

8
00:21.200 --> 00:24.640
So that said, let's bring up that diagram and take a look.

9
00:26.940 --> 00:30.420
So as we're jumping in here and taking a look at our diagram,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.940 --> 00:30.420
So as we're jumping in here and taking a look at our diagram,

10
00:30.420 --> 00:33.420
the first thing to note is everything here

11
00:33.420 --> 00:37.380
at the top of the diagram is what we're referring to

12
00:37.380 --> 00:40.100
as the on-prem location.

13
00:40.100 --> 00:43.180
And this particular diagram is just giving us

14
00:43.180 --> 00:48.180
a general overview of how the on-prem location is configured.

15
00:48.180 --> 00:52.980
Now there is a more detailed diagram below this video

16
00:52.980 --> 00:56.340
showing a little bit more how on-prem is configured.

17
00:56.340 --> 01:00.100
This was also configured in a previous skill
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:56.340 --> 01:00.100
This was also configured in a previous skill

18
01:00.100 --> 01:02.420
and there's a reference to that skill as well

19
01:02.420 --> 01:06.780
if you need to go back and configure this on-prem environment.

20
01:06.780 --> 01:10.260
I also included the files below in case you need them

21
01:10.260 --> 01:13.420
for deploying the on-prem equipment.

22
01:13.420 --> 01:17.660
But the on-prem is not really the focus of this skill.

23
01:17.660 --> 01:19.420
What we're going to be focusing on

24
01:19.420 --> 01:23.620
is what's going on down here in Google Cloud.

25
01:23.620 --> 01:25.940
Specifically, we're going to be starting

26
01:25.940 --> 01:30.940
by deploying GCP R1 here into the Google Cloud environment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:25.940 --> 01:30.940
by deploying GCP R1 here into the Google Cloud environment

27
01:30.940 --> 01:35.540
and joining this into our SD-WAN environment.

28
01:35.540 --> 01:37.700
Now a few things to note here.

29
01:37.700 --> 01:42.500
On Google Cloud, when you're putting two different interfaces

30
01:42.500 --> 01:47.300
on a device, it actually requires that those interfaces

31
01:47.300 --> 01:50.460
be in two different VPCs.

32
01:50.460 --> 01:53.420
If you've been following along with our previous skills

33
01:53.420 --> 01:58.020
where we did AWS and Microsoft Azure,

34
01:58.020 --> 02:02.100
you'll know that we only used one VPC or one VNet
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.020 --> 02:02.100
you'll know that we only used one VPC or one VNet

35
02:02.100 --> 02:03.820
in those deployments.

36
02:03.820 --> 02:06.620
However, if you try to do that in Google Cloud,

37
02:06.620 --> 02:09.780
you'll get an error that you can't put the two interfaces

38
02:09.780 --> 02:12.100
into the same VPC.

39
02:12.100 --> 02:15.420
So in this case, we're going to need two VPCs.

40
02:15.420 --> 02:17.340
So we're still gonna have our two subnets

41
02:17.340 --> 02:19.220
like we've done previously.

42
02:19.220 --> 02:23.300
However, now there's going to be one subnet per VPC.

43
02:23.300 --> 02:26.300
The Google Cloud environment is going to be representing

44
02:26.300 --> 02:30.660
the 10.40.0.0/16 network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:26.300 --> 02:30.660
the 10.40.0.0/16 network

45
02:30.660 --> 02:33.500
and therefore in our SD-WAN environment,

46
02:33.500 --> 02:36.580
acting as site 40.

47
02:36.580 --> 02:40.460
Now of course, our ultimate goal with this entire design

48
02:40.460 --> 02:45.460
is we wanna build a VPN from our on-prem network

49
02:45.460 --> 02:48.220
down here into Google Cloud.

50
02:48.220 --> 02:52.100
Specifically, we're gonna be using VPN 10.

51
02:52.100 --> 02:57.100
This is going to link our on-prem location to Google Cloud.

52
02:57.100 --> 03:01.900
Ultimately, our goal here is going to be to have reachability
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:57.100 --> 03:01.900
Ultimately, our goal here is going to be to have reachability

53
03:01.900 --> 03:05.380
from workstation one up here on-prem,

54
03:05.380 --> 03:08.060
all the way down here to our jump box

55
03:08.060 --> 03:10.660
in the Google Cloud environment.

56
03:10.660 --> 03:15.340
So overall, this is our goal for this skill.

57
03:15.340 --> 03:20.100
In this video, we just jumped in to quickly get a look

58
03:20.100 --> 03:22.740
at what our goal is for this skill

59
03:22.740 --> 03:26.820
with deploying SD-WAN into Google Cloud.

60
03:26.820 --> 03:30.780
Next, let's go ahead and prepare our Google Cloud environment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
03:26.820 --> 03:30.780
Next, let's go ahead and prepare our Google Cloud environment

61
03:30.780 --> 03:33.540
to accept the Catalyst 8000V,

62
03:33.540 --> 03:36.480
which of course is ultimately our final goal.